DDNS not working with RT31P2

Posts: 2 · New Forum Member Joined: Nov 02, 2004 Posts: 2

According to the RT31P2 in order for dynamic dns to work you have to use one of the 2 providers they say. Dyndns.org and TZO.com. I transferred my domain over to dyndns.org and I know it's configured right on that end. When I attempt to activate ddns on the router set up it tells me the host name is unknown. Anyone else have a similar problem?

Posts: 2 · New Forum Member Joined: Sep 26, 2005 Posts: 2

Just reviving a long dead thread in hopes someone has stumbled across the answer to this problem here. I've the same setup/issue with the DDNS feature failing to log into DynDns servers and update the host record. Running v1.30 of firmware on the RT31P2 Thanks Smile

Posts: 1715 · Posted: Mon Sep 26, 2005 1:34 pm Post subject:

I've not played with the RT31 & Dyndns, but with my RTP300 & WRT54G routers, here's how I have it configured:

Username: this would be the username you use to log on & add/delete services on Dyndns
Password: password for the above
Hostname: put the full host name here. So, if you're using "VOIP@dyndns", you'd need to enter voip.dyndns.org here. It MUST have the full host name, not just the name portion you created.

Posts: 2 · New Forum Member Joined: Sep 26, 2005 Posts: 2

That is how I have it set up, but it doesn't seem to make a difference. >.<

Posts: 4 · New Forum Member Joined: Nov 02, 2004 Posts: 4

It's well known that Linksys does not keep up with the DDNS protocol. It doesn't work. Instead, I run a client on a PC to do the same.

One would think that Vonage would have some influcen on Linksys but this feature doesn't appear to be a priority Sad

Chris

Posts: 33 · Vonage Forum Junior Joined: Jun 19, 2005 Posts: 33

cjtwantstoknow wrote:

It's well known that Linksys does not keep up with the DDNS protocol. It doesn't work. Instead, I run a client on a PC to do the same.

One would think that Vonage would have some influcen on Linksys but this feature doesn't appear to be a priority Sad

Chris

I'm not sure how "well known" it is - I (and many friends) are using dyndns on our RTP300, RT31P2 and various linksys routers without any issue. I've have DDNS working for nearly 2 years now.

Occasioanlly the router gets hung, and doesn't change the IP address, but a quick reboot will fix that.

Posts: 1715 · Posted: Tue Sep 27, 2005 12:35 pm Post subject:

Add one more "success" vote for the RTP300 & DynDNS.. never had an issue with it not updating. Of course, when I'm running behind another router like I am most of the time, the RTP300 only posts the 10.x.x.x IP that it gets, but I only use the DynDNS addy when I'm on the road and the RTP300 is acting as my primary router.

Posts: 1 · New Forum Member Joined: Jan 07, 2006 Posts: 1

VonageTPA wrote:

I've not played with the RT31 & Dyndns, but with my RTP300 & WRT54G routers, here's how I have it configured:

Username: this would be the username you use to log on & add/delete services on Dyndns
Password: password for the above
Hostname: put the full host name here. So, if you're using "VOIP@dyndns", you'd need to enter voip.dyndns.org here. It MUST have the full host name, not just the name portion you created.

Found this in Dyndns.org forum and wanted to get it posted somewhere else as well. Following is pasted from there:

"Why does the DDNS client in my router report "The hostname does not exist"?

Unless the DDNS client in your router has a specific option for Custom DNS, it does not provide direct support for this service. You may be able to make this DDNS client work with Custom DNS by adding "&system=custom" (without the quotes) after your domain in the "Host" field. As an example, instead of having example.com in the Host field you would have example.com&system=custom.

In a few cases, we have seen routers which require that this be enclosed in either single or double quotes. So, if "&system=custom" (without the quotes) does not work, try "example.com&system=custom" (with the quotes) or 'example.com&system=custom' (with single quotes)."

I was getting "invalid hostname" and after changing to:
example.com&system=custom (without quotes)
I got a sucessful update.