South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
Unable to resolve target system name wowhead.com.
Unable to resolve target system name wowhead.com.
Seeing some reports here yeah - if you can, please let me know how I can replicate the issues being seen so I can have it looked into.
Example: dnjs.cloudflare.com/ajax/libs/angular.js/1.2.20/angular.min.js
With the Afrihost DNS server I get:
Unable to resolve target system name cdnjs.cloudflare.com.
With Google 8.8.8.8
I get a resolve in 1ms:
Tracing route to cdnjs.cloudflare.com.cdn.cloudflare.net [198.41.215.182]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
......
traceroute to cdnjs.cloudflare.com.cdn.cloudflare.net (198.41.214.187), 64 hops max, 52 byte packets
1 router.asus.com (192.168.1.1) 1.066 ms 0.946 ms 0.754 ms
2 105-236-12-65-esr-lo.mtnbusiness.co.za (105.236.12.65) 4.825 ms 5.637 ms 5.654 ms
3 41.181.201.94 (41.181.201.94) 7.925 ms 6.062 ms 6.556 ms
4 tb-dca-2.za--qux-a.za.mtnbusiness.net (41.181.184.28) 6.237 ms 5.869 ms 5.779 ms
5 compj-cpt-1.mtnns.net (196.44.18.2) 8.374 ms 7.232 ms 7.220 ms
6 ls-cr-2--tb-cr-1.uk-b.mtnns.net (196.44.31.113) 150.933 ms 181.216 ms 150.166 ms
7 am-cr-1.nl--ls-cr-2.uk-a.mtnns.net (196.44.31.183) 159.472 ms 159.156 ms 159.201 ms
8 am-tpr-1.nl--am-cr-1.nl-a.mtn.net (209.212.111.141) 195.678 ms 260.963 ms 195.180 ms
9 xe-4-1-0.edge5.amsterdam1.level3.net (212.72.41.89) 174.537 ms 171.959 ms 168.402 ms
10 * * *
11 ae-130-3516.edge6.amsterdam1.level3.net (4.69.162.238) 161.208 ms
ae-240-3616.edge6.amsterdam1.level3.net (4.69.162.254) 159.841 ms
ae-130-3516.edge6.amsterdam1.level3.net (4.69.162.238) 158.528 ms
12 4.68.111.178 (4.68.111.178) 159.851 ms 159.928 ms 159.047 ms
13 cloudflare-ic-304618-adm-b4.c.telia.net (62.115.36.94) 195.608 ms 196.738 ms 197.350 ms
14 198.41.214.187 (198.41.214.187) 196.020 ms 195.596 ms 195.807 ms[/quote]
This is the tracert I get for this site.
Tracing route to www.mybroadband.co.za [197.242.89.170]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 9 ms 9 ms 10 ms 105-236-11-129-esr-lo.mtnbusiness.co.za [105.236
.11.129]
3 10 ms 48 ms 10 ms 41.181.178.41
4 11 ms 11 ms 35 ms 41.181.165.115
5 11 ms 11 ms 10 ms jh-dca-2.za--qux-q.za.mtnbusiness.net [196.31.18
0.4]
6 46 ms 11 ms 11 ms 196.44.0.224
7 98 ms 11 ms 10 ms 196.44.0.222
8 * * * Request timed out.
9 31 ms 30 ms 30 ms CORE.GP-CN-HET-MEE-1.TO.GP-MR-VOD-MEE-1.DFA.P2P.
10G.za.africainx.net [41.84.12.151]
10 30 ms 30 ms 30 ms 41.66.132.246
11 32 ms 31 ms 31 ms core-access-switch1.jnb1.host-h.net [197.189.193
.1]
12 32 ms 31 ms 36 ms row-access-switch1-row3-4.jnb1.host-h.net [197.1
89.193.36]
13 29 ms 29 ms 31 ms 197.242.89.170
Trace complete.
Are you able to open up the site though?
If I run a trace I'm setting some timeouts after Level3, this is outside of our network.
Do your results look similar?
Code:traceroute to cdnjs.cloudflare.com.cdn.cloudflare.net (198.41.214.187), 64 hops max, 52 byte packets 1 router.asus.com (192.168.1.1) 1.066 ms 0.946 ms 0.754 ms 2 105-236-12-65-esr-lo.mtnbusiness.co.za (105.236.12.65) 4.825 ms 5.637 ms 5.654 ms 3 41.181.201.94 (41.181.201.94) 7.925 ms 6.062 ms 6.556 ms 4 tb-dca-2.za--qux-a.za.mtnbusiness.net (41.181.184.28) 6.237 ms 5.869 ms 5.779 ms 5 compj-cpt-1.mtnns.net (196.44.18.2) 8.374 ms 7.232 ms 7.220 ms 6 ls-cr-2--tb-cr-1.uk-b.mtnns.net (196.44.31.113) 150.933 ms 181.216 ms 150.166 ms 7 am-cr-1.nl--ls-cr-2.uk-a.mtnns.net (196.44.31.183) 159.472 ms 159.156 ms 159.201 ms 8 am-tpr-1.nl--am-cr-1.nl-a.mtn.net (209.212.111.141) 195.678 ms 260.963 ms 195.180 ms 9 xe-4-1-0.edge5.amsterdam1.level3.net (212.72.41.89) 174.537 ms 171.959 ms 168.402 ms 10 * * * 11 ae-130-3516.edge6.amsterdam1.level3.net (4.69.162.238) 161.208 ms ae-240-3616.edge6.amsterdam1.level3.net (4.69.162.254) 159.841 ms ae-130-3516.edge6.amsterdam1.level3.net (4.69.162.238) 158.528 ms 12 4.68.111.178 (4.68.111.178) 159.851 ms 159.928 ms 159.047 ms 13 cloudflare-ic-304618-adm-b4.c.telia.net (62.115.36.94) 195.608 ms 196.738 ms 197.350 ms 14 198.41.214.187 (198.41.214.187) 196.020 ms 195.596 ms 195.807 ms[/quote][/QUOTE] On the Afrihost DNS I cannot even resolve the hostname.
Yes but sometimes I have to refresh several times before it opens. Some international sites don't open at all no matter how much I refresh, can't even do a traceroute for them.
*Edit
Seems to be working fine periodically. Works and then doesn't work.
Have you tried testing with another DNS server?
Very strange, I haven't picked up anything that's changed on our end.
If you see the problem again, please grab a full traceroute to the site - similar to what I've posted. It'll help identify where any potential issues are coming in.
HOW CAN YOU SO A TRACERT IF THE NAME IS NOT RESOLVING FFS???????????
It'll resolve as far as it can, doesn't mean the entire traceroute it going to be a problem![]()
It wasn't resolving at all.
Was getting this:
"Unable to resolve target system"