DOH, DOH/3, and DOQ all randomly stop accepting DNS queries...

[32bitx64bit]

Hi, currently having this weird issue where all but DoT will stop accepting DNS queries.
I'm on the latest technitium dns server build.
Running on Debian 12.
It only fixes itself when I restart the server completely.
2024-11-18(1).log
Here's the latest log if it helps.

[ShreyasZare]

Thanks for the post. The logs shared do not have any error log related to the issue you are mentioning. The errors in there are related to failure to resolve a specific domain name due to some network issues.

I am not sure why this could happen since I have these deployed in production and its working well on Debian 12. I would suggest that you debug the issue when it occurs.

To do that, you should first check if the service ports are open using sudo netstat -nlptu command which should list all the open ports. If you see the ports are open then the services are running. If not, then check the DNS logs to see if there are any error logs.

If ports are open, try using the DNS Client tool on the admin panel to test if the DNS server responds over the selected protocol. Since these are encrypted DNS services, you will need to use the full DoH URL with the domain name used to generate the TLS certificate. To test DoH/3, use h3 as the URL scheme instead of https. Test all the services, DoH, DoH/3, DoQ, and DoT and share your results here.

[32bitx64bit]

Alright I'll give it a shot

[32bitx64bit]

Hm weird. All the UDP ports aren't listening anymore. That explains why protocols but TLS is failing. Would you happen to know anyway to fix this?

[ShreyasZare]

Hm weird. All the UDP ports aren't listening anymore. That explains why protocols but TLS is failing. Would you happen to know anyway to fix this?

If you do not see any port belonging to the DNS server listening then the server may have stopped working. Do post the output of command you ran so that I can understand it better.

[32bitx64bit]

Hm weird. All the UDP ports aren't listening anymore. That explains why protocols but TLS is failing. Would you happen to know anyway to fix this?

If you do not see any port belonging to the DNS server listening then the server may have stopped working. Do post the output of command you ran so that I can understand it better.

Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:853 0.0.0.0:* LISTEN 402/dotnet
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 424/sshd: /usr/sbin
tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN 402/dotnet
tcp6 0 0 :::443 :::* LISTEN 402/dotnet
tcp6 0 0 :::853 :::* LISTEN 402/dotnet
tcp6 0 0 :::53443 :::* LISTEN 402/dotnet
tcp6 0 0 :::80 :::* LISTEN 402/dotnet
tcp6 0 0 :::22 :::* LISTEN 424/sshd: /usr/sbin
tcp6 0 0 :::53 :::* LISTEN 402/dotnet
udp 0 0 0.0.0.0:53 0.0.0.0:* 402/dotnet
udp 0 0 159.100.250.108:68 0.0.0.0:* 363/systemd-network
udp6 0 0 :::853 :::* 402/dotnet
udp6 0 0 :::443 :::* 402/dotnet
udp6 0 0 :::53 :::* 402/dotnet
udp6 0 0 :::53443 :::* 402/dotnet

As for running DoQ DNS resolve it works fine on server. On my secondary separate server it gives a connection error.