Child domain dns server resolves all queries except those by itself???


T

T0GGLe

Hi,

2 domains, with child domain having one dns server. New delegation was
carried out properly on parent domain and dns was installed on the
server in the child domain, dynamic updatees enabled and all that jazz
:)

Now everything works fine from the computers in the child domain - if
you ping the FQDN of any computer on the network it works fine,
appending the correct suffix to the computer name depending on which
domain the computer is located.

Great you might ask, then what's the problem? Well if i open up a
command prompt on the child domain dns server and try pinging a
computer in the parent domain it gives me "unknown host". If i ping
the fqdn of that same computer, it works fine.

It's just that i would have thought that being the dns server that all
the computers in the child domain successfully use to resolve their
dns queries, it should be able to resolve dns queries "itself".

As per MS's instructions the child dns server points to itself for dns
server setting within tcp/ip properties.

I assure you the computers in the child domain use this child domain
dns server for name resolution and not the ones in the parent domain,
as i can see from ipconfig /all, the dns details of which are
distributed via dhcp.

Now the solution i guess is to manually put the dns search suffixes in
tcp/ip properties on this server but for crying out loud it's the dns
server, can't it look to itself for name resolution even when it's
told to?

Help!
 
Ad

Advertisements

S

Steve Duff [MVP]

The DNS client resolver on a DNS server is no different
than the one on the workstations.

In the server's network adapter have you checked "use
parent suffixes of the primary DNS suffix" checkbox?
That being not checked is the only reason I can think of
offhand why you'd get the behavior you describe.

If so, try turning on tracing in NSLOOKUP and see
what is going on. NSLOOKUP has its own resolver logic
that allows you to see what is happening.

Steve Duff, MCSE, MVP
Ergodic Systems, Inc.
 
Ad

Advertisements

T

T0GGLe

In the server's network adapter have you checked "use
parent suffixes of the primary DNS suffix" checkbox?
That being not checked is the only reason I can think of
offhand why you'd get the behavior you describe.

Thanks Steve that was it. Interestingly enough without that box ticked
if i did ping <parent domain server name> i got host not found, but if
i did nslookup <parent domain server name> it was resolved.

However having put that tick in it now works fine both ways thanks.

Cheers!
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top