DNS Configuration

Required DNS records

Point relay.<your-domain> and *.relay.<your-domain> (A and AAAA records) at your server to route incoming traffic and issue automatic Let’s Encrypt certificates. In the examples below, replace example.com with <your-domain>.

Direct IP records (static public IP)

If your server has a static IPv4 (and optionally IPv6) address, create address records:

relay.example.com.    300 IN A    203.0.113.10
*.relay.example.com.  300 IN A    203.0.113.10
relay.example.com.    300 IN AAAA 2001:db8::10
*.relay.example.com.  300 IN AAAA 2001:db8::10

Wildcard CNAME records (dynamic IP or NAS)

If you run Viaalink Relay on an ASUSTOR NAS or residential connection with dynamic DNS (such as ASUSTOR EZ-Connect yourname.myasustor.com), point both names using wildcard CNAME records:

relay.example.com.    300 IN CNAME yourname.myasustor.com.
*.relay.example.com.  300 IN CNAME yourname.myasustor.com.

The CNAME chain automatically updates with your dynamic IP address, requiring zero manual DNS maintenance.

Important: When using Cloudflare, set both records to DNS only (grey cloud). The orange “proxied” mode intercepts traffic at Cloudflare’s edge and breaks ACME TLS certificate issuance on your Relay.

Why both records are needed

• relay.example.com is the primary hostname for your Viaalink Relay server, used for SSH client connections and the browser setup dashboard.
• *.relay.example.com is the wildcard record that directs all published application subdomains (such as myapp.relay.example.com) to your Relay.

Supported DNS-01 providers for automated wildcards

When running Viaalink Relay with DNS-01 certificate issuance, the following DNS providers are natively supported:

1. Porkbun
2. Cloudflare
3. AWS Route53
4. DigitalOcean
5. GoDaddy

For instructions on configuring provider credentials, see Run Relay with Docker and Run Relay on ASUSTOR NAS.