Hi,

dnsmasq service isn't configured to start on boot, according "Server
Settings -> Services Configuration". But it's being started, as I
could see in /var/log/messages file. Anyway, as the resolution of my local system name was failing, my first idea was to configure it to start on boot. I'm getting however the error:
...
Nov 1 11:14:11 oml dnsmasq[4832]: failed to create listening socket:
Address already in use
Nov 1 11:14:11 oml dnsmasq[4832]: FAILED to start up
...
Here are the output of nslookup with my dns provider hostname, working fine, and with thelocal system name, this one not
working:

[root@oml ~]# nslookup 75.75.75.75
Server: 75.75.75.75
Address: 75.75.75.75#53

Non-authoritative answer:
75.75.75.75.in-addr.arpa name = cdns01.comcast.net.

Authoritative answers can be found from:

[root@oml ~]# nslookup oml
Server: 75.75.75.75
Address: 75.75.75.75#53

** server can't find oml: NXDOMAIN

So, I restarted the dnsmasq service from "System-> Administration -> Server Settings -> Services" and both names (and any other) have been resolved:

[root@oml ~]# nslookup 75.75.75.75
Server: 192.168.1.80
Address: 192.168.1.80#53

Non-authoritative answer:
75.75.75.75.in-addr.arpa name = cdns01.comcast.net.

Authoritative answers can be found from:

[root@oml ~]# nslookup oml
Server: 192.168.1.80
Address: 192.168.1.80#53

Name: oml.home.lab
Address: 192.168.1.80

So, restarting the service dnsmasq seems to be a valid workaround for that, even when the service isn't excplictly configured. I would like however to fix that. What am I missing here?
Thanks,
Paulo

I do not known that you are aware of dnsmasq is mainly DNS server. And I understand that you want only working DNS resolution. Even if it works now, it is not a correct solution for this problem. The first thing in that should be investigation of /etc/resolv.conf file, if it contain proper dns server IP. Of course after disabling dnsmasq.

Selix:

Thanks for your reply. Here is my resolv.conf file:
---------------------------
nameserver 192.168.1.80
nameserver 75.75.75.75
---------------------------
Where:
192.168.1.80 -> my system
75.75.75.75 -> comcast DNS

I still don't understand why if we restart the process my system name begins to be resolved fine. Looks like if it was stopped other configuration data is read.

Best Regards,
Paulo

Disable dnsmasq, then remove "nameserver 192.168.1.80" line from /etc/resolv.conf Leave only second line. If this will not work, check /etc/dnsmasq.conf for "resolv-file=" line. In my it is "/tmp/resolv.conf.auto" When you get this file copy it contents here.

eSelix: if he really wants to run a DNS server for and from his internal network, he DOES want DNSMASQ running, and on every boot.
Shutting it down and removing it from resolv.conf allows him to test his ISP DNS, but not his OWN DNS (running DNSMASQ)!

Paulo: what was the point of running DNSMASQ? Are you intending to use it for caching DNS queries, for resolving your local hosts, for providing DHCP services locally, or some combination of these?

1 members found this post helpful.