Hello,
your DNS have worked for our family and friends pretty well for half a year at least.
But we have experienced some issues recently. The one most annoying is this one.
Hope you can help me with that ASAP, otherwise I will have to go back to my providers DNS.
thanks
LH
While using your DNS servers www.microsoft.com resolves to the IP below and it never reaches the server.
Tracing route to e13678.dspb.akamaiedge.net [23.38.84.178] over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.24.1
2 1 ms 1 ms 1 ms 109.234.46.1
3 1 ms 1 ms 1 ms 10.0.10.1
4 3 ms 4 ms 2 ms b1-ccl-mb1001.n.cbsn.cz [109.234.47.201]
5 3 ms 2 ms 2 ms ip-185-255-116-145.n.cbsn.cz [185.255.116.145]
6 * * * Request timed out.
7 * * * Request timed out.
8 *While using your DNS
while using the provider DNS server it resolves to following IP and it reaches the server without issues.
tracert www.microsoft.com
Tracing route to e13678.dspb.akamaiedge.net [2.18.70.63] over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.24.1
2 1 ms 2 ms 1 ms 109.234.46.1
3 1 ms 1 ms 1 ms 10.0.10.1
4 2 ms 2 ms 2 ms b1-ccl-mb1001.n.cbsn.cz [109.234.47.201]
5 2 ms 2 ms 2 ms ip-185-255-116-145.n.cbsn.cz [185.255.116.145]
6 3 ms 3 ms 2 ms cust-helios.supernetwork.cz [88.86.99.36]
7 2 ms 3 ms 2 ms ae12-402.prg10.core-backbone.com [5.56.20.81]
8 7 ms 7 ms 7 ms ae1-2051.vie20.core-backbone.com [81.95.15.49]
9 7 ms 7 ms 7 ms vix-vie.netarch.akamai.com [193.203.0.168]
10 7 ms 7 ms 7 ms a2-18-70-63.deploy.static.akamaitechnologies.com [2.18.70.63]
Not sure if it helps with this issue, but below is the output of your diagnostic tool.
Hi, sorry about that. It seems like it resolves www.microsoft.com, but the issue is resolving the reverse name in your traceroute output. I’m assuming it’s cust-helios.supernetwork.cz (88.86.99.36) but it could be something else. You should be able to get a list of addresses without the symbolic resolution with the -n option, e.g. traceroute -n www.microsoft.com to help debug this.
Tracing route to e13678.dspb.akamaiedge.net [23.38.84.178] over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.24.1
2 3 ms 2 ms 1 ms 109.234.46.1
3 21 ms 2 ms 2 ms 10.0.10.1
4 6 ms 3 ms 4 ms 109.234.47.201
5 4 ms 3 ms 3 ms 185.255.116.145
6 * * * Request timed out.
7 * * * Request timed out.
8 * *
D:\SYSTOOLS\curl\bin\curl.exe --resolve www.microsoft.com:443:23.38.84.178 https://www.microsoft.com -v
* Added www.microsoft.com:443:23.38.84.178 to DNS cache
* Hostname www.microsoft.com was found in DNS cache
* Trying 23.38.84.178:443...
* connect to 23.38.84.178 port 443 failed: Timed out
* Failed to connect to www.microsoft.com port 443: Timed out
* Closing connection 0
curl: (28) Failed to connect to www.microsoft.com port 443: Timed out
but today it seems to be OK, it is resolving to 2.17.14.63, which works
EDIT: I have just realized that the IP is different from the IP which worked yesterday
and the route is also a bit different.
tracert www.microsoft.com
Tracing route to e13678.dspb.akamaiedge.net [2.17.14.63] over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms router.lan [192.168.24.1]
2 1 ms 1 ms 1 ms 109.234.46.1
3 1 ms 1 ms 1 ms 10.0.10.1
4 2 ms 2 ms 2 ms b1-ccl-mb1001.n.cbsn.cz [109.234.47.201]
5 2 ms 2 ms 2 ms ip-185-255-116-145.n.cbsn.cz [185.255.116.145]
6 2 ms 4 ms 2 ms cust-helios.supernetwork.cz [88.86.99.36]
7 2 ms 2 ms 2 ms ae8.cr3-prg1.ip4.gtt.net [46.33.86.13]
8 2 ms 2 ms 2 ms ae16.cr4-prg1.ip4.gtt.net [213.200.114.10]
9 2 ms 2 ms 2 ms akamai-gw.ip4.gtt.net [141.136.98.10]
10 2 ms 2 ms 2 ms a2-17-14-63.deploy.static.akamaitechnologies.com [2.17.14.63]
Have you been able to fix it or it was fixed somewhere else?
Just asking, so I know who to bother next time, because it is beyond me how these geo/peering things work
If you have some spare time I would appreciate if you could explain it to me or just point me to some “how it works” articles.
Today, I get sometimes IP for www.microsoft.com which works, but most of the time I get IP which don’t.
I have the same problems with another site running on akamai.net
tracert www.ebay.com
Tracing route to e9428.b.akamaiedge.net [104.127.53.230] over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms router.lan [192.168.24.1]
2 1 ms 1 ms 1 ms 109.234.46.1
3 89 ms 1 ms 1 ms 10.0.10.1
4 2 ms 2 ms 2 ms b1-ccl-mb1001.n.cbsn.cz [109.234.47.201]
5 2 ms 2 ms 2 ms ip-185-255-116-145.n.cbsn.cz [185.255.116.145]
6 * * * Request timed out.
7 * * * Request timed out.
8 *
when I try the IP which I get from providers DNS, it works
www.ebay.com
Server: ns.cbsn.cz
Address: 81.25.16.250
Non-authoritative answer:
Name: e9428.b.akamaiedge.net
Address: 2.18.69.152
Aliases: www.ebay.com
slot9428.ebay.com.edgekey.net
tracert 2.18.69.152
Tracing route to a2-18-69-152.deploy.static.akamaitechnologies.com [2.18.69.152] over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms router.lan [192.168.24.1]
2 1 ms 1 ms 1 ms 109.234.46.1
3 1 ms 1 ms 1 ms 10.0.10.1
4 2 ms 1 ms 2 ms b1-ccl-mb1001.n.cbsn.cz [109.234.47.201]
5 3 ms 2 ms 2 ms ip-185-255-116-145.n.cbsn.cz [185.255.116.145]
6 5 ms 2 ms 4 ms cust-helios.supernetwork.cz [88.86.99.36]
7 2 ms 2 ms 2 ms ae12-402.prg10.core-backbone.com [5.56.20.81]
8 6 ms 7 ms 7 ms ae1-2051.vie20.core-backbone.com [81.95.15.49]
9 8 ms 7 ms 7 ms vix-vie.netarch.akamai.com [193.203.0.168]
10 6 ms 9 ms 7 ms a2-18-69-152.deploy.static.akamaitechnologies.com [2.18.69.152]
So how this works is Akamai will look at the source address of the resolver and return a node address based on that information. Since you’re using a PoP in PRG it should return a nearby node, but for some reason it returns a node address that’s either far away or faulty. I’ll open a support ticket and see if we can do anything.
