|
Hey all. I've been using DynDNS for a while now in conjunction with the various routers I've had over time with no problems at all. However, recently I've noticed that my dynamic IP address isn't being automatically updated to my DynDNS account, so I went into my router to see what gives. Turns out that now it's giving me the error "Failed to resolve hostname" whenever it tries to connect to my account. Anybody have any idea what's the matter? My router is a Linksys WRT160NV3 running the latest firmware. Thanks. |
|
The two DNS server addresses DNS1 and DNS2 on your router, 192.168.1.150 and 192.168.1.151, are bad addresses not responding to DNS lookups. Therefore remove these. These are causing your troubles with "Failed to resolve hostname". In case you got other DNS server IP addresses from Roadrunner, enter those now instead of these 192.168.1.x addresses. |
|
"Just to be clear, I replace the 123.321.123.321 with my IP address right?" Yes and no, not with the IP address assigned to you by your ISP, but with the primary DNS server IP address shown on your router, whatever this is. You apparently did it wrong again (DNS Server: unknown). Start over, you still have eight trials left. ;-) |
Oh, no! I wasn't aware I was being monitored. :P Anyway, hopefully I got it right this time (Used 192.168.1.1). It kept closing before I could read it, but I eventually got it down: |
|
"t's giving me the error "Failed to resolve hostname" whenever it tries to connect to my account." Most DDNS updaters in routers perform a DNS lookup against the hostname, i.e. your DynDNS hostname. If that fails the router may stop the update process at this point. Check that you correctly entered your full hostname, e.g.
Where |
|
You mean in my PC's command prompt? I ran that command and got a few time outs and then the prompt closed. I'm guessing that's not supposed to happen. |
1 2 3 4 next page »