ping and host

I have the hereafter results regarding ping and host.
Fine for 'ping' but what does 'host' return means ?

[root@pc34ghz ~]# ping www.google.com
PING www.l.google.com (216.239.59.99) 56(84) bytes of data.
64 bytes from 216.239.59.99: icmp_seq=0 ttl=237 time=35.6 ms
64 bytes from 216.239.59.99: icmp_seq=1 ttl=237 time=35.6 ms

[root@pc34ghz ~]# host www.google.com
www.google.com is an alias for www.l.google.com.
www.l.google.com has address 216.239.59.147
www.l.google.com has address 216.239.59.99
www.l.google.com has address 216.239.59.104
www.l.google.com has address 216.239.59.103
;; Warning: Message parser reports malformed message packet.
;; connection timed out; no servers could be reached

Cheers,
Bruno

On Sun, 04 Sep 2005 22:28:05 +0200, Bruno Costacurta wrote:
> I have the hereafter results regarding ping and host.
> Fine for 'ping' but what does 'host' return means ?
>
> [root@pc34ghz ~]# ping www.google.com
> PING www.l.google.com (216.239.59.99) 56(84) bytes of data.
> 64 bytes from 216.239.59.99: icmp_seq=0 ttl=237 time=35.6 ms
> 64 bytes from 216.239.59.99: icmp_seq=1 ttl=237 time=35.6 ms
>
> [root@pc34ghz ~]# host www.google.com
> www.google.com is an alias for www.l.google.com.
> www.l.google.com has address 216.239.59.147
> www.l.google.com has address 216.239.59.99
> www.l.google.com has address 216.239.59.104
> www.l.google.com has address 216.239.59.103
> ;; Warning: Message parser reports malformed message packet.
> ;; connection timed out; no servers could be reached

guessing an overloaded DNS server or realy bad connection somewhere.

host www.google.com
www.google.com is an alias for www.l.google.com.
www.l.google.com has address 64.233.161.147
www.l.google.com has address 64.233.161.99
www.l.google.com has address 64.233.161.104
www.google.com is an alias for www.l.google.com.
www.google.com is an alias for www.l.google.com.

check each dns server
cat /etc/resolv.conf

host www.google.com dns_ip_here_to_test
or
dig www.google.com dns_ip_here_to_test

Bit Twister wrote:

> On Sun, 04 Sep 2005 22:28:05 +0200, Bruno Costacurta wrote:
>> I have the hereafter results regarding ping and host.
>> Fine for 'ping' but what does 'host' return means ?
>>
>> [root@pc34ghz ~]# ping www.google.com
>> PING www.l.google.com (216.239.59.99) 56(84) bytes of data.
>> 64 bytes from 216.239.59.99: icmp_seq=0 ttl=237 time=35.6 ms
>> 64 bytes from 216.239.59.99: icmp_seq=1 ttl=237 time=35.6 ms
>>
>> [root@pc34ghz ~]# host www.google.com
>> www.google.com is an alias for www.l.google.com.
>> www.l.google.com has address 216.239.59.147
>> www.l.google.com has address 216.239.59.99
>> www.l.google.com has address 216.239.59.104
>> www.l.google.com has address 216.239.59.103
>> ;; Warning: Message parser reports malformed message packet.
>> ;; connection timed out; no servers could be reached
>
> guessing an overloaded DNS server or realy bad connection somewhere.
>
> host www.google.com
> www.google.com is an alias for www.l.google.com.
> www.l.google.com has address 64.233.161.147
> www.l.google.com has address 64.233.161.99
> www.l.google.com has address 64.233.161.104
> www.google.com is an alias for www.l.google.com.
> www.google.com is an alias for www.l.google.com.
>
> check each dns server
> cat /etc/resolv.conf
>
> host www.google.com dns_ip_here_to_test
> or
> dig www.google.com dns_ip_here_to_test

