0
Aliant/Bell Connection Not Resolving Domains, using DNS Override on Router
I signed up for Pro a few weeks ago and things were running quite well, however last week all domains stopped resolving. My DNS settings were replaced with the ones from my.nextdns.io page.
If I revert DNS to my provider default everything returns to normal.
https://nextdns.io/diag/1d216fd0-b203-11ed-9894-0facf703e77c
Welcome to NextDNS network diagnostic tool.
This tool will capture latency and routing information regarding
the connectivity of your network with NextDNS.
The source code of this tool is available at https://github.com/nextdns/diag
Do you want to continue? (press enter to accept)
Testing IPv6 connectivity
available: false
Fetching https://test.nextdns.io
status: unconfigured
client: 142.162.46.54
resolver: 142.166.151.141
Fetching PoP name for ultra low latency primary IPv4 (ipv4.dns1.nextdns.io)
ovh-ymq: 36.005ms
Fetching PoP name for ultra low latency secondary IPv4 (ipv4.dns2.nextdns.io)
zepto-ymq: 37.263ms
Fetching PoP name for anycast primary IPv4 (45.90.28.0)
vultr-yto: 28.998ms
Fetching PoP name for anycast secondary IPv4 (45.90.30.0)
anexia-yto: 22.256ms
Pinging PoPs
anexia-yto: 23.377ms
vultr-yto: 29.107ms
anexia-ewr: 29.727ms
smarthost-bos: 30.92ms
zepto-ymq: 35.118ms
ovh-ymq: 35.074ms
zepto-xrs: 34.761ms
vultr-ewr: 35.995ms
hetzner-iad: 37.303ms
axcelx-bos: 40.141ms
Traceroute for ultra low latency primary IPv4 (51.222.107.153)
1 192.168.2.1 3ms 1ms 1ms
2 142.166.182.17 3ms 3ms 3ms
3 142.176.208.53 3ms 3ms 3ms
4 142.166.185.145 5ms 4ms 5ms
5 207.231.227.53 23ms 24ms 22ms
6 4.31.208.117 25ms 23ms 24ms
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 198.27.73.218 * 38ms *
13 192.99.146.138 35ms 34ms 34ms
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 51.222.107.153 36ms 34ms 34ms
Traceroute for ultra low latency secondary IPv4 (86.106.90.57)
1 192.168.2.1 2ms 1ms 1ms
2 142.166.182.17 3ms 1ms 2ms
3 142.176.208.53 3ms 2ms 3ms
4 142.166.185.145 5ms 5ms 4ms
5 207.231.227.53 23ms 23ms 23ms
6 184.150.187.56 24ms 24ms 25ms
7 * * *
8 142.124.126.223 25ms 25ms 24ms
9 4.1.114.169 26ms 23ms 23ms
10 4.69.134.34 40ms 39ms 39ms
11 4.15.18.246 34ms 34ms 34ms
12 193.27.15.190 53ms 54ms 53ms
13 83.97.21.81 35ms 34ms 35ms
14 * * *
15 86.106.90.57 35ms 34ms 34ms
Traceroute for anycast primary IPv4 (45.90.28.0)
1 192.168.2.1 2ms 1ms 1ms
2 142.166.182.17 7ms 16ms 4ms
3 142.176.208.49 4ms 4ms 6ms
4 142.166.185.154 3ms 3ms 3ms
5 142.166.185.145 5ms 5ms 4ms
6 207.231.227.53 22ms 22ms 21ms
7 184.150.187.56 24ms 23ms 23ms
8 * * *
9 142.124.126.221 25ms 28ms 25ms
10 4.1.114.169 30ms 37ms 22ms
11 4.69.151.109 23ms 23ms 25ms
12 4.16.52.82 29ms 30ms 29ms
13 * * *
14 * * *
15 * * *
16 45.90.28.0 30ms 28ms 28ms
Traceroute for anycast secondary IPv4 (45.90.30.0)
1 192.168.2.1 3ms 2ms 2ms
2 142.166.182.17 3ms 3ms 3ms
3 142.176.208.53 10ms 4ms 4ms
4 142.166.185.145 21ms 6ms 12ms
5 207.231.227.53 23ms 23ms 22ms
6 184.150.187.56 25ms 25ms 26ms
7 64.230.97.178 28ms * *
8 142.124.127.39 24ms 24ms 25ms
9 213.248.97.222 22ms 22ms 23ms
10 62.115.117.229 23ms 22ms 24ms
11 62.115.160.18 23ms 83ms 55ms
12 188.172.249.32 76ms 22ms 22ms
13 45.90.30.0 25ms 21ms 22ms
2 replies
-
The instructions for router setup were using the wrong IP information, looking at one of the other methods of setup and using those IP's worked.
Content aside
- 1 yr agoLast active
- 2Replies
- 60Views
-
2
Following