ping not resolving names

[Derek Broughton]

Felipe Figueiredo wrote:

> On Thursday 26 July 2007 20:20:09 NoOp wrote:
>> On 07/26/2007 03:57 PM, Felipe Figueiredo wrote:
>> > On Thursday 26 July 2007 19:35:11 Bruce Marshall wrote:
>> > 
>> >> What is in your  /etc/resolv.conf   file?
>> > 
>> > Three valid resolvers I entered manually
> in /etc/resolvconf/resolv.conf.d/base
>> > 
>> > nameserver 201.17.0.19
>> > nameserver 146.164.10.2
>> > nameserver 192.168.1.10
>> 
>> Take out nameserver 192.168.1.10 unless of course you have dns server
>> installed on that machine.
> 
> I do have.
> 
> 
>> Also: 201.17.0.19 is not responding:
>> :~$ ping 201.17.0.19
>> PING 201.17.0.19 (201.17.0.19) 56(84) bytes of data.
>> 
>> --- 201.17.0.19 ping statistics ---
>> 6 packets transmitted, 0 received, 100% packet loss, time 5009ms
> 
> This is my ISP DNS. It is operational

Indeed it is. 

dig www.google.com @201.17.0.19
and 
dig www.google.com @146.164.10.2

both work fine for me.
>> 
>> :~$ ping 146.164.10.2
>> PING 146.164.10.2 (146.164.10.2) 56(84) bytes of data.
>> 64 bytes from 146.164.10.2: icmp_seq=1 ttl=53 time=199 ms
>> 64 bytes from 146.164.10.2: icmp_seq=2 ttl=53 time=198 ms

Pinging a nameserver doesn't help you find out if the nameserver is serving
names...

Use
dig www.google.com
and make sure that it reports the nameserver it uses as being one of the
ones you've listed - I have no experience with using resolve.conf.d, so
can't be certain you've set it correctly.
-- 
derek