Diagnosing amazon

gistfile1.txt

# dig api.production.aws.neds.com
; <<>> DiG 9.10.6 <<>> api.production.aws.neds.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 12273
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1



# dig +trace api.production.aws.neds.com
api.production.aws.neds.com. 60	IN	A	54.153.251.4
api.production.aws.neds.com. 60	IN	A	54.66.161.38
production.aws.neds.com. 172800	IN	NS	ns-1519.awsdns-61.org.
production.aws.neds.com. 172800	IN	NS	ns-1831.awsdns-36.co.uk.
production.aws.neds.com. 172800	IN	NS	ns-450.awsdns-56.com.
production.aws.neds.com. 172800	IN	NS	ns-955.awsdns-55.net.
;; Received 225 bytes from 2600:9000:5305:ef00::1#53(ns-1519.awsdns-61.org) in 21 ms



# dig +short ns-1519.awsdns-61.org
205.251.197.239



# dig +short aaaa ns-1519.awsdns-61.org
2600:9000:5305:ef00::1



# dig @205.251.197.239 api.production.aws.neds.com
; <<>> DiG 9.10.6 <<>> @205.251.197.239 api.production.aws.neds.com
; (1 server found)
;; global options: +cmd
;; connection timed out; no servers could be reached



# dig @2600:9000:5305:ef00::1 api.production.aws.neds.com
; <<>> DiG 9.10.6 <<>> @2600:9000:5305:ef00::1 api.production.aws.neds.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 24663
;; flags: qr aa rd; QUERY: 1, ANSWER: 2, AUTHORITY: 4, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;api.production.aws.neds.com.	IN	A

;; ANSWER SECTION:
api.production.aws.neds.com. 60	IN	A	54.153.251.4
api.production.aws.neds.com. 60	IN	A	54.66.161.38

;; AUTHORITY SECTION:
production.aws.neds.com. 172800	IN	NS	ns-1519.awsdns-61.org.
production.aws.neds.com. 172800	IN	NS	ns-1831.awsdns-36.co.uk.
production.aws.neds.com. 172800	IN	NS	ns-450.awsdns-56.com.
production.aws.neds.com. 172800	IN	NS	ns-955.awsdns-55.net.

;; Query time: 21 msec
;; SERVER: 2600:9000:5305:ef00::1#53(2600:9000:5305:ef00::1)
;; WHEN: Tue Apr 24 22:33:03 AEST 2018
;; MSG SIZE  rcvd: 225

And to prove that the IPv4 addresses normally resolve correctly...

# dig @205.251.197.239 api.production.aws.neds.com

; <<>> DiG 9.10.6 <<>> @205.251.197.239 api.production.aws.neds.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 23375
;; flags: qr aa rd; QUERY: 1, ANSWER: 2, AUTHORITY: 4, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;api.production.aws.neds.com.	IN	A

;; ANSWER SECTION:
api.production.aws.neds.com. 60	IN	A	54.66.161.38
api.production.aws.neds.com. 60	IN	A	54.153.251.4

;; AUTHORITY SECTION:
production.aws.neds.com. 172800	IN	NS	ns-1519.awsdns-61.org.
production.aws.neds.com. 172800	IN	NS	ns-1831.awsdns-36.co.uk.
production.aws.neds.com. 172800	IN	NS	ns-450.awsdns-56.com.
production.aws.neds.com. 172800	IN	NS	ns-955.awsdns-55.net.

;; Query time: 21 msec
;; SERVER: 205.251.197.239#53(205.251.197.239)
;; WHEN: Tue Apr 24 23:16:01 AEST 2018
;; MSG SIZE  rcvd: 225

This tweet fits

https://twitter.com/sajal/status/988768982118252545

Some AWS Route53 IPs were being mis-routed today (bad route announced via HE) https://pulse.turbobytes.com/results/5adf2844ecbe40692e003ad2/ … . Appears to be fixed now.