In response to Jack's queries:

#netstat -rn
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt
Iface
10.24.156.1     0.0.0.0         255.255.255.255 UH        0 0          0
eth1
10.24.156.0     0.0.0.0         255.255.254.0   U         0 0          0
eth1
0.0.0.0         10.24.156.1     0.0.0.0         UG        0 0          0
eth1

# ping www.google.com
PING www.l.google.com (64.233.169.106) 56(84) bytes of data.
64 bytes from yo-in-f106.1e100.net (64.233.169.106): icmp_seq=1 ttl=239
time=123 ms
64 bytes from yo-in-f106.1e100.net (64.233.169.106): icmp_seq=2 ttl=239
time=116 ms
^C
--- www.l.google.com ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1274ms
rtt min/avg/max/mdev = 116.044/119.553/123.063/3.526 ms


Curiously, my problem seems to only occur with some domain names. My homebox
has issues, but I can SSH into another computer by domain name with no
problems.

On Thu, Dec 31, 2009 at 3:05 AM, Aura Ura <[email protected]> wrote:

> Hello,
>
> I have a very similar problem, with the same hardware, although I am on a
> wireless network. Pinging my homebox by IP address and domain name works,
> but for some reason, SSH only works when I use the IP address, not the
> domain name. However, my web browser is fine. My resolv.conf also contains
> the single line "nameserver 127.0.0.1"
>
> Here is the output of nslookup www.google.com:
> # nslookup www.google.com
> Server:        127.0.0.1
> Address:    127.0.0.1#53
>
> Non-authoritative answer:
> www.google.com    canonical name = www.l.google.com.
> Name:    www.l.google.com
> Address: 64.233.169.147
> Name:    www.l.google.com
> Address: 64.233.169.105
> Name:    www.l.google.com
> Address: 64.233.169.99
> Name:    www.l.google.com
> Address: 64.233.169.106
> Name:    www.l.google.com
> Address: 64.233.169.103
> Name:    www.l.google.com
> Address: 64.233.169.104
>
> nslookup on my home's domain name also works fine.
>
> This is the error message I get when I try to SSH:
> ssh: Could not resolve hostname <home's domain name>: Name or service not
> known
>
> Some additional info: This problem only occurs on the specific network I am
> on. It hasn't come up on any other network.
>
>
> On Thu, Dec 31, 2009 at 1:29 AM, Li, Yan <[email protected]> wrote:
>
>> On Thu, Dec 31, 2009 at 06:34:27AM +0800, Michael Heath wrote:
>> > Hi all,
>> >
>> > I'm using a Dell Inspiron Mini 9 with wired networking and the most
>> > current Moblin 2.1 image. The connection manager seems to setup the
>> > device fine, get a DHCP lease, and configure everything great.
>> > ifconfig shows the configuration exactly as I'd expect it to be, as
>> > does route. Also, when I use 'ping' on the console, everything works
>> > GREAT - I can resolve and ping any hostname or IP address on my
>> > network and elsewhere.
>> >
>> > However, thats just ping. Everything else (yum on the console, the web
>> > browser, everything else I've been able to find) refuses to resolve
>> > domain names.
>>
>> What's the error message? Please install bind-utils package and try:
>>
>>    # nslookup www.google.com
>>
>> and post the result.
>>
>> --
>> Best regards,
>> Li, Yan
>>
>> Moblin Team, Opensource Technology Center, SSG, Intel
>> Office tel.: +86-10-82171695 (inet: 8-758-1695)
>> OpenPGP key: 5C6C31EF
>> IRC: yanli on network irc.freenode.net
>> _______________________________________________
>> Moblin dev Mailing List
>> [email protected]
>>
>> To manage or unsubscribe from this mailing list visit:
>> http://lists.moblin.org/listinfo/dev or your user account on
>> http://moblin.org once logged in.
>>
>> For more information on the Moblin Developer Mailing lists visit:
>> http://moblin.org/community/mailing-lists
>>
>
>
_______________________________________________
Moblin dev Mailing List
[email protected]

To manage or unsubscribe from this mailing list visit:
http://lists.moblin.org/listinfo/dev or your user account on http://moblin.org 
once logged in.

For more information on the Moblin Developer Mailing lists visit:
http://moblin.org/community/mailing-lists

Reply via email to