A body slam. reminds me of the old TV wrestling matches. Killer Kowalski, Gorgeous George… the referee who always looked the other way…am I really that old?
Well. After extensive debugging, I have isolated the problem with viewing the gocomics.com site. The content is served through assets.amuniversal.com. That domain is subverted by a content distribution network (cdngc.net), which intercepts queries and returns an IP that is geographically close to the query ip – a common hack due to the deficiencies of HTTP protocol for centralized content (such content should be using IPFS or other distributed protocol).
Normally, such CDNs continue to also work with normal DNS lookups according to internet standards. But this week, they dropped support for normal lookups – and the content is only viewable when using a DNS resolver that uses whatever proprietary protocol cdngc.net requires. So you guys are probably using your ISP resolver – something I, and others in the know, studiously avoid.
The dilbert.com site also uses amuniversal.com, and has the same problem (everything but the actual Dilbert cartoons loads). This is what gave me the clue as to the problem.
As a work around, I added an exception to my resolver to forward amuniversal.com and subdomains to Google DNS servers at 8.8.8.8 and 8.8.4.4.
@amuniversal.com – this may be a bug in your network. Doing a dig +trace assets.amuniversal.com ends up with a cname referencing wtxcdn.com, which has nameservers like dns2.cdn20.info – none of which will resolve.
J Short over 5 years ago
That’s it? Like our border policy. This is the 3rd time we have caught you crossing illegally; stop it.
Polsixe over 5 years ago
You’ve been told mister,
Ray*C over 5 years ago
A body slam. reminds me of the old TV wrestling matches. Killer Kowalski, Gorgeous George… the referee who always looked the other way…am I really that old?
tripwire45 over 5 years ago
Might as well do him in now Tarzan and get it over with.
Old Comic Strip Lover over 5 years ago
West sure recovered his composure fast.
Gent over 5 years ago
Ape man ain’t too bright is he?
Thorby over 5 years ago
Lord Greystoke ain’t THAT dumb!
stuart over 5 years ago
Well. After extensive debugging, I have isolated the problem with viewing the gocomics.com site. The content is served through assets.amuniversal.com. That domain is subverted by a content distribution network (cdngc.net), which intercepts queries and returns an IP that is geographically close to the query ip – a common hack due to the deficiencies of HTTP protocol for centralized content (such content should be using IPFS or other distributed protocol).
Normally, such CDNs continue to also work with normal DNS lookups according to internet standards. But this week, they dropped support for normal lookups – and the content is only viewable when using a DNS resolver that uses whatever proprietary protocol cdngc.net requires. So you guys are probably using your ISP resolver – something I, and others in the know, studiously avoid.
The dilbert.com site also uses amuniversal.com, and has the same problem (everything but the actual Dilbert cartoons loads). This is what gave me the clue as to the problem.
As a work around, I added an exception to my resolver to forward amuniversal.com and subdomains to Google DNS servers at 8.8.8.8 and 8.8.4.4.
@amuniversal.com – this may be a bug in your network. Doing a dig +trace assets.amuniversal.com ends up with a cname referencing wtxcdn.com, which has nameservers like dns2.cdn20.info – none of which will resolve.
jdb5169 over 5 years ago
Tarzan should ‘bitch slap’ him,then put a ‘sleeper hold’ on him,and give him to a pack of apes.