server 2003 - dns server - nic properties setup HELP needed

[troyquigley]

i have 2 dns servers running server 2003
they are both connected to the same switch (they sit right next to each other)
they are both setup vertually identical (identical hardware)

one of the servers surfs the internet fine - the other is ALOT slower at surfing & disconnects from workstations sometimes.
someone mentioned in my last post about dns looping. i want to make sure i have not messed up my dns nic settings.

what i have done:
installed latest nic drivers
rebooted
checked my cisco switch for errors on the port. (zero errors)
made sure the port and the nic were both set to auto detect (they are)
they are both running at 100/full

BTW - all my workstations have the "dns client" service disabled

this is what i have
server 1
ip: 192.168.0.254
p dns: 192.168.0.254
s dns: 192.168.0.253

server 2
ip: 192.168.0.253
p dns: 192.168.0.253
s dns: 192.168.0.254

is the above settings causing dns looping ? or could it be causing some of my problems ?

 

[Genx87]

Hard to say but I have a similar setup but my backup DNS\AD still used the Primary DNS\AD as its primary DNS server.

 

[BZeto]

Maybe I'm missing something, but I dont see a need to have the 2nd DNS server's Primary dns set as itself.

 

[spidey07]

yes, you're looping.

one and only one server should be primary.

the other is secondary and pulls zone information from the primary.

there should be tons of information on microsoft on how to setup DNS. It's one of the most important things there is so make sure you read a ton about it.

 

[RebateMonger]

Why do you disable the DNS Client Service on your client PCs?

Microsoft: DNS Client Services

"If the DNS client service is stopped or disabled on your computer, you may not be able to locate the domain controllers of the Active Directory domains and will no longer be able to locate the devices identified using DNS names."