2024-04-24T15:39:07+05:00 [1:dnsmasq1:dnsmasq] dnsmasq: failed to create listening socket for port 53: Address already in use
2024-04-24T15:39:07+05:00 [1:dnsmasq1:podman] 2024-04-24 15:39:07.965826062 +0500 +05 m=+0.065612697 container start 4c0fbd38ada65495818bd4e4a748b202ef21370cbae9a7a2bfb1ef0579d8ca30 (image=ghcr.io/nethserver/dnsmasq-server:latest, name=dnsmasq, io.buildah.version=1.23.1, PODMAN_SYSTEMD_UNIT=dnsmasq1.service)
2024-04-24T15:39:07+05:00 [1:dnsmasq1:podman] 4c0fbd38ada65495818bd4e4a748b202ef21370cbae9a7a2bfb1ef0579d8ca30
2024-04-24T15:39:07+05:00 [1:dnsmasq1:podman] 2024-04-24 15:39:07.925719508 +0500 +05 m=+0.025506088 image pull 48bd9fe84aa10cd1690dc8ac1b695060f74f38ca2948342a8ac05a9edea3f498 Package dnsmasq-server · GitHub
2024-04-24T15:39:07+05:00 [1:dnsmasq1:podman] 2024-04-24 15:39:07.999399283 +0500 +05 m=+0.025428669 container died 4c0fbd38ada65495818bd4e4a748b202ef21370cbae9a7a2bfb1ef0579d8ca30 (image=ghcr.io/nethserver/dnsmasq-server:latest, name=dnsmasq, PODMAN_SYSTEMD_UNIT=dnsmasq1.service, io.buildah.version=1.23.1)
2024-04-24T15:39:08+05:00 [1:dnsmasq1:podman] 2024-04-24 15:39:08.028392861 +0500 +05 m=+0.054422257 container remove 4c0fbd38ada65495818bd4e4a748b202ef21370cbae9a7a2bfb1ef0579d8ca30 (image=ghcr.io/nethserver/dnsmasq-server:latest, name=dnsmasq, PODMAN_SYSTEMD_UNIT=dnsmasq1.service, io.buildah.version=1.23.1)
2024-04-24T15:39:12+05:00 [1:dnsmasq1:agent@dnsmasq1] task/module/dnsmasq1/d1b87fc8-f5c9-4b13-a259-e7b8dc92adb2: get-status/20read is starting
2024-04-24T15:39:13+05:00 [1:dnsmasq1:agent@dnsmasq1] task/module/dnsmasq1/d1b87fc8-f5c9-4b13-a259-e7b8dc92adb2: action “get-status” status is “completed” (0) at step validate-output.json
2024-04-24T15:40:00+05:00 [1:dnsmasq1:agent@dnsmasq1] task/module/dnsmasq1/3bad4cdc-70ec-4db6-b216-953c4d640a98: get-available-interfaces/10fetch is starting
2024-04-24T15:40:00+05:00 [1:dnsmasq1:agent@dnsmasq1] task/module/dnsmasq1/3bad4cdc-70ec-4db6-b216-953c4d640a98: action “get-available-interfaces” status is “completed” (0) at step validate-output.json
2024-04-24T15:40:00+05:00 [1:dnsmasq1:agent@dnsmasq1] task/module/dnsmasq1/b981800e-5e11-449f-a67c-52f0cabfea7f: get-configuration/10get is starting
2024-04-24T15:40:00+05:00 [1:dnsmasq1:agent@dnsmasq1] task/module/dnsmasq1/b981800e-5e11-449f-a67c-52f0cabfea7f: action “get-configuration” status is “completed” (0) at step validate-output.json
2024-04-24T15:40:34+05:00 [1:dnsmasq1:agent@dnsmasq1] task/module/dnsmasq1/5fb2da1b-d232-48da-b5d2-4b4c25137ad9: get-status/20read is starting
2024-04-24T15:40:35+05:00 [1:dnsmasq1:agent@dnsmasq1] task/module/dnsmasq1/5fb2da1b-d232-48da-b5d2-4b4c25137ad9: action “get-status” status is “completed” (0) at step validate-output.json
samba is using the port for dns
1 Like
So I can’t use dnsmasq?
Not together as samba and dnsmasq both provide DNS on the default DNS port.
You could add a NS8 node for samba or let the router provide DNS and DHCP.
Samba and DNSmasq can run on the same node only if the DNS switch is off (Samba holds port 53). It is a scenario where Samba is the LAN DNS and DNSmasq plays the role of DHCP server only.
1 Like