Closed
Bug 1077267
Opened 10 years ago
Closed 10 years ago
more apparent ipv6 support on IRC
Categories
(Infrastructure & Operations Graveyard :: Infrastructure: IRC, task)
Infrastructure & Operations Graveyard
Infrastructure: IRC
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: gcox, Assigned: dparsons)
References
Details
"IPv6 support" was listed as a feature of the new IRC network. And it has it. BUT:
irc.m.o doesn't have a AAAA. One lone server, whose name doesn't indicate it's a v6 host, does. Internals can figure it out from mana, but, publicly/documentedly, it'd be good to have the v6 support attached to a proper hostname (e.g ipv6.irc.m.o) rather than the behind-the-scenes name.
Assignee | ||
Comment 1•10 years ago
|
||
It was meant to have AAAA at launch tonight, but we're using Dynect's "Traffic Management" feature (geodns) which is not making it easy to have an AAAA at the root node. It will be sorted out soon.
Assignee: infra → dparsons
On this topic, suggest creating ipv6.irc.mozilla.org as a static AAAA record for bruford for users who desire IPv6 *only*, with no fallback to IPv4 (and to provide a simpler test platform for "can i use ipv6", too).
Assignee | ||
Comment 3•10 years ago
|
||
Fixed!
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•10 years ago
|
Component: Infrastructure: Other → Infrastructure: IRC
QA Contact: jdow → dparsons
Updated•5 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•