|FROM ||Rick Moen
|SUBJECT ||Re: [Hangout-NYLXS] DNS issues behind hotel wifi
|Quoting Ruben Safir (ruben-at-mrbrklyn.com):
> Why would dig be able to find and report on where www.mrbrklyn.com but
> ssh report it can't resolve it.
Technically, /usr/bin/ssh doesn't 'resolve' DNS names. It makes a
library call to libc.so.6, which includes hooks to the local nameservice
Could be a IPV4 vs IPV6 problem.
Try: ssh -4 ruben-at-www.mrbrklyn.com
Both tools, ssh and dig, have -4 and -6 switches, by the way.
Also, you said you used dig but didn't cite _how_ you used it, so I'm
guessing you didn't bother to specify a nameserver, but rather left that
to chance. Bad habit. That adds a chaos factor that tends to muddy
The IPs for Google Public DNS, 22.214.171.124 and 126.96.36.199, are useful for such
$ dig www.mrbrklyn.com -at-188.8.131.52 +short
In the long term, when you get tired of being jerked around and get
serious, start running and using a local recursive nameserver, i.e., one
bound to 127.0.0.1 and referenced that way in /etc/resolv.conf . The
Unbound software is perfect for this.
hangout mailing list