|
| 1 | +--- |
| 2 | +title: Public DNS and AdGuard Home Integration |
| 3 | +impact: HIGH |
| 4 | +impactDescription: Without proper public DNS and AdGuard Home configuration, users may experience degraded performance, connectivity issues, or inability to leverage NextDNS features for unlinked devices and third-party DNS forwarders. |
| 5 | +type: capability |
| 6 | +tags: public dns, adguard, anycast, doh, dot, browser setup, windows, android, ios, upstream dns, bootstrap dns |
| 7 | +--- |
| 8 | + |
| 9 | +# Public DNS and AdGuard Home Integration |
| 10 | + |
| 11 | +**Impact: HIGH** - Critical for unlinked device setup and AdGuard Home upstream configuration |
| 12 | + |
| 13 | +## Overview |
| 14 | + |
| 15 | +NextDNS provides public DNS servers (anycast) that can be used for devices that cannot link to a specific configuration profile, as well as integration with AdGuard Home as an upstream DNS provider. This guide covers browser setup, operating system configuration, and AdGuard Home integration patterns. |
| 16 | + |
| 17 | +## Public DNS Servers (Anycast) |
| 18 | + |
| 19 | +NextDNS operates the following public DNS servers for unlinked devices: |
| 20 | + |
| 21 | +**IPv4 Addresses:** |
| 22 | +- Primary: `45.90.28.0` |
| 23 | +- Secondary: `45.90.30.0` |
| 24 | + |
| 25 | +**IPv6 Addresses:** |
| 26 | +- Primary: `2a07:a8c0::` |
| 27 | +- Secondary: `2a07:a8c1::` |
| 28 | + |
| 29 | +**DNS over HTTPS (DoH):** |
| 30 | +- Endpoint: `https://dns.nextdns.io/` |
| 31 | + |
| 32 | +**DNS over TLS (DoT) / Android Private DNS:** |
| 33 | +- Hostname: `dns.nextdns.io` |
| 34 | + |
| 35 | +## Browser Setup |
| 36 | + |
| 37 | +### Chrome and Edge |
| 38 | + |
| 39 | +Configure secure DNS in Chromium-based browsers: |
| 40 | + |
| 41 | +1. Navigate to **Settings** |
| 42 | +2. Go to **Privacy and security** |
| 43 | +3. Select **Security** |
| 44 | +4. Enable **Use secure DNS** |
| 45 | +5. Select **Custom** provider |
| 46 | +6. Enter: `https://dns.nextdns.io/` |
| 47 | + |
| 48 | +### Firefox |
| 49 | + |
| 50 | +Configure DNS over HTTPS in Firefox: |
| 51 | + |
| 52 | +1. Navigate to **Settings** |
| 53 | +2. Go to **Privacy & Security** |
| 54 | +3. Enable **DNS over HTTPS** |
| 55 | +4. Select **Max Protection** |
| 56 | +5. Choose **NextDNS** from the provider list |
| 57 | + |
| 58 | +## Operating System Setup |
| 59 | + |
| 60 | +### Windows 11 |
| 61 | + |
| 62 | +Configure DNS settings with DoH support: |
| 63 | + |
| 64 | +1. Open **Settings** |
| 65 | +2. Navigate to **Network & internet** |
| 66 | +3. Select your connection (**Wi-Fi** or **Ethernet**) |
| 67 | +4. Click **Hardware properties** |
| 68 | +5. Under **DNS Server Assignment**, click **Edit** |
| 69 | +6. Set **IPv4 DNS servers**: |
| 70 | + - Preferred: `45.90.28.0` |
| 71 | + - Alternate: `45.90.30.0` |
| 72 | +7. Set **IPv6 DNS servers**: |
| 73 | + - Preferred: `2a07:a8c0::` |
| 74 | + - Alternate: `2a07:a8c1::` |
| 75 | +8. Set **DNS over HTTPS** to **On (manual template)** |
| 76 | +9. Enter template: `https://dns.nextdns.io/` |
| 77 | + |
| 78 | +### Android |
| 79 | + |
| 80 | +Configure Private DNS for system-wide encrypted DNS: |
| 81 | + |
| 82 | +1. Open **Settings** |
| 83 | +2. Navigate to **Network & internet** |
| 84 | +3. Select **Private DNS** |
| 85 | +4. Choose **Private DNS provider hostname** |
| 86 | +5. Enter: `dns.nextdns.io` |
| 87 | + |
| 88 | +### iOS |
| 89 | + |
| 90 | +iOS requires installing a configuration profile: |
| 91 | + |
| 92 | +1. Visit the [Apple configuration generator](https://apple.nextdns.io) |
| 93 | +2. Generate and download the `.mobileconfig` profile for your configuration |
| 94 | +3. Install the profile on your iOS device |
| 95 | +4. Navigate to **Settings** → **General** → **VPN & Device Management** |
| 96 | +5. Select and install the NextDNS profile |
| 97 | + |
| 98 | +**Note:** The profile must be generated from the official NextDNS Apple generator to ensure proper signing and compatibility. |
| 99 | + |
| 100 | +## AdGuard Home Integration |
| 101 | + |
| 102 | +### Upstream DNS Servers |
| 103 | + |
| 104 | +Configure NextDNS as upstream DNS in AdGuard Home for load balancing: |
| 105 | + |
| 106 | +**Recommended Configuration:** |
| 107 | +```conf |
| 108 | +https://dns1.nextdns.io/ |
| 109 | +https://dns2.nextdns.io/ |
| 110 | +``` |
| 111 | + |
| 112 | +**Alternative Protocols:** |
| 113 | +- **DNS over TLS:** Use `tls://dns1.nextdns.io/` and `tls://dns2.nextdns.io/` |
| 114 | +- **DNS over QUIC:** Use `quic://dns1.nextdns.io/` and `quic://dns2.nextdns.io/` |
| 115 | + |
| 116 | +### Bootstrap DNS Servers |
| 117 | + |
| 118 | +**Critical:** Bootstrap DNS servers must be configured to ensure AdGuard Home can resolve NextDNS upstream hostnames and maintain EDNS Client Subnet (ECS) functionality for optimal routing. |
| 119 | + |
| 120 | +**Recommended Bootstrap Servers:** |
| 121 | +```conf |
| 122 | +8.8.8.8 |
| 123 | +9.9.9.11 |
| 124 | +208.67.222.222 |
| 125 | +``` |
| 126 | + |
| 127 | +These public resolvers ensure that AdGuard Home can properly resolve the NextDNS upstream hostnames and maintain ECS functionality for optimal routing. |
| 128 | + |
| 129 | +## Best Practices |
| 130 | + |
| 131 | +- Use DNS over HTTPS (DoH) or DNS over TLS (DoT) whenever possible for encrypted DNS queries |
| 132 | +- Configure both IPv4 and IPv6 DNS servers for dual-stack networks |
| 133 | +- Always set bootstrap DNS servers in AdGuard Home to avoid ECS issues |
| 134 | +- Use load-balanced endpoints (`dns1` and `dns2`) for better reliability in AdGuard Home |
| 135 | +- Test DNS configuration after setup using online DNS leak test tools |
| 136 | + |
| 137 | +## Common Pitfalls |
| 138 | + |
| 139 | +- **Missing Bootstrap DNS:** AdGuard Home may fail to resolve NextDNS upstream servers without proper bootstrap configuration |
| 140 | +- **IPv6 Only:** Ensure both IPv4 and IPv6 are configured on dual-stack networks |
| 141 | +- **DoH Template Format:** Windows 11 requires the full `https://` URL format for DoH templates |
| 142 | +- **iOS Profile Expiry:** Configuration profiles may need to be reinstalled after iOS updates |
| 143 | + |
| 144 | +## Troubleshooting |
| 145 | + |
| 146 | +**DNS Not Resolving:** |
| 147 | +- Verify DNS server addresses are entered correctly |
| 148 | +- Check firewall rules allow DNS traffic (port 53, 443 for DoH, 853 for DoT) |
| 149 | +- Test with `nslookup` or `dig` commands |
| 150 | + |
| 151 | +**AdGuard Home Connection Issues:** |
| 152 | +- Ensure bootstrap DNS servers are configured |
| 153 | +- Verify network connectivity to NextDNS endpoints |
| 154 | +- Check AdGuard Home logs for upstream DNS errors |
| 155 | + |
| 156 | +**ECS Not Working:** |
| 157 | +- Confirm bootstrap DNS servers are set to public resolvers |
| 158 | +- Verify AdGuard Home upstream configuration uses hostnames (not IP addresses) |
| 159 | + |
| 160 | +## Reference |
| 161 | + |
| 162 | +- [NextDNS Setup Guide](https://help.nextdns.io/tag/setup) |
| 163 | +- [AdGuard Home Configuration](https://github.com/AdguardTeam/AdGuardHome/wiki/Configuration) |
| 164 | +- [Apple Configuration Generator](https://apple.nextdns.io) |
0 commit comments