Seattle routing
Forums › Service Issues › Networking, Routing, Technology › Seattle routing
-
My understanding is that there’s a Seattle DNS server that’s part of the global anycast network. However, I’m getting assigned to a non-Seattle dns server whenever I perform a test using https://dnsleaktest.com. Here’s my result:
Hostnames:
1. dns-edge-usa-central-utah.cleanbrowsing.org (108.171.217.194)
2. dns-edge-usa-west-sv.cleanbrowsing.org (144.202.108.20)
Any idea why? The side effect I noticed is I’m getting routed to CDNs that are far away from Seattle.
-
This topic was modified 3 years, 6 months ago by
ll.
The SV ( Silicon Valley ) datacenter is pretty close to Seattle. Mind sending a traceroute to:
185.228.168.10
So we can see what is going on? also, what’s your ISP?
Here’s my traceroute to 185.228.168.10:
1 fdr01.sllk.wa.nwestnet.net (50.46.181.23) 1.563 ms 1.256 ms 1.495 ms 2 50.46.176.54 (50.46.176.54) 1.715 ms 1.594 ms 1.895 ms 3 ae3---0.cor02.sttl.wa.nwestnet.net (50.46.176.18) 3.180 ms 4.842 ms 2.693 ms 4 ae1---0.cbr01.sttl.wa.nwestnet.net (50.46.176.43) 2.729 ms 3.822 ms 2.806 ms 5 ae51.edge6.Seattle1.Level3.net (4.35.242.37) 2.952 ms 2.906 ms 3.064 ms 6 * * * 7 4.7.18.206 (4.7.18.206) 20.343 ms 20.002 ms 30.828 ms 8 * * * 9 * * * 10 adult-filter-dns.cleanbrowsing.org (185.228.168.10) 20.049 ms 19.555 ms 20.004 ms
-
This topic was modified 3 years, 6 months ago by
You must be logged in to reply to this topic.