dns over http only listens on ips listed under local end points for the normal UDP ports

[foss-fiona]

Im using a traefik reverse proxy to use for DoH in my Docker-compose technitium deployment.

Traefik uses its own network for proxying webtraffic, which is why I dont need the normal udp/53 port listening on this ip and therefor havent used this IP-Address in "DNS Server Local End Points".

Here I ran into the Issue that traefik just couldnt reach the dns over http webserver. I (incorrectly) assumed that since the Local End Points setting for the normal UDP dns Ports specifically list the Ip-addresses with :53, that this is only for the udp resolver and doesnt involve optional protocols.

This is a little confusing and should be documented better or should be a seperate option altogether for the optional protocols only listen on certain IPs/Net interfaces.

Also especially for use in docker environments I think needing to list specific IPs for the Server to listen on, is a little unpractical. I mean you could assign a fixed IP for the docker container, but this would just make the docker environment less flexible, which is like the main reason to use docker.
Especially for docker environments, but also in general, I think being able to list the Network Interfaces instead of the IPs would be a nice option to have.

This is my first github Issue, so I hope I gave all the information necessary and this issue is at least a little coherent.

Main takeaways:

• Document that the local end points doesnt just bind the port 53 but also the optional protocols
• Maybe inplement a seperate option for the optional protocols
• Maybe add the option to bind to net interfaces instead of IPs

Thanks to the Technitium Team for this amazing Software, I recently completely switched over from Pihole and im loving the features and advanced configurability.

[ShreyasZare]

Thanks for the post and compliments.

The "DNS Server Local End Points" are the end points for use by the DNS server where UDP and TCP are mandatory protocols and then you have these optional protocols that you can switch on. The docs in GUI does not say that the local end point is only for UDP & TCP but says that its for the DNS server to listen on for requests. Having a separate local end point option for Optional Protocols may create more confusion and misconfigurations. Hope that clarifies the confusion.

Since you are using docker, you do not need to configure local end points and let it use the default values. With docker, you need to edit your compose file to map the ports inside the container to the ports on the host server. You will need to configure local end points only and only when your docker container is being configured to use "host" network mode where it gets direct access to host system's network.

It is not possible to bind sockets to interface. It has to bind to an IP address only. The best way is to keep the default values so that it works for all interfaces.

Let me know if you have any more queries.