A race would have been fun, but for my bug(s), pointing /etc/resolv.conf straight to ns.ubuntu.com satisfies apt-get.
The difference? ns.ubuntu.com is authoritative. So is apt-get's use of getaddrinfo(3) throwing out non-authoritative responses?
...If it is, is there a reason for this? Did I miss a memo where non-authoritative caches are now considered dangerous?
Of course, `dig` hand-crafts its own queries so it's only good for looking at DNS "reality," not resolver behavior.
*bonk* - the sound of my head hitting the desk.
New theory:
A race would have been fun, but for my bug(s), pointing /etc/resolv.conf straight to ns.ubuntu.com satisfies apt-get.
The difference? ns.ubuntu.com is authoritative. So is apt-get's use of getaddrinfo(3) throwing out non-authoritative responses?
...If it is, is there a reason for this? Did I miss a memo where non-authoritative caches are now considered dangerous?
Of course, `dig` hand-crafts its own queries so it's only good for looking at DNS "reality," not resolver behavior.