Forums

Resolved
0 votes
Hi,

We have a ClearOS 6.7 server that has been runnign fine for several year.

However, the other day, when I'm in the webconfig and in DNS I get an error if I make any change. It says 'Command Execution Failure'. If I manually try to restart dnsmasq I get "DNSmasq: failed to bind DHCP socket: Address already in use".

DHCP still appears to work as does everything else - just cannot make any changes.

Any ideas?

Roger
Wednesday, October 19 2016, 05:05 AM
Share this post:
Responses (8)
  • Accepted Answer

    Wednesday, October 19 2016, 06:51 PM - #Permalink
    Resolved
    0 votes
    Hi Nick,

    Thanks for the suggestions. I tried commenting out all the extra stuff (which is not new - been there for years) and same thing. The extra DNS server is AD - you are correct. Might have a more aggressive fiddle with it next week when users are not in school (might zap to 7.2 - should not take long). At least as far as users are concerned its all working - as I said quite possibly been like this for a long time. Interesting tip about putting modifications into a different file - thanks.

    Roger
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, October 19 2016, 06:16 PM - #Permalink
    Resolved
    0 votes
    You've done more changes than that. I think a basic file looks something like:
    bogus-priv
    conf-dir=/etc/dnsmasq.d
    dhcp-authoritative
    dhcp-lease-max=1000
    domain-needed
    domain=howitts.co.uk
    expand-hosts
    no-negcache
    resolv-file=/etc/resolv-peerdns.conf
    strict-order
    user=nobody
    I also made changes but I think this is the 6.x original. You've add an alternative DNS server for your LAN devices (for AD?) and made a few other tweaks.

    FWIW, I recently realised that if you want to make additions to the file you can make them to a file /etc/dnsmasq.d/anything.conf which will separate your additions from the base file. dnsmasq does, however, complain if you repeat a parameter in different files.
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, October 19 2016, 05:59 PM - #Permalink
    Resolved
    0 votes
    Hi,

    I tried commenting out that line (used as we images PCs with FOG (on a ubuntu server - the 192.168.10.8) - which works fine). Got the same error - so must be something else. However, everything appears to be working fine and its possibly been like this for months as I seldom touch the server. This one runs 6.7 - we also have a newer 7.2 gateway which does not have the issue - so maybe time to rebuild unless there are any other suggestions (have not rebooted - but might do next week as people on hols).

    Thanks,

    Roger
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, October 19 2016, 04:06 PM - #Permalink
    Resolved
    0 votes
    It looks like you have made some changes and configured a PXE server. Have you tried removing your changes to see if it then works?
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, October 19 2016, 12:45 PM - #Permalink
    Resolved
    0 votes
    Hi,

    bogus-priv
    cache-size=10000
    conf-dir=/etc/dnsmasq.d
    dhcp-authoritative
    dhcp-boot=undionly.kpxe,image.wps.local,192.168.10.8
    dhcp-lease-max=4000
    dns-forward-max=5000
    domain-needed
    domain=wps.local
    enable-tftp
    expand-hosts
    no-negcache
    port=53
    resolv-file=/etc/resolv-peerdns.conf
    server=/wps.local/192.168.10.2
    strict-order
    user=nobody

    Is the content of the file.

    Roger
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, October 19 2016, 12:37 PM - #Permalink
    Resolved
    0 votes
    That looks OK. DNS generally uses UDP:53 but can fall back to TCP:53 if the UDP replies are bigger than 512 bytes. Then you have IPv4 and IPv6.

    I have no idea what could be causing the error as nothing else is listening on 53.

    What is the contents of /etc/dnsmasq.conf?
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, October 19 2016, 11:40 AM - #Permalink
    Resolved
    0 votes
    Hi Nick,
    Thanks for the reply. The output is:
    netstat -tulpn | grep ':53'
    tcp 0 0 0.0.0.0:53 0.0.0.0:* LIST EN 32401/dnsmasq
    tcp 0 0 :::53 :::* LIST EN 32401/dnsmasq
    udp 0 0 0.0.0.0:53 0.0.0.0:* 32401/dnsmasq
    udp 0 0 :::53 :::*

    Don't know why there are several entries for dnsmasq - looking at the process viewer there is only on dnsmasq listed.
    Roger
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, October 19 2016, 11:27 AM - #Permalink
    Resolved
    0 votes
    Is anything else listening on port 53? What is the output of:
    netstat -tulpn | grep ':53'
    The reply is currently minimized Show
Your Reply