linux-admin.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Schulman <andrex-cmaem7PIVQQM4YKboWzA4l6hYfS7NtTn@public.gmane.org>
To: linux-admin-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: DNS caching nameserver problem
Date: Mon, 30 May 2005 22:05:32 -0400	[thread overview]
Message-ID: <d7ggka$qjl$1@sea.gmane.org> (raw)
In-Reply-To: 84bd26ef050530112422641001@mail.gmail.com


>> I have a DNS caching server that works ok until
>> it is rebooted. When this happens it restarts
>> normally, except the /etc/resolv.conf file is
>> altered and the server stops serving names. (The
>> line 'nameserver 127.0.0.1' is missing and other
>> namservers appear instead).
>> 
>> The server obtains an address through DHCP and my
>> theory is that the DHCP server is providing it
>> with DNS servers as well, which it substitutes
>> when it probably shouldn't.
>> 
>> I have tried a horrible patch in rc.local,
>> stopping named, overwriting resolv.conf with a
>> correct copy and restarting, but
>> editing the file and restarting 'named' does not
>> seem to work 100% of the time, requiring
>> sometimes one or two restarts of the service to
>> make it serve names for the internal hosts.
>> 
>> What do you think is the problem?
>> Is there a workaround?
> 
>   Yes, the problem is that your DHCP client is overwriting the
> resolv.conf file. How to avoid this, as far as I know, is
> distribuition specific. What distribution do you have?

pump, for example, includes an option --no-dns that tells it not to
overwrite /etc/resolv.conf.  I use this along with my cacheing DNS server. 
I put 'nameserver 127.0.0.1' into /etc/resolv.conf, then I have pump run a
postprocessing script that extracts the DNS server information and writes
it to /etc/dnsmasq.conf, where dnsmasq (my cacheing name server) looks to
find the upstream DNS servers.

Good luck,
Andrew.


-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2005-05-31  2:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-30 17:51 DNS caching nameserver problem gerardo juarez-mondragon
2005-05-30 18:24 ` Darío Mariani
2005-05-31  2:05   ` Andrew Schulman [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='d7ggka$qjl$1@sea.gmane.org' \
    --to=andrex-cmaem7pivqqm4ykbowza4l6hyfs7nttn@public.gmane.org \
    --cc=linux-admin-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).