sendnrw/netbird-docs
2
0
Fork 0
mirror of https://github.com/netbirdio/docs.git synced 2026-10-17 02:59:04 +02:00
Code Issues Packages Projects Releases Wiki Activity

Show both protocols when looking up the resolver listener port

Browse Source
This commit is contained in:
Viktor Liu
2026-09-09 11:36:19 +02:00
parent 5361814a22
commit a5977c739c
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
src/pages/manage/dns/troubleshooting.mdx
+1 -1
View File
@@ -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**: