Last modified: 2012-12-21 16:51:43 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T43270, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 41270 - No IPv6 addresses on Wikimedia nameservers ns(0-2).wikimedia.org
No IPv6 addresses on Wikimedia nameservers ns(0-2).wikimedia.org
Status: NEW
Product: Wikimedia
Classification: Unclassified
DNS (Other open bugs)
wmf-deployment
All All
: Low normal with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
: ipv6, ops
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-10-22 14:46 UTC by Jasper Deng
Modified: 2012-12-21 16:51 UTC (History)
5 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Jasper Deng 2012-10-22 14:46:22 UTC
http://meta.wikimedia.org/wiki/Talk:IPv6_initiative#Domain_servers

Because ns(0-2).wikimedia.org are missing IPv6 addresses, DNS lookups on IPv6-only clients fail to reach the Wikimedia domains, according to that thread, which makes sense because they are unable to reach a Wikimedia nameserver.
Comment 1 Andre Klapper 2012-10-22 18:59:47 UTC
I've created RT #3772
Comment 2 Andre Klapper 2012-10-22 22:05:14 UTC
Answer:
"That's because we do GSLB / geo load balancing based on IPv4-only geoip data. Until that can change and work well enough with IPv6 too, we can't put IPv6 addresses on our NS records and have our DNS auth servers answer on IPv6, unfortunately."
Comment 3 Jasper Deng 2012-10-23 00:52:21 UTC
IPv6 geolocation databases do exist, but no reliable sites exist to query such databases, so the WMF would have to host its own. Hhm...
Comment 4 Faidon Liambotis 2012-10-27 09:50:32 UTC
We don't query external databases for both privacy, performance and resiliency reasons. MaxMind does provide an IPv6 database but it's of subpar quality compared to their IPv4 database (that we already use).

However, there's a larger issue: our DNS infrastructure needs to be changed; we currently use PowerDNS' GeoIP module (which was written by Mark specifically for this use and merged upstream) which doesn't support IPv6 at all. It's not just a matter of replacing a file on the filesystem.

So, it's definitely our agenda, as part of some larger pending DNS changes, but it's not something that can be easily done.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links