Incorrect DNS resolutions
I've got a funny problem with DNS resolution. I'm away from home staying in a Hotel which supplies internet to each room via ethernet. An address is assigned via DHCP and a DNS server is also supplied from DHCP.
However, on trying to access any domain name (via ping, Firefox, anything), especially for the first time, often an incorrect IP is returned -- always 169.254.1.1. Of course, google.com isn't at 169.254.1.1 so the connection will time out.
If I type in the correct IP (obtained from calling ping a few times until it returns something other than 169.254.1.1) then it will work perfectly.
Now, the odd thing, is that even if I supply an alternative DNS server (for example, Google's 184.108.40.206 and 220.127.116.11, or even the DNS servers from my home ISP), it still performs the same behaviour. How could the hotel's router affect that?
Typing in `route' shows nothing out of the ordinary in the routing table.
When I'm on-site at work (as I am now), the ethernet connection works perfectly and shows the same routing table (just a different gateway).
Does anybody have any idea what is going on?
For reference, I'm running Ubuntu 10.04 with Gnome's network manager. However my co-workers Windows laptop appears to be producing the same behaviour in the same hotel.