Another problems-Weird DNS resolving issues

[CourtLNet36]

Okay here is my setup. A small AD integrated network (all
Win 2K) with a primary (GC) and secondary domain
controller in the same subnet (just for redundancy). Both
servers are also the primary and secondary internal DNS
servers for the network. Everything replicates between
the two. These servers have mapped outside access to
resolve internet queries. I have removed the "root" DNS
entry, and have added the IP address of our external DNS
servers to the Forwarders tab.
Here is the weird part. When client machines try to
resolve Internet addresses the request skips the first
domain controller (primary DNS), and gets resolved by the
secondary domain controller (secondary DNS). So, I don't
have a problem with Internet URL resolution unless I don't
add the secondary controller/DNS to the "Alternate" DNS
entry on the client machines. Even the primary
controller/DNS goes to the secondary for outside
resolution! Internal DNS resolution can still take place
with the primary machine though.
Any insight would be appreciated.

Thanks!

 

[snooze821]

Are you using DHCP? if the second DNS is static is the IP or your primary DNS first in the DNS listings?

 

[CourtLNet36]

Nope, not using DHCP. I'm not quite sure what you are asking about the second part. If you are talking about what I list as the DNS entries on the client machines, then yes, the primary is listed first. Hope this helps!

 

[Jpoandl]

Nice explaination of your setup. I think I have a good picture.

One thing to check: What are the local TCP/IP properties of your DNS servers?

DNS prim IP = 10.10.10.1
Local TCP/IP DNS primary = 10.10.10.2
Local TCP/IP DNS Secondry = 10.10.10.1

DNS Sec IP = 10.10.10.2
Local TCP/IP DNS = 10.10.10.1
Local TCP/IP DNS = 10.10.10.2

Should try to register with remote DNS servers of the same domain. (Although, I think MS is going to revamp thier reccomendations in the future to be more like NT 4.0 WINS...point primary and secondary to itself.)

You DNS local TCP/IP properties should NOT point to the internet DNS servers. You should use forwarding for this. It sounds like you are; however, you should check just in case.

Another thing FORWARDING to the internet is a SERVER BASED setting. Therefore, if you have TWO DNS servers, you have to make the forwarding configuration 2 times. Check you primary DNS server, verify that it is forwarding to the internet as well.

You also might want to use NSLOOKUP to troubleshoot. You can point directly to any DNS server using NDLOOKUP. Use the SET D2 to enable DEBUG information.

I hope this helps. Joseph L. Poandl
MCSE 2000

If your company is in need of experts to examine technical problems/solutions, please check out

http://www.esavio.com