I have a small home network and website. The server runs Windows 2003 Server with Exchange 2003. All my home systems have static IPs. I have broadband with dynamic IP (provider doesn't offer home broadband with static IPs), thus necessitating DynDns service. The new version of DynDns Updater keeps changing my Primary DNS IP setting from my local server to theirs, hosing my Active Directory. Workstations won't authenticate with IPs going through DynDns's server. How can I stop the Updater from chaning my Primary DNS IP setting?
Regarding the changed DNS entries, this is the DynDNS Update Client version 4.x. You need to uncheck Use DynDNS.com Internet Guide on this computer under Advanced. More Details. You may have selected to use Internet Guide during installation.
Also, version 4.x is not eligible to be used on servers, as of the bottom of this page. Use the more elaborated version 188.8.131.52 on servers instead. Don't be confused about the version numbers. Version 4.x is for easy use on client PCs, whereas version 3.x is the real Pro version.
I have the opposite problem and am looking for an answer.
I have the updater (4.x) operating on a Vista X64 machine which is hosting some services through my cable modem/router.
I have a small wifi network with several devices and computers. The gateway modem/router is the DHCP server for the networked devices. The computer hosting the Dyn Updater has a "reserved" IP address - meaning it too uses DHCP however it always gets the same address from the gateway.
It seems that every time the updater updates with Dyn, all the other client machines have their DNS address set to the machine with the DYN update client running on it, so then they can not access the internet. My computer running the Dyn updater is not set up to be a DNS server and nor do I want that.
I have no idea how the computer with the Dyn updater could possibly be influencing the DHCP settings for the gateway or other network clients. This is totally bazaar.
Any advice would be greatly appreciated!
answered Jun 16 at 02:10 PM