Question Locked

DHCP Users Lose Correct DNS Address

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

My users that use DHCP to get a network address are sometimes losing connectivity due to their DNS address being changed. The DNS is run on the domain controller which is Windows 2003.

When they first obtain their lease, they show the proper address (192.168.50.5). They'll be working fine, then after some time they magically lose the proper DNS address and it changes to 192.168.15.1, though the rest of their information is fine and they can still ping via IP. Renewing the lease fixes the problem and they can go about their business.

I've never experienced this before and don't really know where to start looking. Any help is greatly appreciated!

6 replies

by churdoo

I'm willing to bet that there is a rogue DHCP server on your network. Perhaps someone inadvertantly installed a soho router and/or wireless appliance somewhere and did not disable the factory default DHCP.

by christopher

Thank you for the reply.

I was wondering about this also, but wouldn't it change more than just the DNS address if this were true?

If it is another DHCP server, is there a fool-proof way to find it's address?

by churdoo

One would think that the DHCP client would get all of the settings from one or the other DHCP server, whichever one responded to the DHCP request first, but I've had this exact scenario at a client and it was only the DNS info that was pulled from the rogue DHCP that turned out to be a SOHO wireless/router appliance which some jamoke hung on the network with the factory default DHCP left enabled.

Unfortunately, these are very hard to find physically, but I'm guessing that the rogue appliance has an IP of 192.168.15.1 (the addy of the false DNS server). Also check IPCONFIG /ALL at a client which is experiencing the problem as it may also list a false DHCP server IP that may or may not match the false DNS IP. In either case, you can statically assign a test workstation an IP in the same network as the false IP, something like 192.168.15.11 for example to see if you can PING the false IP. If you get replies, then you can get a MAC Addy by doing an 'ARP -a' and depending on your switches, you may be able to query their ARP tables and isolate which switch the rogue device is connected to.

Happy hunting

by fred123456

Did you define alternate DNS setting in TCP/IP on the local machines?

Its under the Advanced button wen you config TCP/IP. You can add alternative DNS entries that will be used when the primary is unreachable.

by christopher

Thanks a bunch churdoo! I guess it was against my instincts that it'd be another device since it was only changing the DNS. After an exhaustive search I found the device (ended up being a voip box) that a user had plugged in under their desk. Thanks again :)

This discussion is closed to new replies.