🔧 Client Configuration – DNSaaS Help Centre

Step 1: Install Docker Desktop

Download and install Docker Desktop from docker.com. Ensure it's running before proceeding.

Step 2: Run the DNS Proxy Container

Open PowerShell as Administrator and run:

docker run -d --name "https-dns-proxy" --restart unless-stopped -p 53:5053/udp -p 53:5053/tcp `
  -e RESOLVER_URL="https://dns1.oss.co.za/testclient123" `
  -e DNS_SERVERS="1.1.1.1,8.8.8.8" `
  bwmoran/https-dns-proxy -vvv

Step 3: Configure Windows DNS

Go to Settings → Network & internet → [Your Network] → Edit DNS assignment. Set to Manual and enter 127.0.0.1 as the Preferred DNS.

Step 4: Test

Run nslookup google.com in PowerShell. You should see Server: localhost and IP addresses returned.

Step 1: Open System Settings

Click the Apple menu → System Settings → Network → select your active connection (e.g., Wi-Fi).

Step 2: Go to DNS Settings

Click Details... → select the DNS tab.

Step 3: Add DNS Servers

Click the + button under DNS Servers and enter your primary and secondary DNSaaS IP addresses. Remove any existing entries if they are not needed.

Step 4: Apply & Test

Click OK → Apply. Open Terminal and run:
dig example.com
Verify the SERVER: line shows your configured DNS IP.

Step 1: Open Network Manager

Go to Settings → Network → click the gear icon next to your active connection (Wired or Wi-Fi).

Step 2: Switch to Manual IPv4

In the IPv4 tab, change DNS from Automatic to Manual.

Step 3: Enter DNS Addresses

Add your primary and secondary DNSaaS IPs in the DNS field, separated by a comma.

Step 4: Apply & Restart

Click Apply and toggle the connection off/on. In Terminal, test with:
resolvectl status or dig example.com.

Step 1: Open Network & Internet

Go to Settings → Network & Internet → Private DNS (or search "Private DNS" in settings).

Step 2: Enter DNS-over-TLS Hostname

Select Private DNS provider hostname and enter your DNSaaS DoT endpoint (e.g., dns.yourdomain.com).

Step 3: Save & Verify

Tap Save. To test, open a browser and visit a site. For technical verification, use a network monitor app.

Step 1: Open Wi-Fi Settings

Go to Settings → Wi-Fi → tap the (i) info icon next to your connected network.

Step 2: Configure DNS

Scroll to Configure DNS → change from Automatic to Manual.

Step 3: Add DNS Servers

Tap Add Server and enter your primary DNSaaS IP. Add a secondary if needed. Remove any existing servers.

Step 4: Save & Test

Tap Save. Use Safari to browse. For terminal-like testing, you can use the iSH Shell app with nslookup.

Step 1: Access Router Admin

Open a browser and enter your router's IP (usually 192.168.1.1 or 192.168.0.1). Log in with admin credentials.

Step 2: Find DNS Settings

Look for Internet, WAN, or DHCP settings. The exact location varies by brand (look for "DNS Server" or "DNS Address").

Step 3: Set Static DNS

Change DNS Assignment from Get Automatically from ISP to Use These DNS Servers. Enter your primary and secondary DNSaaS IPs.

Step 4: Save & Reboot

Save settings and reboot the router. All connected devices should now use your DNSaaS. Test from a client with nslookup.

Linux (systemd-resolved)

sudo resolvectl set-dns eth0 203.0.113.1 203.0.113.2
sudo resolvectl set-dnsovertls eth0 yes

Windows Server (PowerShell)

Set-DnsClientServerAddress -InterfaceAlias "Ethernet" -ServerAddresses "203.0.113.1", "203.0.113.2"

macOS (networksetup)

sudo networksetup -setdnsservers Wi-Fi 203.0.113.1 203.0.113.2

Verify your DNS Server

nslookup example.com (Windows/macOS/Linux) – Check the Server field.

Check DNS Transport

Use tcpdump -i any port 53 or tshark to confirm queries are going to your DNSaaS IP and not elsewhere.

Common Issues

• Cannot reach DNS: Firewall or routing issue. Ping the DNS IP.
• Certificate errors (DoT/DoH): Ensure system date/time is correct and CA bundle is up to date.
• Authentication failures: Check API key/token or mTLS certificate validity.