dig AAAA mismatch

[IPv6-flagg]

I've been seeing a lot of "Result: Fail Reason: Record mismatch" on dig AAAA in user's dig query.

I'm trying to figure out what the reason is but it's not redly apparent to me. I'm having to chase several domain names a day to get one that will play nice with the daily aaaa test (all the other daily tests work fine). Be nice to know before I try and submit that there's a problem.

Thanks in advance for any help,
Neil

Here's the latest example, www.google.com.bd failed but www.enom.com worked just fine. Any ideas?

; <<>> DiG 9.8.3-P1 <<>> www.google.com.bd aaaa
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 56620
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;www.google.com.bd.      IN   AAAA

;; ANSWER SECTION:
www.google.com.bd.   116   IN   AAAA   2607:f8b0:400a:801::101f

;; Query time: 7 msec
;; SERVER: 10.0.1.1#53(10.0.1.1)
;; WHEN: Wed Apr  9 10:39:49 2014
;; MSG SIZE  rcvd: 63


Summary of user's dig query
Host name: www.google.com.bd
AAAA Record:2607:f8b0:4005:802::101f
Status: NOERROR
Result: Fail
Reason: Record mismatch

; <<>> DiG 9.8.3-P1 <<>> www.enom.com aaaa
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 42300
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;www.enom.com.         IN   AAAA

;; ANSWER SECTION:
www.enom.com.      473   IN   AAAA   2620:10f:5000:5000::2

;; Query time: 3 msec
;; SERVER: 10.0.1.1#53(10.0.1.1)
;; WHEN: Wed Apr  9 10:38:01 2014
;; MSG SIZE  rcvd: 58

[kcochran]

Sites which geolocate or round-robin replies are not going to be good ones for this.  On our side there's a verification query, which has to match.  When the site returned different results to the same query, odds are there won't be a match.  For example, same AAAA query, different reply.

;; ANSWER SECTION:
www.google.com.bd.   299   IN   AAAA   2607:f8b0:4005:802::1018

[IPv6-flagg]

Thanks! That makes total sense. I'll try a dig -x to grab the host name and see if that avoids future aaaa mismatch headaches.

Yours comes back to nuq05s02-in-x18.1e100.net and mine comes back to sea09s02-in-x1f.1e100.net

Cheers,
Neil