Skip to main content

How can we help you?

Search

help Knowledge Base
forum Community
checklist Release Notes
event Events

Resolve DNS Relay deployment errors

Minetta Gould
  • Updated

    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.

relay.conf configuration error

This error behavior applies to Relay v1.5.0 and higher. On earlier versions, a missing or malformed relay.conf may produce the error open /go/bin/lan-proxy.conf: no such file or directory instead. The resolution steps below apply to both.

A missing, incorrectly named, or malformed relay.conf file produces a configuration error on startup in Relay v1.5.0 and higher.

Confirm the following:

  • relay.conf exists in the expected directory for the deployment mode in use
  • The file name is spelled and capitalized correctly
  • The file uses valid TOML formatting with no syntax errors
  • The file is accessible by the Docker daemon (Docker deployments)

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.

Related content

Was this article helpful?
3 out of 3 found this helpful
Return to top

Comments

0 comments

Please sign in to leave a comment.