Intermittent DNS failure on windows 2003 network

we are having intermittent DNS failures on our windows 2003 network.

every 30 minutes or so it seems some people lose their DNS settings. what is bizarre is that even manually configured dns machines are going nutty
example:

our dns servers are
10.99.70.5
10.99.70.6

doing "nslookup all"   reveals both DNS servers

However after a while doing "nslookup all" shows one dns server with an IP of
192.168.11.1
"results of nslookup below"

DNS reqquest timed out.
timeout was 2 seconds
can't find server name for address 192.168.11.1: timed out
Default server: unknown
address: 192.168.11.1


Running ipconfig /flushdns and /registerdns brings it back.

Now we had VMware installed on one of the DNS servers and I recently uninstalled it.

It should also be noted that the FIRST (FSMO) DNS server is a Virtual machine running on VMware and the second DNS is running on metal.

Nothing I do seems to change this.

Any ideas?
05fdmlAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

RobinHumanCommented:
Do you use the 192.168.11 range?
If so, it is using the dns data from that when it does replication, and that's why you are loosing connection.
Also, make sure that your dns records are reflecting the correct host and pointer addresses (check when the server is not responding what the dns record is showing in forward and reverse lookup zones)
0
sensored2008Commented:
there is a big chance 192.168.11.1 is an for a router on the network that has dhcp enabled and when it broadcast its  settings,  you  loose  connection
 to find  out  try this
from  run type cmd  then type tracert 192.168.11.1
and check on a failing machine  what ip setting it is  getting
also  check if that  host  file of your DNS  server has that ip in it as its  own
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
05fdmlAuthor Commented:
yes that was it
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.