|
Hi, I can't connect to my server using the hostname I just set up. Here's a quick summary of where I'm at: I set up tversity server on my pc. When I use my iphone with wifi turned off (hence outside my lan) I can connect to tversity with my external IP address. DynDNS updater is working and DynDNS shows the correct IP address, but when I use my hostname I cannot get to the server. DNScog reports the wrong external IP address. I switched my DNS to the Internet Guide servers, but no love. Any suggestions from anyone on what I might be missing? I have already flushed my local DNS cache. It's been a couple hours now and I figured the Internet Guide servers would have the proper 10min TTL even if my ISP's did not. Any help greatly appreciated! -Greg |
|
Actually, I wonder if your problems related to these DynDNS status updates. Well, it might have been something to do with those. Or it could have been something else. But whatever it was, it's working now. Cry Havok and cgonyea, I appreciate all the supportive feedback. And I wish I could have contributed to the solution rather than the mystery!
Jul 22 at 11:13 PM
Grreg
|
|
The TTL shouldn't be the issue, http://DynDNS.com hostnames have a 60 second TTL by default unless you changed it. That means any time the DynDNS Updater sends an IP address update, the longest anyone will have the old IP address cached is 60 seconds. You can view what the TTL is on the modify hostname page for the hostname. When you say DNSCog is showing the wrong IP address, are you running the dig lookup via DNSCog? Use http://dnscog.com/dig/ , type in your hostname, and make sure the answer section matchs the IP address that the DynDNS Updater says you have. DynDNS Updater uses http://checkip.dyndns.com to do its checks, so the IP addresses should match. If they don't match, then I wonder if you have multiple update clients. The behavior you are describing might be a symptom of this issue. A common mistake is to configure the update client on your router (or maybe tversity has an update client?) plus installing the DynDNS Updater. If the router for example sends the wrong IP address (such as its LAN IP instead of WAN IP), that could cause the issue. If you have done this, make sure you disable all update clients except for the DynDNS Updater. If that doesn't work out, then e-mail support and we can take a look at the logs. Without knowing your hostname, we are just guessing at this point. Yes, I'm using http://dnscog.com/dig/ to do the lookup. But what it returns doesn't match what I see when I log into my account at DynDNS and look at the host services page. There I see the correct address, which matches the updater. My router (an airport extreme) doesn't even support DDNS as far as I can tell. Tversity doesn't have one to the best of my knowledge, and I certainly didn't configure one in it. This is the first time I've ever tried a DDNS, so I don't have any old or other clients installed. I didn't change the TTL, I just wrote the wrong thing in my question. Thanks for the help
Jul 17 at 10:56 PM
Grreg
Thanks for the prompt response, on a weekend no less!
Jul 17 at 10:57 PM
Grreg
|
|
Cry Havok: those status updates just have to do with the http://nsX.mydyndns.org nameservers (ie: Custom DNS and Secondary DNS). If he is using just the free DynDNS service (or the Pro upgrade), those are on different nameservers (nsX.dyndns.org). In either case, the maintenance would have no effect on the updates, as the updates are sent to a different server (members.dyndns.org), would go out to the other nameservers that are running, and would show up on the logs. At no point was there no downtime for those using Custom DNS or Secondary DNS. I know in the roughly 50-75 e-mail tickets I can do a day, plus phone calls, I haven't come across a single one that has reported a similar issue to this. No one else here has mentioned reports of this happening either. If something were really broken with updates, I tell you one thing, it would be extremely stressful here with 4 million users e-mailing in asking why their hostname hasn't been updated! Grreg: If you are still having problems, e-mail support so we can take a look at the logs and compare it with what your updater is showing. Send your update client log in the ticket. Yeah, I've seen one thread here with a few people posting. If it was widespread I'd expect to see a lot more noise in the forums and I've not been able to duplicate the issues. It's just that Grreg's description matches those other posts exactly.
Jul 20 at 05:38 PM
Cry Havok ♦
|
|
When you visit the DynDNS host page it'll also show you the IP address that you're browsing from - are you sure that both IP addresses on that page are the same? I don't see where it shows the IP I'm browsing from. However http://whatismyip.com returns the same address as is shown on the host services page in the details column. http://dnscog.com/dig is still returning the wrong ip address tonight... oh, I just found the page where it shows both the IP I'm browsing from and the one set in dyndns, and yes, they match.
Jul 19 at 06:27 AM
Grreg
|
|
Note that comment notification is not reliable - only use it for commenting, not for adding to an answer or providing information. I know that the other week people were reporting similar problems. Unfortunately none of them opened fault tickets with DynDNS and neither I nor DynDNS could duplicate the problem. I'd strongly recommend you open a ticket. |
1 2 next page »