Hi, i want to use VM, but without the inbuild DNS Server, how to do? For what is that dns server needed!?

Edited December 8, 20178 yr by nuhll

I need this.

 

Any help?!?!?

4 minutes ago, nuhll said:

I need this.

 

Any help?!?!?

If you set the VM to use a bridged connection (typically br0 but it depends on what you set up under Settings->Network) then the VM will act as if directly connected to the LAN and get its IP address and DNS via the LAN DHCP server.   The built in DNS server is for when you do not want the VM to be visible on the LAN.

All my VMs are set to br0.

 

The problem is as soon as u enable VM, the DNS Server gets startet, complete waste of everything.

 

 

What makes you think there is a DNS server running on br0?

 

I cant start a docker which should listen on the DNS port. If i disable VM, the docker works, if i enable, docker dont start "port already occupied".

What is the output of?

 

lsof -Pni | grep 53
 

dnsmasq   23174 nobody    5u  IPv4  276539      0t0  UDP 192.168.122.1:53
dnsmasq   23174 nobody    6u  IPv4  276540      0t0  TCP 192.168.122.1:53 (LISTEN)
 

That one is expected and shouldn't confict, it is the DNS server for the VM virtual bridge interface virbr0.

 

Dont know what you mean?

 

root@Unraid-Server:~# lsof -Pni | grep 53
ntpd       1530    ntp   16u  IPv4    7863      0t0  UDP 127.0.0.1:123
ntpd       1530    ntp   17u  IPv4  268959      0t0  UDP 192.168.86.2:123
ntpd       1530    ntp   18u  IPv6    7867      0t0  UDP [::1]:123
avahi-dae  2757  avahi   14u  IPv4   16725      0t0  UDP *:5353
avahi-dae  2757  avahi   15u  IPv6   16726      0t0  UDP *:5353
nginx      2808 nobody    4u  IPv4 3053668      0t0  TCP 192.168.86.2:81->192.168.86.3:55208 (ESTABLISHED)
nginx      2808 nobody   27u  IPv4 3053655      0t0  TCP 192.168.86.2:81->192.168.86.3:55207 (ESTABLISHED)
dnsmasq   23174 nobody    3u  IPv4  276536      0t0  UDP *:67
dnsmasq   23174 nobody    5u  IPv4  276539      0t0  UDP 192.168.122.1:53
dnsmasq   23174 nobody    6u  IPv4  276540      0t0  TCP 192.168.122.1:53 (LISTEN)
Plex\x20M 23487 nobody   78u  IPv4  374569      0t0  UDP 127.0.0.1:53120
Plex\x20T 23650 nobody   92u  IPv4  374584      0t0  UDP 192.168.86.2:46094->192.168.0.2:53
 

/usr/bin/docker: Error response from daemon: driver failed programming external connectivity on endpoint steamcache-dns (cf4af8712cf65461d7e7b64d24e52ea5faf32120c98ae054d7e96e335d09df12): Error starting userland proxy: listen udp 0.0.0.0:53: bind: address already in use.
 

Dont understand, now the DNS Server even runs if i disable the VMs completly... 

 

Suggestion: Add option to disable DNS Server 

Edited December 10, 20178 yr by nuhll

Well, your problem has nothing to do with VMs.

 

Change the network type of your steamcache-dns container to "host". It now fails because in bridge mode it will conflict with the built-in docker DNS server.

 

... I dont know why its not more connected with VM.

 

But before i could disable VM in settings and i could start the docker.

 

But your fix worked.

 

Still, i dont need a DNS Server on Unraid. Probably like many many ppl.

 

So, please add an option to disable DNS Server.

1 minute ago, nuhll said:

So, please add an option to disable DNS Server.

 

Both libvirt and docker start their own internal DNS server, this is required for their internal interfaces (virbr0 and bridge), besides that unRAID does not start any other DNS server.

I still dont understand for what this DNS Server is used....? If i set all dockers/VMs to br0 or host, this shouldnt be needed, or?

Okay, the docker starts, but i guess its still not accessable becaus ei get wrong results with ping. I guess the unraid dns is first priority, so im where i startet. I want to use a docker with a dns server, but i cant, because unraids own is running.

 

How i can remove it, disable it, what ever?

As the dev explained the dnsmasq process is required by libvirt to act as a DNS relay (and DHCP provider for the subnets?) . If you want to run your own DNS server then you can set your container to run on br0 so it can have its own IP address

 

You could also have the docker redirect on your host IP only instead of 0.0.0.0. I have an Unbound docker that starts fine when running in bridge mode and adding this in the extra parameters

-p 192.168.1.3:53:53/udp -p 192.168.1.3:53:53

Edited December 14, 20178 yr by sarbian