But the DNS looks fine. In fact they're working on my previous config wich
is an ADSL modem.
Now I just installed a Wireless modem router (using same DNS) but received
the herebefore problems.
I cannot see why same DNS produce different results.

> I have the hereafter results regarding ping and host.
> Fine for 'ping' but what does 'host' return means ?
>
> [root@pc34ghz ~]# ping www.google.com
> PING www.l.google.com (216.239.59.99) 56(84) bytes of data.
> 64 bytes from 216.239.59.99: icmp_seq=0 ttl=237 time=35.6 ms
> 64 bytes from 216.239.59.99: icmp_seq=1 ttl=237 time=35.6 ms
>
> [root@pc34ghz ~]# host www.google.com
> www.google.com is an alias for www.l.google.com.
> www.l.google.com has address 216.239.59.147
> www.l.google.com has address 216.239.59.99
> www.l.google.com has address 216.239.59.104
> www.l.google.com has address 216.239.59.103
> ;; Warning: Message parser reports malformed message packet.
> ;; connection timed out; no servers could be reached
>
> Cheers,
> Bruno

Hi,

perhaps it is a "DNS-loadbalancing" ?

greetings
ruediger

Ruediger Grimm wrote:

>> I have the hereafter results regarding ping and host.
>> Fine for 'ping' but what does 'host' return means ?
>>
>> [root@pc34ghz ~]# ping www.google.com
>> PING www.l.google.com (216.239.59.99) 56(84) bytes of data.
>> 64 bytes from 216.239.59.99: icmp_seq=0 ttl=237 time=35.6 ms
>> 64 bytes from 216.239.59.99: icmp_seq=1 ttl=237 time=35.6 ms
>>
>> [root@pc34ghz ~]# host www.google.com
>> www.google.com is an alias for www.l.google.com.
>> www.l.google.com has address 216.239.59.147
>> www.l.google.com has address 216.239.59.99
>> www.l.google.com has address 216.239.59.104
>> www.l.google.com has address 216.239.59.103
>> ;; Warning: Message parser reports malformed message packet.
>> ;; connection timed out; no servers could be reached
>>
>> Cheers,
>> Bruno
>
> Hi,
>
> perhaps it is a "DNS-loadbalancing" ?
>
> greetings
> ruediger
>
>

Why do you mean by a "DNS-loadbalancing" ?

However the problem I mentioned here appears with a Wireless ADSL
Router. I never had these problems with my previous modem (and same DSN
settings).

Bruno Costacurta wrote:
> Ruediger Grimm wrote:
>
>
>>>I have the hereafter results regarding ping and host.
>>>Fine for 'ping' but what does 'host' return means ?
>>>
>>>[root@pc34ghz ~]# ping www.google.com
>>>PING www.l.google.com (216.239.59.99) 56(84) bytes of data.
>>>64 bytes from 216.239.59.99: icmp_seq=0 ttl=237 time=35.6 ms
>>>64 bytes from 216.239.59.99: icmp_seq=1 ttl=237 time=35.6 ms
>>>
>>>[root@pc34ghz ~]# host www.google.com
>>>www.google.com is an alias for www.l.google.com.
>>>www.l.google.com has address 216.239.59.147
>>>www.l.google.com has address 216.239.59.99
>>>www.l.google.com has address 216.239.59.104
>>>www.l.google.com has address 216.239.59.103
>>>;; Warning: Message parser reports malformed message packet.
>>>;; connection timed out; no servers could be reached
>>>
>>>Cheers,
>>>Bruno
>>
>>Hi,
>>
>>perhaps it is a "DNS-loadbalancing" ?
>>
>>greetings
>>ruediger
>>
>>
>
>
> Why do you mean by a "DNS-loadbalancing" ?
>
> However the problem I mentioned here appears with a Wireless ADSL
> Router. I never had these problems with my previous modem (and same DSN
> settings).

This isnt a "problem" at all - It looks to me as if it's all working okay.

