The apt source list for security update is by default configured to security.ubuntu.com.
When you have a system using only IPv6 (and having not access to IPv4 via NAT-PT),
security.ubuntu.com is only reachable in IPv4.
It would be wise to configure an AAAA record to security.ubuntu.com to at least
point to one of the many mirrors supporting IPv6 connectivity.
That would avoid system running natively in IPv6 to lack by default the security
update.
Thanks a lot,
Kind regards
PS : I checked this as being a security vulnerability but this is more a configuration issue
on the Ubuntu network infrastructure than a real security vulnerability:
Dear,
The apt source list for security update is by default configured to security. ubuntu. com.
When you have a system using only IPv6 (and having not access to IPv4 via NAT-PT),
security.ubuntu.com is only reachable in IPv4.
It would be wise to configure an AAAA record to security.ubuntu.com to at least
point to one of the many mirrors supporting IPv6 connectivity.
That would avoid system running natively in IPv6 to lack by default the security
update.
Thanks a lot,
Kind regards
PS : I checked this as being a security vulnerability but this is more a configuration issue
on the Ubuntu network infrastructure than a real security vulnerability:
A DNS AAAA request :
dig -t AAAA security.ubuntu.com
; <<>> DiG 9.4.1-P1 <<>> -t AAAA security.ubuntu.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26872
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION: ubuntu. com. IN AAAA
;security.
;; AUTHORITY SECTION: canonical. com. 2008061805 10800 3600 604800 3600
ubuntu.com. 3600 IN SOA ns1.canonical.com. hostmaster.
;; Query time: 134 msec 1#53(127. 0.0.1)
;; SERVER: 127.0.0.
;; WHEN: Thu Jun 19 15:17:39 2008
;; MSG SIZE rcvd: 98