returns incorrect NS records


We are seeing reproducible behaviour in Australia with the wrong NS records being returned for DNS should be handled by Akamai according to Whois. Queries result in an nxdomain. Would paste a dig, but because I’m a new user I can’t.

Apparently this is not the same in other regions.


You can still paste the dig text into your message if it’s still not letting you upload an image.

dig ns @

; <<>> DiG 9.10.3-P4-Ubuntu <<>> ns @
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 8200
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1

; EDNS: version: 0, flags:; udp: 1536

;; ANSWER SECTION: 1742 IN NS 1742 IN NS 1742 IN NS 1742 IN NS

That’s odd… There really is an zone on those nameservers.

(Route 53 doesn’t validate users really control a zone.)

Maybe Adobe was running an experiment?

Or there was a cache poisoning attack…?

Yep - it wouldn’t let me paste it because the nameservers looked like links, and you are limited to no more than two links per post when you are new! An admin has approved the dig through at some stage following this, because I had pasted in a reply :slight_smile:

As of around lunch time, Sydney time, Cloudflare was returning the correct records again.