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
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
dnsmasq is capable of being the first DNS for clients and determining which
requests should go to the AD controller and which to external DNS. Or, the
configuration you describe is also possible.
Where Ravi appears to have gone wrong is in thinking that /etc/resolv.conf
addresses would be sent
On 08/05/2017 11:43 AM, /dev/rob0 wrote:
Yes, there is an option you can use in dnsmasq.conf to change the
nameserver[s] given to DHCP clients, but why do you want that? See the
dnsmasq(8) manual for details.
one possibility is on an AD network where all device DNS lookups go through the
AD
On Fri, Aug 04, 2017 at 09:53:52PM -0700, Anoop Ravi wrote:
> I am using dnsmasq as dns and dhcp server on my device. Somehow
> dnsmasq is not giving correct dns server address to my clients.
> Instead it is giving default gateway ip. I have correct dns servers
> listed in resolv.conf and my
