When I do `dig whoami.akamai.net AAAA` on my computer, I got

```
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 32160
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4000
;; QUESTION SECTION:
;whoami.akamai.net.     IN  AAAA

```

But if I try from @1.1.1.1 or @8.8.8.8 or even OpenDNS, I can get a AAAA RR.

What prevent my local dig not to get a result?

According to the RFC4074 (<https://www.rfc-editor.org/rfc/rfc4074#section-3>):

> 
> Suppose that an authoritative server has an A RR but has no AAAA RR
> for a host name. Then, the server should return a response to a query
> for an AAAA RR of the name with the response code (RCODE) being 0
> (indicating no error) and with an empty answer section (see Sections
> 4.3.2 and 6.2.4 of RFC 1034). Such a response indicates that there is at least one RR of a different type than AAAA for the queried name, and
> the stub resolver can then look for A RRs.
> 
> 
> 

I thought it was what happening, but it looks like the domain has an existing AAAA record (since the major dns resolver have it). I do not get what is happening here.