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!
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!