[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Dnsmasq and resolvconf was Re: AAAARGHHHHH - aptitude hosed my system



On Mon, 21 Feb 2005 12:15:51 +0100
Bob Alexander <bob@ngi.it> wrote:

> > I have the package dhcp-client installed and when I comment my
static configuration and use dhcp the nameserver information is added
and removed by resolvconf when I ifup and ifdown the interface. 
> > 
> > I have not used dnsmasq but after reading up on it, it seems to me
it would make more sense to...
> > 
> > Disable the DHCP server on the router.
> > Use a static configuration on the machine with dnsmasq installed.
> > Use dnsmasq as the DHCP server for the other machines on the
network.
> > 
> 
> I do not fully understand your email. My setup (with the DHCP server
on 
> the router) works absolutely fantastically for me ... I travel with
this 
> laptop from home to office and dhclient, ifup/down, ifplugd, dnmasq, 
> resolvconf take care of everything as I expect.
> 
> Thank you.
> 
> Bob
> 

My understanding of networking issues is relatively limited, but the way
things should work...

If your networked machines all get their network configuration through
DHCP and the DHCP server is the one on the router, then they should get
the DNS numbers of the DNS server(s) the router connects to.

>From reading the package description of dnsmasq, I see it being a
benefit when you set it up on a single machine to handle DNS for your
local network and to query the DNS servers on the internet and forward
the response to the local machines as necessary.

For staticly configured machines on your local network you would set
them to use the machine with dnsmasq installed as the nameserver and add
their ip number and name to the hosts file on the computer where dnsmasq
is installed, then they should be able to access the internet sites by
name as well as accessing other local machines by name.

If dnsmasq is used as the DHCP server, then when it gives a client
machine it's address it should also be able to pick up it's name so it
can provide DNS translation for that address/name pairing to the rest of
the local machines and they can then access DHCP configured computers by
name, without having to make sure those computers get the same address
every time and having them listed permanently in your hosts file on the
machine where dnsmasq is installed.

For all of this to work to it's full potential with DHCP configured
machines you would need to:

> > Disable the DHCP server on the router.
> > Use a static configuration on the machine with dnsmasq installed.
> > Use dnsmasq as the DHCP server for the other machines on the
network.

If it is not a benefit for you to do above things, I do not see a reason
to have dnsmasq installed on any of your machines and certainly not on a
laptop, but if it is installed and things are working the words 'if it's
not broke don't fix it' come to mind. ;)

Later, Seeker



Reply to: