Dnns service posting gateway instead of IP address. Anybody see this??

[WA2TTP]

I have an account with DynDns.com which has posted my host IP ok but last time it did on 1/27 it posted a gate way instead 255.255.255.255 which is useless. My IP is still the same so I can still access my remote station but I had to remove my host name from my apps and enter the IP address. I'am using a D link router.

Anybody see this happen??

Steve
WA2TTP

[K0JEG]

It sounds like your router just isn't reporting/updating DynDNS properly. When that happens to me or my parent's router, a powercycle usually fixes it. Sometimes you'll need to log into the router and re-connect to DynDNS. Unfortunately you'll need to be onsite or have someone who can be guided over the phone on site. Also make sure your account is current, passwords are still correct, etc.

DynDNS is a hack of a solution and unfortunately doesn't always work as advertised.

[WA2TTP]

Hi Eric,

Thanks for the reply. I have a feeling also that a reboot might force an update. I didn't set up remote access to the router before I left but I do have telephone remote control to reboot the cable modem and router together. I was reluctant to do this because my IP doesn't change that often and my remote station is working now. If I reboot and end up with a new IP and it doesn't report correctly then I'll have to have my local IT guy, aka son in law, stop by and log into the router and tell me what it is.

73,
Steve

[K0JEG]

One other thing you could try: Since you can reach your remote PC (I'm assuming PC, not RemoteRig or similar), you could log into the router's setup screen from the remote PC and try to determine what's going on. Usually if DynDNS isn't synced the router will show what the error is (at least with Linksys routers).

[WA2TTP]

Eric,

I'm using Remoterig and a Lantronix serial server to take care of my remote control, N8LP's control board, and my rotor. No PC on at the station end. If worst comes to worst I'll have my son in law stop by and see if any error messages are present. I also had an issue with a linksys router that wouldn't accept the domain name I was entering until I reloaded it's firmware. It worked after that by I replaced it with the D Link because it was about 4 years old.

Steve

[K7AAT]

  For the future,  you might consider putting your modem and router power on a battery backup system.   A simple 4A 12VDC regulated charger floating a small 5 or 10AH battery would preclude momentary power outages from having an effect on your equipment.   Works for me, anyway.   

[W9IQ]

Hi Steve,

You didn't say in your original post if you are using the dyndns client on a PC within your network or if your router is acting as the dyndns client. Can you clarify?

The 255.255.255.255 address likely isn't a "gateway" address although it does clearly point to a problem with your dyndns update.

- Glenn DJ0IQ and W9IQ

[WA2TTP]

Hi Glenn,

Time flys. I'm using the Dyndns client on the D link router. It has worked in the past but just isn't updating with an IP. The IP hasn't changed since I left in January so I've been able to work around it. When I get to the end of my stay in Florida I may just do a remote reboot of the router/cable modem and see what happens.

Steve

[W9IQ]

Hi Steve,

The dyndns folks did change some of their commercial terms a while back so you may want to log into their site and just make sure everything is OK with your account. It sounds however, like that shouldn't be the issue since you can still use your dyndns URL.

You may also wish to look at the dyndns web site for routers that are known to work / have problems. I have used the list in the past before making an architecture or purchase decision.

I would also suggest taking a look at the log file of your router to see if you can spot any problems there.

- Glenn DJ0IQ and W9IQ

[WA2TTP]

Hi Glenn,

My Dyndns acct still shows the same host ip of 255. etc that is useless. I can't use the dyndns URL because of this but I know what the home IP is so I just plugged that into my Remoterig gear and the serial server software. I'm good as long as the IP doesn't change. I'll check the router log when I get home. I'm leaning toward a router glitch but as long as my station still works I don't want to reboot the router. The router sent about 3 good IP updates in Jan but after that it's been ng.
Thanks for your suggestions.

Steve

[W9IQ]

Hi Steve,

Sorry for the confusion - the thread has been open for a while and I should have reread your original post.

I find that consumer grade routers (and unfortunately some of the commercial grade ones as well) often suffer from unexplained glitches that a simple power off/on cycle clears. So for routers to which I have limited access, I install a plug in the wall timer that does a brief power off/on cycle in the middle of the night when the router isn't being used. This ensures that if I lose access through the router it will fix itself in less than 24 hours.

My first incarnation of this was a PIC based processor with a relay and battery that I put inline on the secondary side of the wallwart. For less than $5 of parts, it worked very well. But then I saw that I could buy the digital wall timers with 15 minutes of granularity for the same price that did the job just as well but with less hassle. The solution works great if you can tolerate 15 minutes of regularly scheduled downtime a day in exchange for automatic recovery.

- Glenn DJ0IQ and W9IQ

[WA2TTP]

Glenn,

That's a good idea. I may just do that next year before I go away.

Thanks,
Steve

[WA2TTP]

When I concluded my Florida remote operations I rebooted the router and it posted a correct IP host address to the  Dyndns website within a minute.

When I got home I found out my power had been off for 2 1/2 hours during the 2 1/2 months I was away.

Thanks to those who posted suggestions.

Steve,
WA2TTP

[K0JEG]

Glad to hear everything worked out for you. This was a good topic, I got a few tips for future reference.