For some reason I'm getting this:
$ systemctl status dnsmasq ● dnsmasq.service - DNS caching server. Loaded: loaded (/usr/lib/systemd/system/dnsmasq.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Mon 2016-01-25 13:27:16 GMT; 1s ago Process: 3502 ExecStart=/usr/sbin/dnsmasq -k (code=exited, status=2) Main PID: 3502 (code=exited, status=2)
Jan 25 13:27:16 bree systemd[1]: Started DNS caching server.. Jan 25 13:27:16 bree systemd[1]: Starting DNS caching server.... Jan 25 13:27:16 bree dnsmasq[3502]: dnsmasq: failed to create listening socket for port 53: Address already in use Jan 25 13:27:16 bree dnsmasq[3502]: failed to create listening socket for port 53: Address already in use Jan 25 13:27:16 bree systemd[1]: dnsmasq.service: Main process exited, code=exited, status=2/INVALIDARGUMENT Jan 25 13:27:16 bree systemd[1]: dnsmasq.service: Unit entered failed state. Jan 25 13:27:16 bree systemd[1]: dnsmasq.service: Failed with result 'exit-code'.
Can't figure out what is sitting on port 53 (the DNS port). I'm not running bind.
poc
On Mon, Jan 25, 2016 at 2:30 PM, Patrick O'Callaghan pocallaghan@gmail.com wrote:
For some reason I'm getting this:
$ systemctl status dnsmasq ● dnsmasq.service - DNS caching server. Loaded: loaded (/usr/lib/systemd/system/dnsmasq.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Mon 2016-01-25 13:27:16 GMT; 1s ago Process: 3502 ExecStart=/usr/sbin/dnsmasq -k (code=exited, status=2) Main PID: 3502 (code=exited, status=2)
Jan 25 13:27:16 bree systemd[1]: Started DNS caching server.. Jan 25 13:27:16 bree systemd[1]: Starting DNS caching server.... Jan 25 13:27:16 bree dnsmasq[3502]: dnsmasq: failed to create listening socket for port 53: Address already in use Jan 25 13:27:16 bree dnsmasq[3502]: failed to create listening socket for port 53: Address already in use Jan 25 13:27:16 bree systemd[1]: dnsmasq.service: Main process exited, code=exited, status=2/INVALIDARGUMENT Jan 25 13:27:16 bree systemd[1]: dnsmasq.service: Unit entered failed state. Jan 25 13:27:16 bree systemd[1]: dnsmasq.service: Failed with result 'exit-code'.
Can't figure out what is sitting on port 53 (the DNS port). I'm not running bind.
Unbound?
NetworkManager? (check the "dns=" line in "/etc/NetworkManager/NetworkManager.conf", if it exists.)
Check the listening ports with ss.
Allegedly, on or about 25 January 2016, Patrick O'Callaghan sent:
Can't figure out what is sitting on port 53 (the DNS port). I'm not running bind.
[root@localhost ~]# netstat -antuevp|grep 53
On Mon, 2016-01-25 at 14:37 +0100, Tom H wrote:
On Mon, Jan 25, 2016 at 2:30 PM, Patrick O'Callaghan pocallaghan@gmail.com wrote:
For some reason I'm getting this:
$ systemctl status dnsmasq ● dnsmasq.service - DNS caching server. Loaded: loaded (/usr/lib/systemd/system/dnsmasq.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Mon 2016-01-25 13:27:16 GMT; 1s ago Process: 3502 ExecStart=/usr/sbin/dnsmasq -k (code=exited, status=2) Main PID: 3502 (code=exited, status=2)
Jan 25 13:27:16 bree systemd[1]: Started DNS caching server.. Jan 25 13:27:16 bree systemd[1]: Starting DNS caching server.... Jan 25 13:27:16 bree dnsmasq[3502]: dnsmasq: failed to create listening socket for port 53: Address already in use Jan 25 13:27:16 bree dnsmasq[3502]: failed to create listening socket for port 53: Address already in use Jan 25 13:27:16 bree systemd[1]: dnsmasq.service: Main process exited, code=exited, status=2/INVALIDARGUMENT Jan 25 13:27:16 bree systemd[1]: dnsmasq.service: Unit entered failed state. Jan 25 13:27:16 bree systemd[1]: dnsmasq.service: Failed with result 'exit-code'.
Can't figure out what is sitting on port 53 (the DNS port). I'm not running bind.
Unbound?
NetworkManager? (check the "dns=" line in "/etc/NetworkManager/NetworkManager.conf", if it exists.)
There is no such line, however in the NM config options I do have nameservers set to 127.0.0.1,192.168.1.254 (my router) and normal non- local DNS queries work. Queries from elsewhere on my LAN which are configured to point at this machine just timeout.
Check the listening ports with ss.
See my reply to Tim in this thread.
poc
On Tue, 2016-01-26 at 00:34 +1030, Tim wrote:
Allegedly, on or about 25 January 2016, Patrick O'Callaghan sent:
Can't figure out what is sitting on port 53 (the DNS port). I'm not running bind.
[root@localhost ~]# netstat -antuevp|grep 53
Nothing comes up for my local machine.
poc
On Mon, 2016-01-25 at 16:46 +0000, Patrick O'Callaghan wrote:
On Tue, 2016-01-26 at 00:34 +1030, Tim wrote:
Allegedly, on or about 25 January 2016, Patrick O'Callaghan sent:
Can't figure out what is sitting on port 53 (the DNS port). I'm not running bind.
[root@localhost ~]# netstat -antuevp|grep 53
Nothing comes up for my local machine.
I figured it out (sort of). Turns out I'm running a virtual bridge network for VirtualBox on virbr0, and it was sitting on the port for some reason. Still not sure why but when I shit down that network it all started to work.
poc
On 01/25/2016 08:52 AM, Patrick O'Callaghan wrote:
On Mon, 2016-01-25 at 16:46 +0000, Patrick O'Callaghan wrote:
On Tue, 2016-01-26 at 00:34 +1030, Tim wrote:
Allegedly, on or about 25 January 2016, Patrick O'Callaghan sent:
Can't figure out what is sitting on port 53 (the DNS port). I'm not running bind.
[root@localhost ~]# netstat -antuevp|grep 53
Nothing comes up for my local machine.
I figured it out (sort of). Turns out I'm running a virtual bridge network for VirtualBox on virbr0, and it was sitting on the port for some reason. Still not sure why but when I shit down that network it all started to work.
Sometimes it takes extreme measures...
On Mon, Jan 25, 2016 at 5:52 PM, Patrick O'Callaghan pocallaghan@gmail.com wrote:
On Mon, 2016-01-25 at 16:46 +0000, Patrick O'Callaghan wrote:
On Tue, 2016-01-26 at 00:34 +1030, Tim wrote:
Allegedly, on or about 25 January 2016, Patrick O'Callaghan sent:
Can't figure out what is sitting on port 53 (the DNS port). I'm not running bind.
[root@localhost ~]# netstat -antuevp|grep 53
Nothing comes up for my local machine.
I figured it out (sort of). Turns out I'm running a virtual bridge network for VirtualBox on virbr0, and it was sitting on the port for some reason. Still not sure why but when I shit down that network it all started to work.
I'm not familiar with VirtualBox. Is virbr0 created (and used) by VirtualBox? Or did you create it manually?
Or do you have libvirt installed (it's the default libvirt bridge name)?
By default, there'll be a dns server on virbr0 for natted guests, but not for the host.
On Mon, 2016-01-25 at 10:16 -0800, mike wrote:
On 01/25/2016 08:52 AM, Patrick O'Callaghan wrote:
On Mon, 2016-01-25 at 16:46 +0000, Patrick O'Callaghan wrote:
On Tue, 2016-01-26 at 00:34 +1030, Tim wrote:
Allegedly, on or about 25 January 2016, Patrick O'Callaghan sent:
Can't figure out what is sitting on port 53 (the DNS port). I'm not running bind.
[root@localhost ~]# netstat -antuevp|grep 53
Nothing comes up for my local machine.
I figured it out (sort of). Turns out I'm running a virtual bridge network for VirtualBox on virbr0, and it was sitting on the port for some reason. Still not sure why but when I shit down that network it all started to work.
Sometimes it takes extreme measures...
oops ...
poc
On Mon, 2016-01-25 at 23:54 +0100, Tom H wrote:
On Mon, Jan 25, 2016 at 5:52 PM, Patrick O'Callaghan pocallaghan@gmail.com wrote:
On Mon, 2016-01-25 at 16:46 +0000, Patrick O'Callaghan wrote:
On Tue, 2016-01-26 at 00:34 +1030, Tim wrote:
Allegedly, on or about 25 January 2016, Patrick O'Callaghan sent:
Can't figure out what is sitting on port 53 (the DNS port). I'm not running bind.
[root@localhost ~]# netstat -antuevp|grep 53
Nothing comes up for my local machine.
I figured it out (sort of). Turns out I'm running a virtual bridge network for VirtualBox on virbr0, and it was sitting on the port for some reason. Still not sure why but when I shit down that network it all started to work.
I'm not familiar with VirtualBox. Is virbr0 created (and used) by VirtualBox? Or did you create it manually?
I believe it was created by VBox.
Or do you have libvirt installed (it's the default libvirt bridge name)?
I do, though nothing seems to depend on it. libvirtd is running, presumably as part of the standard KVM system, but AFAIK that's independent of VBox.
poc
On Tue, Jan 26, 2016 at 1:44 AM, Patrick O'Callaghan pocallaghan@gmail.com wrote:
On Mon, 2016-01-25 at 23:54 +0100, Tom H wrote:
On Mon, Jan 25, 2016 at 5:52 PM, Patrick O'Callaghan pocallaghan@gmail.com wrote:
I figured it out (sort of). Turns out I'm running a virtual bridge network for VirtualBox on virbr0, and it was sitting on the port for some reason. Still not sure why but when I shit down that network it all started to work.
I'm not familiar with VirtualBox. Is virbr0 created (and used) by VirtualBox? Or did you create it manually?
I believe it was created by VBox.
I installed VirtualBox on two laptops (albeit running Ubuntu; I have Fedora and Ubuntu on my laptop but I don't want to install VirtualBox on either) and no br or tap device were created. I doubt that virbr0 would be created by VirtualBox on Fedor and not on Ubuntu. Furthermore, I doubt that VirtualBox would name its bridge virbr0, given that it's part of the libvirt "namespace" and that their respective default NAT setups use different ip ranges.
Or do you have libvirt installed (it's the default libvirt bridge name)?
I do, though nothing seems to depend on it. libvirtd is running, presumably as part of the standard KVM system, but AFAIK that's independent of VBox.
If you're running libvirt, then it's providing virbr0.
Unless you've changed the default, you can confirm this with "virsh net-dumpxml default | grep bridge".
On Thu, 2016-01-28 at 23:15 +0100, Tom H wrote:
Or do you have libvirt installed (it's the default libvirt bridge name)?
I do, though nothing seems to depend on it. libvirtd is running, presumably as part of the standard KVM system, but AFAIK that's independent of VBox.
If you're running libvirt, then it's providing virbr0.
Fair enough.
Unless you've changed the default, you can confirm this with "virsh net-dumpxml default | grep bridge".
I shut down the bridge to get dnsmasq to work.
$ virsh net-dumpxml default | grep bridge error: failed to get network 'default' error: Network not found: no network with matching name 'default'
As I said, I don't know why libvirtd is running in the first place as I don't use KVM, but I may have enabled it some time in the past as an experiment. However presumably some people do have both libvirtd and dnsmasq running on the same machine, so there must be a more elegant way of doing this.
poc
-
Mike Wright -
Patrick O'Callaghan -
Tim -
Tom H