|FROM ||Rick Moen
|SUBJECT ||Re: [Hangout-NYLXS] DNS issues behind hotel wifi
|Quoting mrbrklyn-at-panix.com (mrbrklyn-at-panix.com):
> i tried to use unbound but unlike other times, it is not workingout of
> the box.
If so, that strongly suggests that it cannot get to the global DNS
namespace at all, because, y'know, there's really nothing to adjust in
Unbound. It pretty much just runs and works, normally.
You should be able to use dig, with knowledge of outside public
nameservers such as IPs 22.214.171.124 and 126.96.36.199, to get to the bottom of
this problem -- or at least to confirm that the situation is so broken
that the alleged connectivity is effectively useless.
> im on the road typing from starbucks so I'm not going to get
> into a long descrip right now, but it can't get a socket.
A sufficient explanation would be your hotel network blocking of
outbound traffic to 53/udp and 53/tcp outside the network IPs that
include _their_ namesevers. Obviously, that's a speculation, as I lack
data. And FWIW, that would be an odd thing to do, and I've never seen
it done, but I've heard of claims of it happening.
It would be reassuring to confirm that everything works on _other_
networks, such as perhaps the Starbucks one.
Cheers, Luftputebåten min er full av ål.
hangout mailing list