DNS load balancing means (in this case) that google have defined more
than one IP address for the www.l.google.com host. The idea being that
clients will choose one of the supplied IPs at random - so the "load" on
the servers is evenly distributed.

The reason you see different results with different routers will be
because of the routers internal DNS servers' different behaviours.

I presume you have configured the ADSL router as the DNS server for your
workstations, or that DHCP is doing this for you - yes?

The wireless ADSL router is giving you all the IPs returned by the "real
world" DNS servers, but your previous modem was making it's own random
choice, and giving you just that one IP. Both approaches are okay,
although the old modem isnt playing the whole game.

Chris

--
Using linux, IpTables and Rope to filter P2P and other complex
protocols.. http://www.lowth.com/rope

>>>Hi,
>>>
>>>perhaps it is a "DNS-loadbalancing" ?
>>>
>>>greetings
>>>ruediger
>>>
>>
>> Why do you mean by a "DNS-loadbalancing" ?
>>
>> However the problem I mentioned here appears with a Wireless ADSL
>> Router. I never had these problems with my previous modem (and same DSN
>> settings).
>
> This isnt a "problem" at all - It looks to me as if it's all working okay.
>
> DNS load balancing means (in this case) that google have defined more
> than one IP address for the www.l.google.com host. The idea being that
> clients will choose one of the supplied IPs at random - so the "load" on
> the servers is evenly distributed.
>
> The reason you see different results with different routers will be
> because of the routers internal DNS servers' different behaviours.
>
> I presume you have configured the ADSL router as the DNS server for your
> workstations, or that DHCP is doing this for you - yes?
>
> The wireless ADSL router is giving you all the IPs returned by the "real
> world" DNS servers, but your previous modem was making it's own random
> choice, and giving you just that one IP. Both approaches are okay,
> although the old modem isnt playing the whole game.
>
> Chris
>
> --
> Using linux, IpTables and Rope to filter P2P and other complex
> protocols.. http://www.lowth.com/rope

Indeed you're right.
I tried another ADSL router and received same time out, but in this case,
browsing is working fine.
So I have to look in another direction for the problem I still have with a
not working efficiently router D-Link DSL-G604T.

Bruno Costacurta wrote:

>>>>Hi,
>>>>
>>>>perhaps it is a "DNS-loadbalancing" ?
>>>>
>>>>greetings
>>>>ruediger
>>>>
>>>
>>> Why do you mean by a "DNS-loadbalancing" ?
>>>
>>> However the problem I mentioned here appears with a Wireless ADSL
>>> Router. I never had these problems with my previous modem (and same DSN
>>> settings).
>>
>> This isnt a "problem" at all - It looks to me as if it's all working
>> okay.
>>
>> DNS load balancing means (in this case) that google have defined more
>> than one IP address for the www.l.google.com host. The idea being that
>> clients will choose one of the supplied IPs at random - so the "load" on
>> the servers is evenly distributed.
>>
>> The reason you see different results with different routers will be
>> because of the routers internal DNS servers' different behaviours.
>>
>> I presume you have configured the ADSL router as the DNS server for your
>> workstations, or that DHCP is doing this for you - yes?
>>
>> The wireless ADSL router is giving you all the IPs returned by the "real
>> world" DNS servers, but your previous modem was making it's own random
>> choice, and giving you just that one IP. Both approaches are okay,
>> although the old modem isnt playing the whole game.
>>
>> Chris
>>
>> --
>> Using linux, IpTables and Rope to filter P2P and other complex
>> protocols.. http://www.lowth.com/rope
>
> Indeed you're right.
> I tried another ADSL router and received same time out, but in this case,
> browsing is working fine.
> So I have to look in another direction for the problem I still have with a
> not working efficiently router D-Link DSL-G604T.
>

Finally it's working : MTU value was incorrect.

Checking using another working wireless router ADSL I found that MTU was
updated after an ISP probing with different value.
As I setup the correct value on previous non-working D-Link for the MTU
(1458 versus 1500 in my case) everything works fine.

Bruno