Hello! Don't suppose there's a Yahoo admin in the DNS department that can investigate/debug a Geolocation issue? It appears that Yahoo's Geolocation is putting CenturyLink's IPv6 addresses as being in .BR, causing not only the two CL/Qwest recursive servers (205.171.2.65/205.171.3.65/2001:428::1/2001:428::2), but recusive servers hosted on biz customer IPv6 6RD ranges to return non-US Yahoo servers (and be agonizingly slow). ===== View from local powerdns recursor, dual stacked, but preferring ipv6 for resolving: root@noc:~# dig mg.mail.yahoo.com @127.0.0.2 ; <<>> DiG 9.9.5-9+deb8u9-Debian <<>> mg.mail.yahoo.com @127.0.0.2 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 50638 ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;mg.mail.yahoo.com. IN A ;; ANSWER SECTION: mg.mail.yahoo.com. 1349 IN CNAME fd-geoycpi-uno.gycpi.b.yahoodns.net. fd-geoycpi-uno.gycpi.b.yahoodns.net. 300 IN A 200.152.162.161 fd-geoycpi-uno.gycpi.b.yahoodns.net. 300 IN A 200.152.162.135 ;; Query time: 240 msec ;; SERVER: 127.0.0.2#53(127.0.0.2) ;; WHEN: Fri Jan 27 17:20:52 MST 2017 ;; MSG SIZE rcvd: 116 ===== View from CL/Qwest IPv4 (likely dual stacked) and IPv6 recursors: root@noc:~# dig mg.mail.yahoo.com @205.171.2.65 ; <<>> DiG 9.9.5-9+deb8u9-Debian <<>> mg.mail.yahoo.com @205.171.2.65 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 8308 ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;mg.mail.yahoo.com. IN A ;; ANSWER SECTION: mg.mail.yahoo.com. 758 IN CNAME fd-geoycpi-uno.gycpi.b.yahoodns.net. fd-geoycpi-uno.gycpi.b.yahoodns.net. 138 IN A 200.152.162.161 fd-geoycpi-uno.gycpi.b.yahoodns.net. 138 IN A 200.152.162.135 ;; Query time: 17 msec ;; SERVER: 205.171.2.65#53(205.171.2.65) ;; WHEN: Fri Jan 27 17:21:35 MST 2017 ;; MSG SIZE rcvd: 127 root@noc:~# dig mg.mail.yahoo.com @2001:428::1 ; <<>> DiG 9.9.5-9+deb8u9-Debian <<>> mg.mail.yahoo.com @2001:428::1 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 24138 ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;mg.mail.yahoo.com. IN A ;; ANSWER SECTION: mg.mail.yahoo.com. 464 IN CNAME fd-geoycpi-uno.gycpi.b.yahoodns.net. fd-geoycpi-uno.gycpi.b.yahoodns.net. 214 IN A 200.152.162.161 fd-geoycpi-uno.gycpi.b.yahoodns.net. 214 IN A 200.152.162.135 ;; Query time: 46 msec ;; SERVER: 2001:428::1#53(2001:428::1) ;; WHEN: Fri Jan 27 17:23:38 MST 2017 ;; MSG SIZE rcvd: 127 ===== Google recursor for reference: root@noc:~# dig mg.mail.yahoo.com @8.8.8.8 ; <<>> DiG 9.9.5-9+deb8u9-Debian <<>> mg.mail.yahoo.com @8.8.8.8 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 13327 ;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;mg.mail.yahoo.com. IN A ;; ANSWER SECTION: mg.mail.yahoo.com. 1459 IN CNAME fd-geoycpi-uno.gycpi.b.yahoodns.net. fd-geoycpi-uno.gycpi.b.yahoodns.net. 184 IN A 216.115.100.124 fd-geoycpi-uno.gycpi.b.yahoodns.net. 184 IN A 208.71.44.31 fd-geoycpi-uno.gycpi.b.yahoodns.net. 184 IN A 216.115.100.123 fd-geoycpi-uno.gycpi.b.yahoodns.net. 184 IN A 208.71.44.30 ;; Query time: 27 msec ;; SERVER: 8.8.8.8#53(8.8.8.8) ;; WHEN: Fri Jan 27 17:21:59 MST 2017 ;; MSG SIZE rcvd: 159 For reference, CL/Qwest's IPv6 range for 6RD is 2602::/24. This appears to be impacting Yahoo, Yahoo Mail, Flickr, etc (aka Yahoo owned properties). Thanks! -- Brielle Bruns The Summit Open Source Development Group http://www.sosdg.org / http://www.ahbl.org
There is a thread going on the outages mailing list talking about this issue. Seems to be no failures but increased latency to ns1.yahoo.com and ns3.yahoo.com with trace routes showing USA traffic hitting Asia on v6. Nolan
On Jan 27, 2017, at 6:30 PM, Brielle Bruns <bruns@2mbit.com> wrote:
Hello!
Don't suppose there's a Yahoo admin in the DNS department that can investigate/debug a Geolocation issue?
It appears that Yahoo's Geolocation is putting CenturyLink's IPv6 addresses as being in .BR, causing not only the two CL/Qwest recursive servers (205.171.2.65/205.171.3.65/2001:428::1/2001:428::2), but recusive servers hosted on biz customer IPv6 6RD ranges to return non-US Yahoo servers (and be agonizingly slow).
===== View from local powerdns recursor, dual stacked, but preferring ipv6 for resolving:
root@noc:~# dig mg.mail.yahoo.com @127.0.0.2
; <<>> DiG 9.9.5-9+deb8u9-Debian <<>> mg.mail.yahoo.com @127.0.0.2 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 50638 ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION: ;mg.mail.yahoo.com. IN A
;; ANSWER SECTION: mg.mail.yahoo.com. 1349 IN CNAME fd-geoycpi-uno.gycpi.b.yahoodns.net. fd-geoycpi-uno.gycpi.b.yahoodns.net. 300 IN A 200.152.162.161 fd-geoycpi-uno.gycpi.b.yahoodns.net. 300 IN A 200.152.162.135
;; Query time: 240 msec ;; SERVER: 127.0.0.2#53(127.0.0.2) ;; WHEN: Fri Jan 27 17:20:52 MST 2017 ;; MSG SIZE rcvd: 116
===== View from CL/Qwest IPv4 (likely dual stacked) and IPv6 recursors:
root@noc:~# dig mg.mail.yahoo.com @205.171.2.65
; <<>> DiG 9.9.5-9+deb8u9-Debian <<>> mg.mail.yahoo.com @205.171.2.65 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 8308 ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;mg.mail.yahoo.com. IN A
;; ANSWER SECTION: mg.mail.yahoo.com. 758 IN CNAME fd-geoycpi-uno.gycpi.b.yahoodns.net. fd-geoycpi-uno.gycpi.b.yahoodns.net. 138 IN A 200.152.162.161 fd-geoycpi-uno.gycpi.b.yahoodns.net. 138 IN A 200.152.162.135
;; Query time: 17 msec ;; SERVER: 205.171.2.65#53(205.171.2.65) ;; WHEN: Fri Jan 27 17:21:35 MST 2017 ;; MSG SIZE rcvd: 127
root@noc:~# dig mg.mail.yahoo.com @2001:428::1
; <<>> DiG 9.9.5-9+deb8u9-Debian <<>> mg.mail.yahoo.com @2001:428::1 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 24138 ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;mg.mail.yahoo.com. IN A
;; ANSWER SECTION: mg.mail.yahoo.com. 464 IN CNAME fd-geoycpi-uno.gycpi.b.yahoodns.net. fd-geoycpi-uno.gycpi.b.yahoodns.net. 214 IN A 200.152.162.161 fd-geoycpi-uno.gycpi.b.yahoodns.net. 214 IN A 200.152.162.135
;; Query time: 46 msec ;; SERVER: 2001:428::1#53(2001:428::1) ;; WHEN: Fri Jan 27 17:23:38 MST 2017 ;; MSG SIZE rcvd: 127
===== Google recursor for reference:
root@noc:~# dig mg.mail.yahoo.com @8.8.8.8
; <<>> DiG 9.9.5-9+deb8u9-Debian <<>> mg.mail.yahoo.com @8.8.8.8 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 13327 ;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;mg.mail.yahoo.com. IN A
;; ANSWER SECTION: mg.mail.yahoo.com. 1459 IN CNAME fd-geoycpi-uno.gycpi.b.yahoodns.net. fd-geoycpi-uno.gycpi.b.yahoodns.net. 184 IN A 216.115.100.124 fd-geoycpi-uno.gycpi.b.yahoodns.net. 184 IN A 208.71.44.31 fd-geoycpi-uno.gycpi.b.yahoodns.net. 184 IN A 216.115.100.123 fd-geoycpi-uno.gycpi.b.yahoodns.net. 184 IN A 208.71.44.30
;; Query time: 27 msec ;; SERVER: 8.8.8.8#53(8.8.8.8) ;; WHEN: Fri Jan 27 17:21:59 MST 2017 ;; MSG SIZE rcvd: 159
For reference, CL/Qwest's IPv6 range for 6RD is 2602::/24.
This appears to be impacting Yahoo, Yahoo Mail, Flickr, etc (aka Yahoo owned properties).
Thanks!
-- Brielle Bruns The Summit Open Source Development Group http://www.sosdg.org / http://www.ahbl.org
On 1/27/17 5:34 PM, Nolan Berry wrote:
There is a thread going on the outages mailing list talking about this issue. Seems to be no failures but increased latency to ns1.yahoo.com and ns3.yahoo.com with trace routes showing USA traffic hitting Asia on v6.
Nolan
Interesting - these performance issues have been going on for around 3 weeks now, I just tonight decided to try and get to the bottom of it and did actual diagnostics (and noticed the issues with geolocation). Good to know I'm not the only one! -- Brielle Bruns The Summit Open Source Development Group http://www.sosdg.org / http://www.ahbl.org
participants (2)
-
Brielle Bruns
-
Nolan Berry