Internet: browsers fails to connect to SOME sites, not all, for no reason.

[NoOp]

On 01/28/2009 10:20 AM, Guy Thouret wrote:
> Not necessarily, what you have dug are the IP addresses of the content
> DNS servers for the numericable.fr domain.
> These probably aren't the caching servers that the ISP provide for their
> customers to resolve DNS so may cause more harm than good by adding
> these to resolv.conf. 

I was going on:

<quote>
My e-mail client (Sylpheed) fails to connect to my ISP's POP server,
(pop.numericable.fr). Sylpheed has a "debugging" window, where I can
see that it might be a DNS issue:

********
* Connecting to POP3 server: pop.numericable.fr...
** LibSylph-WARNING: DNS lookup failed
** LibSylph-WARNING: sock_connect_address_list_async: connection to
pop.numericable.fr:110 failed
** LibSylph-WARNING: can't connect to server.
** LibSylph-WARNING: [08:32:11] Connection failed.
** Connection failed.
********
</quote>

His emails are coming from:
Original-Received: from smtp2.tech.numericable.fr ([82.216.111.38])

numericable.fr uses:
nserver:     ns1.numericable.fr [82.216.111.75]
nserver:     ns2.numericable.fr [82.216.111.76]

> 
> On Wed, 2009-01-28 at 18:06 +0000, NoOp <glgxg at sbcglobal.net> wrote:
> 
>> You might check to see if your dns servers are listed in
>> /etc/resolv.conf. They should be 82.216.111.75 and 82.216.111.76.
>> 
>> ;; ANSWER SECTION:
>> numericable.fr.         548     IN      A       82.216.111.15
>> numericable.fr.         548     IN      NS      ns1.numericable.fr.
>> numericable.fr.         548     IN      NS      ns2.numericable.fr.
>> 
>> ns1.numericable.fr.     317122  IN      A       82.216.111.75
>> ns2.numericable.fr.     312318  IN      A       82.216.111.76
>> 
>> So, your 'cat /etc/resolv.conf' should look like this:
>> 
>> $ cat /etc/resolv.conf
>> nameserver 82.216.111.75
>> nameserver 82.216.111.76
> 
>