In this article
Use this article to resolve common error messages encountered during DNS Relay deployment. For general diagnostic steps, see Troubleshoot DNS Relay with Relay Manager.
Listen tcp4 x.x.x.x:53 bind: address already in use
Another process is already bound to port 53 on the host device, preventing the Relay from starting. This commonly occurs on Linux distributions that run a DNS daemon by default.
Disable the running DNS daemon on the host device, or update relay.conf to direct the Relay to listen on a different port.
For Linux distributions running systemd-resolved, see Resolve systemd-resolved conflicts with DNS Relay on Linux.
Post https://api.dnsfilter[...] lookup api.dnsfilter.com: Try Again
The host device does not have an external DNS server configured and cannot resolve api.dnsfilter.com. This commonly occurs after disabling a DNS daemon to resolve the port 53 conflict above.
Add an external DNS server such as 8.8.8.8 or 9.9.9.9 to the system following the applicable Linux distribution instructions.
Not a valid TOML config file / open /go/bin/lan-proxy.conf: no such file or directory
The relay.conf file expected in the current working directory is missing, named incorrectly, contains a formatting error, or cannot be accessed due to permission issues.
Confirm that relay.conf exists in the current working directory, uses the correct file name and TOML formatting, and is accessible by the Docker daemon.
Invalid organization or network secret key
The Site Key entered in relay.conf is invalid. Replace the value with the correct Site Key from the DNSFilter dashboard.
Unsupported hardware family 'vmx-19'
This error indicates the environment is running VMware vSphere v6.5, which reached end-of-life on 12 October 2022. Update to vSphere version 8 to resolve the issue.
Comments
0 comments
Please sign in to leave a comment.