problem in DNS name resolution - 04/22/05 05:45 PM
hi, i have one strange problem (strange to me) in my network. I have a network with an internal DNS server that is an master server for the zone asd.com.
it maps internal computer names to its addresses.
asd.com is just an example nothing more, it doesn't correspond to my real dns.
Then i have a second dns server that maps external hostnames to its ip addresses.
the problem is that some computers inside my network can't resolv hostnames that are defined in the external dns server, those computers have both dns servers specified, first the internal and then the external.
it just happens with some computer so i am thinking its a problem in the clients.
I know that windows for example (and everything else) tryies to resolv a name in the primary name server if it isn't successfull it tryies the next. But the zone that the internal name server is responsible for is asd.com, and the external also uses the same asd.com... is it possible that the clients query the internal dns server for the hostname that is only in the external and the internal says it doesn't exists and the clients stop there because the internal is responsible for asd.com so it shouldn't be necessary to continue?
it maps internal computer names to its addresses.
asd.com is just an example nothing more, it doesn't correspond to my real dns.
Then i have a second dns server that maps external hostnames to its ip addresses.
the problem is that some computers inside my network can't resolv hostnames that are defined in the external dns server, those computers have both dns servers specified, first the internal and then the external.
it just happens with some computer so i am thinking its a problem in the clients.
I know that windows for example (and everything else) tryies to resolv a name in the primary name server if it isn't successfull it tryies the next. But the zone that the internal name server is responsible for is asd.com, and the external also uses the same asd.com... is it possible that the clients query the internal dns server for the hostname that is only in the external and the internal says it doesn't exists and the clients stop there because the internal is responsible for asd.com so it shouldn't be necessary to continue?