Is dnsmasq important for dhcp to setup dns?
That question is a bit confused... dnsmasq is a combined dns and dhcp sever, whether it's important depends on whether you're using it for anything.. What are you actually trying to do?
Just trying to have my dhcp set my dns which it is not doing anymore. It is driving me crazy.
dnsmasq may be a good replacement for your existing DNS and DHCP servers, then. It handles both in one program. It's also very small and simple. The config file comes with plenty of examples.
It's also smart enough to figure out some settings itself -- i.e. when it's configured as a DNS and DHCP server together, dnsmasq will assume it should append its own IP as a DNS server over DHCP.
---------- Post updated at 05:10 PM ---------- Previous update was at 05:06 PM ----------
My own server has only one network card, configured with a static IP of 192.168.0.126. It serves DNS and DHCP over the local subnet, and connects to the internet through a gateway address of 192.168.0.1. Here's the dnsmasq.conf it uses with most comments stripped out:
# Never forward plain names (without a dot or domain part)
domain-needed
# Never forward addresses in the non-routed address spaces.
bogus-priv
# Give out IP's between 192.168.0.129 and 192.168.0.254
dhcp-range=192.168.0.129,192.168.0.254,255.255.255.0,12h
# Default gateway of 192.168.0.1
dhcp-option=3,192.168.0.1
# OPTIONAL: What files to load when PXE booting.
# dhcp-boot=pxelinux.0,mecgentoo,192.168.0.126
# OPTIONAL: You need TFTP for PXE booting.
# enable-tftp
# tftp-root=/tftproot