MESSAGE
DATE | 2016-07-24 |
FROM | From:
|
SUBJECT | Re: [Hangout-NYLXS] DNS issues behind hotel wifi
|
i tried to use unbound but unlike other times, it is not workingout of the box. 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. I hate this hotel.
-- Sent from my HP TouchPad __________________________________________________________________
On Jul 24, 2016 2:24 AM, Rick Moen wrote: 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 client. 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 diagnosis. The IPs for Google Public DNS, 8.8.8.8 and 8.8.4.4, are useful for such purposes, e.g.: $ dig www.mrbrklyn.com -at-8.8.8.8 +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. http://linuxmafia.com/faq/Network_Other/dns-servers.html#unbound _______________________________________________ hangout mailing list hangout-at-nylxs.com http://www.nylxs.com/ _______________________________________________ hangout mailing list hangout-at-nylxs.com http://www.nylxs.com/
|
|