Re: /etc/resolv.conf advice
On Fri, 26 Aug 2005, Chris stated:
> I have noticed something weird today on my Debian box. My
> /etc/resolv.conf file reads 'nameserver 192.168.2.1' (my gateway IP).
>
> This has worked fine for months. However, as of today, the 'host' and
> 'dig' commands are not resolving addresses - yet ping does! What on
> earth is going on there?
ping uses libc's resolver: host and dig implement their own.
Thus, ping's name lookups go through nsswitch.conf, which might be
looking up names from somewhere else (mdns/Zeroconf?)
--
`... published last year in a limited edition... In one of the
great tragedies of publishing, it was not a limited enough edition
and so I have read it.' --- James Nicoll
.
Relevant Pages
- Re: Thanks for all replies -was- Re: Entanet - not all it is made out to be.
... then to ping www.bbc.co.uk and there was a reply to the ping and that is ... for replies in the form of ICMP Echo Response packets. ... DNS resolving is done by the local PC to resolve the ... to use a proxy server, then the browser simply opens a connection to the ...
(uk.telecom.broadband) - Re: dig fails but ping works
... of a name until one resolves or until it runs out of variations. ... but that should show up with dig or host. ... % ping notl337.net. ...
(comp.os.linux.networking) - Re: How to resolve names
... So I can ping and try to ssh/telnet the 2 other machines from my PC via ... name/address resolution via nslookup. ... use dig instead, but its brokenness does not extend to returning answers ...
(comp.os.linux.networking) - Re: Thanks for all replies -was- Re: Entanet - not all it is made out to be.
... then to ping www.bbc.co.uk and there was a reply to the ping and that is ... to use a proxy server, then the browser simply opens a connection to the proxy ... (resolving the name of the proxy if required, ...
(uk.telecom.broadband) - Re: Multiple IP problems
... As far as the netmeeting thing goes i have got that solved. ... H.323 gateway service for that. ... > secondary ip wont ping but it seems to let traffic thru. ... > publishing on the secondary ip and those work fine. ...
(microsoft.public.isaserver) |
|
