MESSAGE
| DATE | 2016-07-24 |
| FROM | Rick Moen
|
| SUBJECT | Re: [Hangout-NYLXS] DNS issues behind hotel wifi
|
And, by the way, when I say it might be an IPv4 versus IPv6, I mean that
dig might be succeeding on IPv4 DNS resolution whereas ssh might be
halting on failure of IPv6 DNS resolution -- or something like that.
As a quick check, try the 'dig' command I gave, adding first the '-4' option
and then instead the '-6' option to gather information. Or, hey, try
your ssh command the same two ways.
Also, irrespective of the cause of your problem, even _if_ you aren't
following my long-term recommendation that you use a local recursive
nameserver, you should at least specify 8.8.8.8 and 8.8.4.4 (Google's
Public DNS IPs) instead of whatever lousy nameserver the wifi connection
hands out with the DHCP lease.
Caution: On some wifi networks, it is necessary to use their DNS
nameservers while making your initial connection because the 'captive
portal' Web page where you sign up and agree to their terms of use is
reachable only using the wifi network's nameservers. But after initial
connection you can use better nameservers in every case I've seen.
--
Cheers, Luftputebåten min er full av ål.
Rick Moen
rick-at-linuxmafia.com
McQ! (4x80)
_______________________________________________
hangout mailing list
hangout-at-nylxs.com
http://www.nylxs.com/
|
|
