[sf-lug] curious name resolving problem

[Alex Kleider]

alex at dp8:~$ cat /etc/resolv.conf
domain sonic.net
search sonic.net
nameserver 10.0.0.2
alex at dp8:~$ 

changed /etc/resolv.conf to be
"""
domain sonic.net
search sonic.net
nameserver 208.201.224.33
nameserver 208.201.224.11
nameserver 10.0.0.2
"""
and now it all works fine.

I still don't understand why the other programs could cope and ssh couldn't.
(And would very much like to know.  Could it have something to do with Cache?)

Thanks for steering me in the right direction.


a_kleider at yahoo.com

--- On Sun, 2/24/13, jim <jim at systemateka.com> wrote:

From: jim <jim at systemateka.com>
Subject: Re: [sf-lug] curious name resolving problem
To: alex at kleico.net
Cc: sf-lug at linuxmafia.com
Date: Sunday, February 24, 2013, 11:18 AM



    (assuming you're using the same system and you 
get the same results) please 
$ cat /etc/resolv.conf 
and share the contents. 

    perhaps reboot blindly and hope things work--
I find this a useful approach (you have to be 
comfortable with "to hell with understanding why..). 



On Sun, 2013-02-24 at 10:46 -0800, Alex Kleider wrote:
> I've got a puzzling situation in which ping works but ssh can't
> resolve a url.
> Can anyone suggest how this can be? I reckon if I understood that, I
> might be able to fix it.
> 
> Here's the evidence:
> """alex at dp8:~$ ping kleico.net
> PING kleico.net (76.191.206.83) 56(84) bytes of data.
> 64 bytes from 76-191-206-83.dsl.dynamic.sonic.net (76.191.206.83):
> icmp_req=1 ttl=251 time=21.6 ms
> 64 bytes from 76-191-206-83.dsl.dynamic.sonic.net (76.191.206.83):
> icmp_req=2 ttl=251 time=21.5 ms
> 64 bytes from 76-191-206-83.dsl.dynamic.sonic.net (76.191.206.83):
> icmp_req=3 ttl=251 time=20.8 ms
> ^C
> --- kleico.net ping statistics ---
> 3 packets transmitted, 3 received, 0% packet loss, time 2002ms
> rtt min/avg/max/mdev = 20.895/21.379/21.668/0.383 ms
> alex at dp8:~$ ssh -p5223 kleico.net
> ssh: Could not resolve hostname kleico.net: No address associated with
> hostname
> alex at dp8:~$ ssh -p5223 76.191.206.83
> alex at 76.191.206.83's password: 
> """
> I've googled "ssh fails to resolve url" but only find references to
> situations when all resolving function fails, not when it seems to
> affect only ssh.  Firefox resolves kleico.net satisfacorily as does
> w3m:
> """
> w3m http://kleico.net:5162
> """
> Can anyone shed some light?  It would be appreciated.
> alex
> ps Apologies to Rick for using "Security by Obscurity":-)  I was doing
> it before I first heard you disparage the practice and just simply
> never switched back- mainly because it's a way of getting to specific
> machines when there are more than one on the network.
> a_kleider at yahoo.com
> _______________________________________________
> sf-lug mailing list
> sf-lug at linuxmafia.com
> http://linuxmafia.com/mailman/listinfo/sf-lug
> Information about SF-LUG is at http://www.sf-lug.org/



_______________________________________________
sf-lug mailing list
sf-lug at linuxmafia.com
http://linuxmafia.com/mailman/listinfo/sf-lug
Information about SF-LUG is at http://www.sf-lug.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://linuxmafia.com/pipermail/sf-lug/attachments/20130224/eb728058/attachment.html>