DNS Disarray

Now this is weird. I just tried accessing my webcams back home over my hotel-supplied Internet connection using my DynDNS-supplied domain name, and got a timeout error. The same thing happened when I subsequently tried to pull up the laptop over VNC. Thinking I might have lost premises power some time in the past 24 hours (specifically, long enough that the UPS battery backup for my DSL modem and router had drained), and that the DynDNS client running on the laptop for some reason didn’t correctly update my account once power came back up, I tried accessing the gear via my alternative TZO dynamic DNS URL instead…which worked.

But in perusing the laptop that way, I could see that DynDNS in fact had an up-to-date AT&T DSL-supplied IP address. And, when I subsequently did ‘pings’ on both URLs here, I discovered that whereas the tzo.com URL correctly resolved, my dyndns.org domain URL resolved to 192.168.100.26…i.e. to an internal hotel LAN address.

Any idea, folks, why (presumably) either the hotel’s firewall or the DNS server of the hotel’s Internet Service Provider is mucking around with my DynDNS.org-assigned domain name? No other URL I’ve tried so far seems to fail in this way; specifically, www.dyndns.org works fine, as does another DynDNS-supplied domain I manage.

Followup: Greetings from ASUS. I’m online here using their network, and my dyndns.org domain resolves fine. So the problem’s not with my laptop; my hotel’s DNS server’s definitely the culprit.