|
I keep getting this error in a WRT54G ddns service: "Can't connect to remote site, DDNS update fail!" After a little poking around I find that for some reason members.dyndns.org gets resolved to 1.1.1.1 Just for amusement I tried members.dyndns.com it also resolves to 1.1.1.1 I find this even happens for both even with the Internet guide ip addresses in Static DNS1 and Static DNS2. (216.146.35.35 & 216.146.36.36) Would this be a result of COMCAST deliberately blocking these url's and DNS IP addresses? Update: |
|
(This answer has been edited to better reflect the updated question) This question can easily turn into a discussion with several posts back and forth, and it may therefore be better to take the discussion to the community discussion forum. But that is up to you. If Comcast is indeed blocking DynDNS' servers, then there isn't really much you can do to circumvent it. But I have trouble understanding why Comcast would do that, and it also surprises me that similar reports haven't been posted here by others, considering the size of Comcast. If you are absolutely confident, then you may wish to send a complaint to Comcast. I am still curious, however, which local device you made the DNS lookups on, and the traceroute. If you did it on your computer, what operating system? If you did it on your router, have you tried on your computer as well? I used a remote machine via VPN to look up the IP for http://members.dyndns.org. I got 204.12.248.112 which I then used tracert locally and got this response: "Tracing route to 204.13.248.112 [1.1.1.1] over a maximum of 30 hops." That answered my question. They are deliberately blocking the DDNS updates.
Jan 23 at 01:30 PM
wsagazoid
|
|
I just switched to comcast today (2/7/2012). My DLink NAS-323 was working successfully on Qwest/Centurylink, but failed when I switched to Comcast. ANSWER: Based on other posts, it seems like Comcast may not be resolving http://members.dyndns.org, which I take to be the name of the DynDNS update service. To work around this, on my Dlink NAS in the LAN setting there is an option to specify "alternate DNS servers". I entered the public Google DNS address (8.8.4.4) for DNS2 and instantly the DynDNS update worked. 8.8.8.8 should also work. So, it would appear that comcast is not blocking the ports, but perhaps is blocking or not resolving the name. |
|
I use Comcast myself, as well as their recursive services (for comparison between Comcast and Internet Guide), and I haven't experienced these issues. Can you provide a full tracert to http://members.dyndns.com and paste the results here? What happens when you use nslookup and try to resolve http://members.dyndns.com? I find it very strange that when he does a traceroute against a specific IP address, it gets translated to a different IP address. You can't do that with DNS, even with a local hosts file.
Jan 27 at 09:56 AM
VikingTiger ♦
Malware? That could well do that kind of thing.
Jan 27 at 11:39 AM
Cry Havok ♦
|
