problem resolving just the host name

  • Thread starter Thread starter NAN
  • Start date Start date
N

NAN

I have 1 tree with 2 subdomains. Every time we do a
nslookup with just the host name (not the FQDN) it
resolves with the parent domain suffix.
Ex. parent domain=cnmc.org
child domain and zone = lab.cnmc.org

When you go to resolve xyz (fqdn = xyz.lab.cnmc.org) you
get back xyz.cnmc.org
Please help!
Thanks.
 
NAN said:
I have 1 tree with 2 subdomains. Every time we do a
nslookup with just the host name (not the FQDN) it
resolves with the parent domain suffix.
Ex. parent domain=cnmc.org
child domain and zone = lab.cnmc.org
Click to expand...
When you go to resolve xyz (fqdn = xyz.lab.cnmc.org) you
get back xyz.cnmc.org
Click to expand...

Of course. Every machine uses it's own DNS domain name
suffix as the DEFAULT suffix for all queries that are not FQDN
(i.e., fully qualified domain names) -- note, an FQDN is any
that is not terminated with a "." dot.

If you wish the machines to ALSO try other domain/zone names
as default suffixes then go to the NIC\IP\Advanced\IP properties
and add them into the suffix search list, e.g., on cnmc.org machines
add lab.cnmc.org and on lab.cnmc.org machines add cnmc.org
OR on the latter, enable searching of parent suffixes.
 
I tried doing that, and a pc in the lab.cnmc.org domain
still comes back with just cnmc.org suffix.
 
I tried doing that, and a pc in the lab.cnmc.org domain
still comes back with just cnmc.org suffix.
Click to expand...

Oh, that sounds like you have the OPPOSITE problem,
where the computer in the child domain, has it's machine
name set in the (wrong) parent domain.

Fix this in the System control panel -- it's better to fix it,
but you should be able to also add the suffix in the NIC
properties.

Either that, or the machine really isn't in the child domain....
 
Back
Top