The WRT54G provides a built in DDNS client which works (for the most part) with all three of our primary DNS services (Custom DNS, Dynamic DNS and Static DNS). This unit has been certified to work with our services.
That said, there are some peculiarities which need to be commented on and which anyone using one of these routers should be aware of.
Note: These comments are based on our testing of the firmware version 3.03.6 dated 1/3/2005. If you are running an older firmware you should consider updating to this version (or a newer one if available).
The good news with this router is that it probably won't send abusive updates and get your host blocked. This is a good thing.
Also, the router properly identifies itself to us when it submits an update, providing the model number and firmware. This may sound like a small thing, but it makes it much easier for us to troubleshoot when there is a problem.
The update client interface has no way to set a number of optional parameters. Specifically there is no support for:
If you are using this router to update a host in our Custom DNS service, the above is not an issue. If you are using Dynamic DNS or Static DNS, this may be a problem for you.
Second, the router has no provision for sending an update if your IP address has not changed within the past 28 days. This is not a problem if you are using Custom DNS or Static DNS, but if you are using Dynamic DNS this may result in your host being deleted after 30 days. This can be avoided by purchasing an Account Upgrade.
Third, in order to update a host in either the Custom DNS or Static DNS service you will need to specify the service in the Hostname field along with the actual host name. For example, for a host in Custom DNS you would enter
example.com&system=custom
and for a host in Static DNS you would enter:
example.homeip.net&system=statdns
The Hostname field is currently limited to no more than 48 characters.
If you set the update client in the router to "Disbaled", the router sends an update that sets your host to 192.168.1.1.
Contact Linksys and ask them to fix this...