/etc/resolv.conf advice
- From: Chris <see@xxxxxxxxxxxxxx>
- Date: Fri, 26 Aug 2005 15:17:02 +0100
Hi,
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?
If I edit resolv.conf to manually input my ISPs DNS server, all commands
work fine again. However, the moment i restart networking, the
resolv.conf entry is reset by DHCP to 192.168.2.1. I know I could go
inet static, but i'd prefer DHCP really.
So, my question is this:
a) What has happened to stop host and dig resolving using 192.168.2.1?
b) How can I get resolv.conf to not grab its DNS servers from DHCP
anymore?
Cheers for any help!
--
Chris
.
- Follow-Ups:
- Re: /etc/resolv.conf advice
- From: Nix
- Re: /etc/resolv.conf advice
- From: Robert Harris
- Re: /etc/resolv.conf advice
- From: Jim Howes
- Re: /etc/resolv.conf advice
- From: Justin C
- Re: /etc/resolv.conf advice
- Prev by Date: Re: Slackware install: Grub 15 error on bootup
- Next by Date: Re: /etc/resolv.conf advice
- Previous by thread: Slackware install: Grub 15 error on bootup
- Next by thread: Re: /etc/resolv.conf advice
- Index(es):
Relevant Pages
|