DNS not accurate

We are running a windows 2008R2 domain environment. i am running into a problem where clients that have two records in DNS (one for wireless and one for ethernet) are failing to update. What happens is when a laptop is connected to both wireless and ethernet then the ethernet is disconnected, the record in DNS for the ethernet connection doesnt go away. This causes server initiated connections to the client to periodically fail as the server (in this case our SCCM 2012r2 server) tries to connect to the ethernet interface which is disconnected.

If I manually delete the record for the client ethernet connection, everything starts working.

Please help!



The primary purpose of DNS is to allow clients to find servers; it is not designed to be a real-time map of your network.

I think you're going to need to create some scripts that periodically remove duplicate entries and force workstations to re-register with DNS.



The primary purpose of DNS is to allow clients to find servers; it is not designed to be a real-time map of your network.

I think you're going to need to create some scripts that periodically remove duplicate entries and force workstations to re-register with DNS.



DNS entries get removed based on the DHCP lease and also when the DNS scavenging task is set to as well.

Unfortunately there is really no way around this (that i can think of) other than having your laptop users only use wireless (which probably will not fly).

Will.



why do you need to activate both wireless and ethernet at the same time?



That's a pretty common setup. Makes it easy to dock and undock.

Otherwise you have to do some magic to disable the wireless when docked....

Most folks manage it by leaving both connections enabled all the time, but having the default route for the wired connection have a lower metric than the default route for the wireless.

That leaves you with two DNS entries, though, as both connections register with DNS. Both connections work when docked, too. When you undock, though, the wired connection is no longer available but the DNS entry is still there.

I suppose one option would be to uncheck the "register this connection with DNS" for the wired connection. Then SCCM finds the device via the wireless address.



create a batch file from notepad, ipconfig /flushdns to run daily at 8am on the server and maybe noon. Do so on startup on the laptops. I've run the command and it's cleared up the wireless issue you're talking about.

I also explain to users that operating systems CPU's where most wireless resinates from now and even wireless cards in older laptops often utilize the faster of the two networks. However this isn't always the case and the majority of time the LAN wired network is faster. I explain that it's best for them to disable the wireless while connected in a docking station. 99% of the time it's a simple function key / tab combination. A little user training never hurt anyone :-)

Share this

Related Posts

There was an error in this gadget