If it doesn't work when started at boot, but does if you started it manually, the most likely reason is that the boot scripts are passing command-line options such as a different config file. If you edited the default config file, when you start dnsmasq by hand, that's the one it finds. The
Thank you for the Info. I dont need dhcp-option 6 to be enabled. On packet capture, I can see DNS query going to dnsmasq, then to nameserver. The response from name server is going directly to the client instead of dnsmasq. Client is getting response as Refused. Any clue on what is happening?
The default configuration of dnsmasq is to act as a caching proxy server (this behavior of dnsmasq has existed before dhcp support). There are a few reasons the proxying could fail, chief among them being firewall rules. If that isn't the problem, increasing the logging detail may give further
Hi, Richard, As you said, I was under an impression that dnsmasq will provide all the nameserver entries in resolv.conf to the clients. Thank you for correcting me. But, my clients are not resoving the names with this configuration. It is getting correct domain name and server ip as dns