From a5977c739cd14e58adbab6e3b2f60e5ce42126db Mon Sep 17 00:00:00 2001 From: Viktor Liu Date: Wed, 9 Sep 2026 11:36:19 +0200 Subject: [PATCH] Show both protocols when looking up the resolver listener port --- src/pages/manage/dns/troubleshooting.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/pages/manage/dns/troubleshooting.mdx b/src/pages/manage/dns/troubleshooting.mdx index 1d940162..799b8c18 100644 --- a/src/pages/manage/dns/troubleshooting.mdx +++ b/src/pages/manage/dns/troubleshooting.mdx @@ -624,7 +624,7 @@ Parts of DNS are implemented with firewall rules, so [`--disable-firewall`](/cli Two things break: -- **The port 53 redirect.** The local resolver prefers port 53, but when another DNS server on the host already holds it the resolver falls back to another port and the client redirects port 53 to it with firewall rules. Without the firewall the redirect is missing and queries keep going to port 53. Confirm with `sudo ss -ulnp | grep :53` on the peer: NetBird listening on a port other than 53 means the redirect was needed. +- **The port 53 redirect.** The local resolver prefers port 53, but when another DNS server on the host already holds it the resolver falls back to another port and the client redirects port 53 to it with firewall rules. Without the firewall the redirect is missing and queries keep going to port 53. Find the resolver's listener with `sudo ss -ltnup | grep netbird` on the peer: a port other than 53 means the redirect was needed. - **The DNS forwarder on a routing peer.** Its port is not opened and the address sets behind domain resource access control are not updated, so domain resources served by that peer do not resolve. **Solutions**: