What is an update client?

An update client is a computer application or a feature in your router that keeps your hostname’s IP address up-to-date. The update client periodically checks your network’s IP address; if it sees that your IP address has changed, it sends (updates) the new IP address to your hostname in your Dyn account.

Why do I need an update client?

If you’re like many DynDNS customers, you have a dynamic IP address which changes periodically (monthly, weekly or even daily). This can make it difficult or impossible to connect to services at home, like remote desktop or FTP.

Using an update client with your Dynamic DNS (DynDNS Pro) hostname allows you to make sure you can always reach your home network, because it makes sure that your hostname is always up-to-date with the latest IP address. The update client runs in the background, so once you have it properly configured you don’t have to worry about it; you only need to remember your hostname to reach your files and services.

Which update clients can I use?

You can either use the update client in your router or download a software client to run on your computer. We highly recommend using software clients since they tend to be more reliable than many of the update clients used in routers.

Our recommendation:

We recommend you use one of the official Dyn Updater Clients. However, if you use a third party update client it should be configured to send via an HTTPS connection to protect the confidentiality of your data over the Internet. If you need to continue the use of HTTP, we strongly recommend utilizing your update client key instead of your account password.

Please note: While we do not officially support inadyn or ddclient, we recommend them over other alternatives. Our Update Client Configurator is available to generate configuration files for them.

“I want to send updates myself via TSIG rather than install software.”

Hardware Devices

Many hardware devices, such as DVRs, webcams, routers, etc, have built in update clients. Unfortunately, as they are all third-party products, you’ll need to contact the manufacturer for support with the device.

Why am I being blocked for abusive updates?

First, don’t panic! If your host was blocked for abuse, it probably wasn’t something that you did intentionally. Hosts are blocked to prevent our system from being flooded with unnecessary updates from broken or misconfigured update clients. You likely had no way of knowing there would be a problem until you received the notice in your Email. Your services aren’t terminated; we have just temporarily stopped accepting updates for the host until the problem is fixed.

There are two possible reasons that you were blocked for abusive updates:

  1. You are using an update client that was not developed correctly. Your update client is sending numerous updates even though your IP address hasn’t changed. An update client should only send updates when a change is detected, but some clients send updates at regular intervals (e.g. hourly) whether or not an update is necessary. We allow dozens of abusive updates before a host is blocked (to allow for test updates and mistakes); if your host is blocked, your update client is behaving abnormally. Even if your ISP or power company is experiencing issues, a good update client will not send abusive updates.

    If your host is blocked for abuse, you should disable your update client and use one that has been certified to work with our services, such as our official Dyn Updater for Windows or Mac OS X. If you are using a hardware device that has worked for months or years without a problem but suddenly begins to send abusive updates, it may be a memory error; try powering down the device for 60 seconds (remove the power cord), then plug it in again. In most cases, this should resolve the issue.

  2. You are using more than one update client at the same time. This typically occurs if you have installed a software client on your computer and are using the update client feature in your router or DVR. Disable all but one of your update clients (preferably keeping the software client instead of a hardware client) and the problem should stop.