Do you have another "rouge" DHCP server (in a router or WAP) handing out IP addresses somewhere?
Main Topics
Browse All Topicswe 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
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?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Shouldn't. It wouldn't forward the BOOTP packets across the networks unless you set up a DHCP relay agent.
Are all your servers set to static IP addresses? Does the DHCP scope only point to those servers for DNS? Does the DNS server point to itself for name resolution? Perhaps a brief overview of your network would give us a better idea.
Upon further review in the first domain controller the second DNS entry is pointing to the ISP DNS.
The second dns server points to the .5 (the first dns server) then to .6 (itself)
That needs to be changed so that it only points to itself and not another dns server.
but this still doesn't explain the 192.168.11.1 cropping up everywhere...
No dhcp relay agent. Only the firewall a sonicwall 2040 enhanced OS is running DHCP.
on the sonicwall the dns server setting si set to maunal and are:
.5 internal dns
.6 internal dns
.17 external isp dns
The dhcp scope is .51 to .254 with conflict detection is enabled.
The dns/wins settings on the DHCP are set to inherit dynamically from sonicwall's dns settings
all the servers are below .50
yeah the forwarders on both dns point to the external (now both external) isp dns servers
yeah that is what i am battling now - some people have decided to enter in the external dns server ip so they can get to the internet... the bad part is they still are having issues as well. i just don't get why the 19x.xxx.xxx.xxx
Well, I would start with the cleanup first and see if that eliminates these odd IP addresses that you are seeing.
How are they entering the IP addresses on their own? They shouldn't have permission to modify their own IP settings, and even if they do how do they know the right IP address to put it to?
You have internet access blocked off?
But seriously, if this were my network I would restructure the DHCP infrastructure to run on one of the Windows Servers. That will give you more granular control of everything.
You can authorize the server in AD and prevent any "rouge" servers ont he domain from handing out IP addresses.
I would then push out a logon script / GPO that reverts the IP settings of the Workstation computers back to what YOU know they should be every time they reboot.
He who controls the servers controls the domain... MWAHAHAHAHAHAHAHA ::cough::
The best solution is to put pot in the IT guy's lunch box, and call the boss over. Or the power supply of his computer.
You said manually configuring the clients does the same thing though, right? I think that something is poisoning the DNS cache on one the the DNS servers. DNS servers can cache query responses.
If possible, try dropping one of those DNS servers off the network, flushing DNS settings on a client that you know has had that issue and see if you see the same thing. Get the same thing, drop the other one.
You are running anti-virus software on these machines, and keeping them up to date, right? I dont have to go down that road, right? (please say no, please say no, please say no)
Also, you can check your switch if it's an L3 switch (depends on the switches firmware, etc etc) for any hosts that are on that network. Another thing that you can try is to set your machine on the 192.168.x.x and use something like Angry IP scanner to suss out the rogue machine.
And for f$ck sake use the Windows DHCP services man. Just do it.
Hope this helps.
I'm giving the points cause you were first with the helpful hints, etc.
I went to the site and in 10 minutes found out what happened. Someone turned on and plugged in a wireless router they found at the site. Turns out the guy there did not check very throughly for what I asked him to check for....
I yanked the router, and when people come in they will ipconfig /flushdns */registerdns
and all should be happy and fine.
Thanks again for the help
Business Accounts
Answer for Membership
by: JohnGerhardtPosted on 2008-11-04 at 12:35:23ID: 22880413
Maybe a rogue DNS server on the network..?