AdGuardDNS
AdGuardDNS copied to clipboard
AdguardTeam
Never routed to UK (London) servers
I'm in the UK, and using AdGuard Private DNS. I am never routed to the AdGuard DNS server in London. I have literally never seen any device connected to it. I have tested over DoQ (my usual method), DoT (Unbound) and DoH (Firefox). I am always routed to the Amsterdam server when connected via my ISP, Virgin Media.
Stranger still, none of my VPN connections route to the AdGuard DNS London server either. All VPNs were tested using their London servers, with the tunnel DNS being set to 127.0.0.1 (using local Unbound forwarded to AdGuard DNS, as well as testing using AdGuard Home with filtering disabled and pointed to AdGuard DNS as the only upstream using DoQ).
Mullvad (London server) routes my queries to AdGuard DNS in Frankfurt. My own WireGuard VPN running on a private VPS in London (Oracle Cloud) also routes queries to AdGuard DNS in Frankfurt. My ISP routes queries to AdGuard DNS in Amsterdam. Nobody goes to AdGuard DNS in London!
Testing with my ISP (no VPNs), I am currently routed to
Protocol: "DNS-over-QUIC"
Server: "dns2-dp-fra-13"
Here is a traceroute to 94.140.14.14 using my ISP:
$ traceroute 94.140.14.14
traceroute to 94.140.14.14 (94.140.14.14), 64 hops max, 52 byte packets
1 router.[domain redacted] (10.100.0.1) 0.801 ms 0.240 ms 0.223 ms
2 10.53.35.5 (10.53.35.5) 16.085 ms 10.194 ms 16.815 ms
3 pres-core-2b-xe-116-0.network.virginmedia.net (213.104.74.153) 11.329 ms 13.482 ms 13.947 ms
4 * * *
5 * * *
6 * * *
7 host-62-254-42.162.not-set-yet.virginmedia.net.42.254.62.in-addr.arpa (62.254.42.162) 25.384 ms 28.942 ms 32.922 ms
8 nl-ams02a-rc2-lag-11-0.aorta.net (84.116.130.150) 37.352 ms 34.985 ms 32.334 ms
9 de-fra02a-rc1-ae-14-0.aorta.net (84.116.130.149) 34.852 ms 37.133 ms 34.707 ms
10 de-fra05a-ri1-ae-4-0.aorta.net (84.116.137.202) 32.862 ms 31.453 ms 34.953 ms
11 se-sto01a-ra2-ge-0-1-0-5.aorta.net (213.46.176.38) 32.714 ms 30.572 ms 33.912 ms
12 dns.adguard.com (94.140.14.14) 34.002 ms 30.170 ms 30.549 ms
Connected via one of my VPNs (a WireGuard instance running on Linux using Oracle Cloud, London):
Protocol: "DNS-over-QUIC"
Server: "dns2-dp-ams-2"
$ traceroute 94.140.14.14
traceroute to 94.140.14.14 (94.140.14.14), 64 hops max, 52 byte packets
1 * * *
2 140.91.200.14 (140.91.200.14) 33.959 ms
140.91.200.11 (140.91.200.11) 34.367 ms
140.91.200.14 (140.91.200.14) 30.101 ms
3 oracle-svc071175-lag003322.ip.twelve99-cust.net (213.248.98.247) 35.350 ms 31.841 ms
oracle-svc071174-lag003319.ip.twelve99-cust.net (213.248.69.255) 29.046 ms
4 slou-b1-link.ip.twelve99.net (213.248.98.246) 36.274 ms 34.403 ms
ldn-b7-link.ip.twelve99.net (213.248.69.254) 30.540 ms
5 ldn-bb4-link.ip.twelve99.net (62.115.141.246) 36.969 ms
ldn-bb4-link.ip.twelve99.net (62.115.117.122) 28.186 ms 31.938 ms
6 adm-bb4-link.ip.twelve99.net (62.115.113.238) 33.388 ms
adm-bb1-link.ip.twelve99.net (213.155.136.99) 35.839 ms
adm-bb4-link.ip.twelve99.net (62.115.134.26) 37.684 ms
7 adm-b7-link.ip.twelve99.net (80.91.246.43) 36.208 ms 36.515 ms 37.554 ms
8 adm-b7-link.ip.twelve99.net (80.91.246.45) 35.381 ms
datacamp-svc073250-ic361077.ip.twelve99-cust.net (62.115.150.178) 42.117 ms 45.633 ms
9 dns.adguard.com (94.140.14.14) 43.627 ms 41.005 ms 43.198 ms
The results for Mullvad look similar:
Protocol: "DNS-over-QUIC"
Server: "dns2-dp-fra-11"
$ traceroute 94.140.14.14
traceroute to 94.140.14.14 (94.140.14.14), 64 hops max, 52 byte packets
1 * * *
2 lon-ix1-cr1-v11.31173.se (141.98.252.65) 25.220 ms 30.084 ms 26.643 ms
3 141.98.252.43 (141.98.252.43) 27.479 ms 27.260 ms 26.903 ms
4 * * *
5 de-fra11b-rc1-ae-56-0.aorta.net (84.116.132.5) 42.377 ms 55.636 ms 43.193 ms
6 de-fra05a-ri1-ae-5-0.aorta.net (84.116.137.210) 46.274 ms 43.362 ms 38.205 ms
7 se-sto01a-ra2-ge-0-1-0-5.aorta.net (213.46.176.38) 40.354 ms 37.717 ms 39.894 ms
8 dns.adguard.com (94.140.14.14) 38.249 ms 38.551 ms 40.890 ms
As you can see, no matter how I connect I am never routed to the London server. Presently, NextDNS feels much snappier and faster browsing the web, as the queries route through London and response times are demonstrably faster. It would be nice if we could make AdGuard DNS just as fast, by using the closest server. Thanks in advance!
Same issue for me, also in the UK with the ISP Virgin Media.
Protocol: "DNS-over-QUIC"
Server: "dns2-dp-fra-8"
tracert.exe 94.140.14.14
Tracing route to dns.adguard.com [94.140.14.14]
over a maximum of 30 hops:
1 3 ms 2 ms 2 ms 192.168.0.1
2 21 ms 12 ms 11 ms 10.53.38.9
3 22 ms 16 ms 12 ms leic-core-2a-ae92-0.network.virginmedia.net [82.3.33.137]
4 * * * Request timed out.
5 * * * Request timed out.
6 26 ms 31 ms 22 ms host-62-254-42.162.not-set-yet.virginmedia.net.42.254.62.in-addr.arpa [62.254.42.162]
7 * * * Request timed out.
8 33 ms 28 ms 27 ms de-fra02a-rc1-ae-14-0.aorta.net [84.116.130.149]
9 30 ms 26 ms 28 ms de-fra05a-ri1-ae-4-0.aorta.net [84.116.137.202]
10 25 ms 25 ms 30 ms se-sto01a-ra2-ge-0-1-0-5.aorta.net [213.46.176.38]
11 27 ms 27 ms 25 ms dns.adguard.com [94.140.14.14]
Trace complete.
In the past week or so I've started getting routed to Amsterdam now instead of Frankfurt. Still not the UK unfortunately :(
Protocol: "DNS-over-QUIC"
Server: "dns2-dp-ams-2"
Tracing route to dns.adguard.com [94.140.14.14]
over a maximum of 30 hops:
1 6 ms 8 ms 4 ms 192.168.0.1
2 15 ms 11 ms 13 ms 10.53.38.9
3 35 ms 21 ms 10 ms leic-core-2b-ae92-0.network.virginmedia.net [82.3.33.165]
4 * * * Request timed out.
5 18 ms 32 ms 20 ms host-62-254-42.162.not-set-yet.virginmedia.net.42.254.62.in-addr.arpa [62.254.42.162]
6 * * 19 ms nl-ams17b-rc1-lag-9-0.aorta.net [84.116.130.241]
7 29 ms 24 ms 21 ms nl-ams14a-ri1-ae-8-0.aorta.net [84.116.135.38]
8 21 ms 19 ms 26 ms nl-ams14a-ri1-ae28-cdn77.aorta.net [213.46.162.26]
9 17 ms 25 ms 19 ms dns.adguard.com [94.140.14.14]
Trace complete.
It seems fixed for me. Here is my Virgin Media ISP line, tested with DoT (using unbound v1.16.2 on Fedora 36) as well as DoH in strict mode 3 (Firefox 104.0.1):
Protocol: "DNS-over-TLS"
Server: "dns2-dp-lon-1"
Protocol: "DNS-over-HTTPS"
Server: "dns2-dp-lon-2"
$ traceroute 94.140.14.14
traceroute to 94.140.14.14 (94.140.14.14), 30 hops max, 60 byte packets
1 _gateway (10.100.0.1) 0.187 ms 0.129 ms 0.110 ms
2 10.53.35.5 (10.53.35.5) 11.811 ms 17.412 ms 19.115 ms
3 pres-core-2b-xe-116-0.network.virginmedia.net (213.104.74.153) 19.221 ms 19.307 ms 19.328 ms
4 * * *
5 86.85-254-62.static.virginmediabusiness.co.uk (62.254.85.86) 28.021 ms 24.531 ms 26.428 ms
6 213.46.175.146 (213.46.175.146) 28.116 ms 33.356 ms 31.713 ms
7 dns.adguard.com (94.140.14.14) 30.060 ms 33.071 ms 22.733 ms
and on Mullvad (London) servers:
Protocol: "DNS-over-HTTPS"
Server: "dns2-dp-lon-2"
$ traceroute 94.140.14.14
traceroute to 94.140.14.14 (94.140.14.14), 30 hops max, 60 byte packets
1 10.64.0.1 (10.64.0.1) 20.265 ms 25.104 ms 26.994 ms
2 lon-ix1-cr1-v11.31173.se (141.98.252.65) 26.952 ms 26.909 ms 26.951 ms
3 141.98.252.43 (141.98.252.43) 26.947 ms 26.937 ms 26.907 ms
4 * * *
5 uk-lon01c-ri2-ae-6-0.aorta.net (84.116.136.98) 26.794 ms uk-lon01c-ri2-ae-4-0.aorta.net (84.116.135.50) 26.741 ms 26.736 ms
6 213.46.175.146 (213.46.175.146) 26.695 ms 21.681 ms 20.158 ms
7 dns.adguard.com (94.140.14.14) 16.696 ms 16.668 ms 20.328 ms
and finally OVPN (London servers):
Protocol: "DNS-over-TLS"
Server: "dns2-dp-lon-1"
$ traceroute 94.140.14.14
traceroute to 94.140.14.14 (94.140.14.14), 30 hops max, 60 byte packets
1 172.16.0.1 (172.16.0.1) 46.818 ms 49.792 ms 49.742 ms
2 vlan113.mer-b3-10g.m247.com (89.238.176.1) 50.472 ms 53.874 ms 55.519 ms
3 212.103.51.246 (212.103.51.246) 107.160 ms 107.158 ms 107.424 ms
4 te-2-5-0.bb1.lon1.uk.m247.com (89.44.212.126) 55.480 ms 55.457 ms 55.420 ms
5 vlan3006.bb1.bud.hu.m247.com (193.9.115.133) 55.503 ms eth-35-1-0.pni1.lon2.uk.m247.com (83.97.21.107) 56.761 ms xe-2-0-0-0.core1.lon2.uk.m247.com (176.10.82.158) 55.325 ms
6 89.44.212.119 (89.44.212.119) 60.686 ms 89.44.212.117 (89.44.212.117) 29.819 ms 89.44.212.119 (89.44.212.119) 27.572 ms
7 vlan2921.as05.thg1.nl.m247.com (83.97.21.27) 28.227 ms 26.896 ms 26.486 ms
8 185.1.32.46 (185.1.32.46) 34.426 ms 38.425 ms 38.451 ms
9 * dns.adguard.com (94.140.14.14) 38.270 ms 38.258 ms
The only remaining affected node for me is using Oracle in London, but their routing is screwed anyway (I get Arabic text and SAE geolocation on Google, for example):
Protocol: "DNS-over-TLS"
Server: "dns2-dp-ams-2"
$ traceroute 94.140.14.14
traceroute to 94.140.14.14 (94.140.14.14), 30 hops max, 60 byte packets
1 10.144.164.1 (10.144.164.1) 19.081 ms 24.020 ms 23.995 ms
2 140.91.200.67 (140.91.200.67) 24.002 ms 140.91.200.71 (140.91.200.71) 23.973 ms 140.91.200.9 (140.91.200.9) 23.948 ms
3 oracle-svc071174-lag003319.ip.twelve99-cust.net (213.248.69.255) 23.927 ms 23.894 ms oracle-svc071175-lag003322.ip.twelve99-cust.net (213.248.98.247) 23.856 ms
4 slou-b1-link.ip.twelve99.net (213.248.98.246) 23.833 ms 23.856 ms 23.822 ms
5 ldn-bb4-link.ip.twelve99.net (62.115.117.122) 23.797 ms ldn-bb4-link.ip.twelve99.net (62.115.141.246) 23.774 ms 23.753 ms
6 adm-bb1-link.ip.twelve99.net (213.155.136.99) 29.148 ms 24.706 ms 24.932 ms
7 adm-bb3-link.ip.twelve99.net (62.115.143.247) 27.384 ms adm-b7-link.ip.twelve99.net (80.91.246.43) 29.210 ms 29.187 ms
8 adm-b7-link.ip.twelve99.net (80.91.246.45) 28.451 ms 29.111 ms 28.346 ms
9 dns.adguard.com (94.140.14.14) 33.204 ms rcsrds-svc077848-ic367304.c.telia.net (62.115.191.210) 34.582 ms dns.adguard.com (94.140.14.14) 33.157 ms
I'd consider this fixed, for me. @AidanGee7 keep testing, hopefully yours will 'wake up' too. The fun and games of BGP!
