Curiously, I can't reproduce this using any of the applications I've tried. While I do have some level of IPv6 networking, I've deliberately turned it off for this test, and in any case I'm testing at the tcpdump level; I can clearly see the A and AAAA queries going out in parallel, rather than what sojourner was seeing which was the AAAA query going out and then a long timeout.
That means I need to figure out what's different about our environments. One useful place to start would be an strace of a fairly simple client such as w3m. Could you please:
* install the strace and w3m packages
* run: strace -f -s 4096 -o w3m.trace w3m http://some/url/of/your/choice
* quit w3m once the page has loaded (shift-Q)
* attach w3m.trace to this bug
This may not be sufficient for me to work out what's wrong, but it will give me a bit more to go on.
Curiously, I can't reproduce this using any of the applications I've tried. While I do have some level of IPv6 networking, I've deliberately turned it off for this test, and in any case I'm testing at the tcpdump level; I can clearly see the A and AAAA queries going out in parallel, rather than what sojourner was seeing which was the AAAA query going out and then a long timeout.
That means I need to figure out what's different about our environments. One useful place to start would be an strace of a fairly simple client such as w3m. Could you please:
* install the strace and w3m packages some/url/ of/your/ choice
* run: strace -f -s 4096 -o w3m.trace w3m http://
* quit w3m once the page has loaded (shift-Q)
* attach w3m.trace to this bug
This may not be sufficient for me to work out what's wrong, but it will give me a bit more to go on.