Comment 40 for bug 241305

Mark A. Ziesemer (ziesemer) wrote :

This again appears to be broken, for both security.ubuntu.com and us.archive.ubuntu.com, at least.

Exactly as Jens had noted above - this is (also) an issue with AAAA records being provided, but not accessible. Though security.ubuntu.com appears to be in ever-so-slightly better shape than security.ubuntu.com.

Some current DNS lookups as of this writing:

security.ubuntu.com has AAAA address 2001:67c:1360:8c01::18
security.ubuntu.com has AAAA address 2001:67c:1562::17
security.ubuntu.com has AAAA address 2001:67c:1562::13
security.ubuntu.com has AAAA address 2001:67c:1562::15
security.ubuntu.com has AAAA address 2001:67c:1360:8c01::19
security.ubuntu.com has AAAA address 2001:67c:1562::16
security.ubuntu.com has AAAA address 2001:67c:1562::14

us.archive.ubuntu.com has AAAA address 2001:67c:1562::14
us.archive.ubuntu.com has AAAA address 2001:67c:1562::16
us.archive.ubuntu.com has AAAA address 2001:67c:1562::13
us.archive.ubuntu.com has AAAA address 2001:67c:1562::17
us.archive.ubuntu.com has AAAA address 2001:67c:1562::15

None of the 2001:67c:1562:: addresses are responding by IPv6, either over ping or HTTP. The two 2001:67c:1360:8c01:: addresses for security.ubuntu.com are properly responding, however.

Please investigate and resolve. Thanks!