Re: some dnsmasq problems
From: Peter T. Breuer (ptb_at_lab.it.uc3m.es)
Date: 11/30/04
- Previous message: buck: "Re: some dnsmasq problems"
- In reply to: buck: "Re: some dnsmasq problems"
- Next in thread: Matteo Corti: "Re: some dnsmasq problems"
- Reply: Matteo Corti: "Re: some dnsmasq problems"
- Reply: buck: "Re: some dnsmasq problems"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 30 Nov 2004 04:42:20 +0100
buck <buck@private.mil> wrote:
> On 29 Nov 2004 23:55:39 +0100, Matteo Corti <corti@inf.ethz.ch> wrote:
>
> >On 2004-11-29, Tauno Voipio <tauno.voipio@iki.fi.NOSPAM.invalid> wrote:
> >> Matteo Corti wrote:
> Content snipped.
>
> The computer on which dnsmasq runs should have a resolv.conf
> containing "nameserver 127.0.0.1" (and NOTHING ELSE) - assuming you
> want it to cache for itself as well as other computers on your LAN.
Eh? How would it know who to use as dns forwarder if that were the case?
No - it can have all it likes, PLUS 127.0.0.1. Dnsmasq reads
resolv.conf to figure out the forwarders.
-r, --resolv-file=<file>
Read the IP addresses of the upstream nameservers from
<file>, instead of /etc/resolv.conf.
> Every other computer should have a resolv.conf containing the ip of
> the dnsmasq machine in its "nameserver" line
That's right.
> I bet your DHCP is overwriting your resolv.conf file(s).
Probably.
Peter
- Previous message: buck: "Re: some dnsmasq problems"
- In reply to: buck: "Re: some dnsmasq problems"
- Next in thread: Matteo Corti: "Re: some dnsmasq problems"
- Reply: Matteo Corti: "Re: some dnsmasq problems"
- Reply: buck: "Re: some dnsmasq problems"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|