Stefan O. Montenejo wrote:

Just an update:

When I went for the port=53 configuration, my file server (samba) didn't work. But I went for the port=0 configuration, everything seems to be working.

I have a hunch that SAMBA installation did something to the server. (This might be helpful for the DEVS).

Yes, very helpful! I saw a Samba Directory notification about this same topic go through the tracker. It will be fixed relatively soon.

Just an update:

When I went for the port=53 configuration, my file server (samba) didn't work. But I went for the port=0 configuration, everything seems to be working.

I have a hunch that SAMBA installation did something to the server. (This might be helpful for the DEVS).


Thanks and more power to ClearOS!

Nick Howitt wrote:

Reading the man page for dnsmasq.conf, setting port to 0 disables the DNS function. Normally you would not need this and I am not sure why it is there. Try setting port to 0 rather than 68. I *think* the DHCP should be listening on 67 and answering from 68 but I could have this wrong.

In which mode are you running samba/windows networking? Have you tweaked samba at all, because I think it can be configured to act as a DNS server. Also setting it as a domain controller could conceivably interfere with dnsmasq.

[edit]
If samba is an AD domain controller then it is probably taking over DNS functions. You could have a bug that "port" is being incorrectly set (should be set to 0) when Samba in an AD DC.
[/edit]

I did install another ClearOS to a virtualbox just to inspect the dnsmasq.conf config and by default it said port=53. I tried changing it on a live machine but dnsmasq service fails to start on a port 53 (on a "service dnsqmasq start" command). I tried to restart the server with the port 53 setting and it did work today. (I did notice the DHCP update by clearOS so I think they may have solved the problem).

I did try setting it to port=0 and it worked! DHCP is acting normally. Thank you! I'll keep this in mind in case I run into troubles again.

All is working now. Thank you!

regarding samba, I did not tweak any of its configurations by hand. I mainly use samba only as my file server.

Anyway, thank you Nick Howitt for the solutions!

Reading the man page for dnsmasq.conf, setting port to 0 disables the DNS function. Normally you would not need this and I am not sure why it is there. Try setting port to 0 rather than 68. I *think* the DHCP should be listening on 67 and answering from 68 but I could have this wrong.

In which mode are you running samba/windows networking? Have you tweaked samba at all, because I think it can be configured to act as a DNS server. Also setting it as a domain controller could conceivably interfere with dnsmasq.

[edit]
If samba is an AD domain controller then it is probably taking over DNS functions. You could have a bug that "port" is being incorrectly set (should be set to 0) when Samba in an AD DC.
[/edit]

Nick Howitt wrote:

I don't know the cause of your error, but note that port 53 is normally for DNS lookup and 67/68 for DHCP.

Hi, I have checked the ports earlier and SAMBA server is using it. I remembered that I installed flexshare.. configured samba... everything seems to work fine.. then as soon as I rebooted my server, DHCP was failing to start. (the port was missing in the dnsmasq.conf). I then tried editing the config file and used port 53 but still no luck. then I tried port 68 and it seems to have solved my problem.

For now, DHCP is handing out IPs using the port 68. Im not sure if that is normal though. I'll try reverting it back to 53 and see of its working.

I don't know the cause of your error, but note that port 53 is normally for DNS lookup and 67/68 for DHCP.