https://bugzilla.novell.com/show_bug.cgi?id=462769
User luca.gugelmann@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=462769#c4
--- Comment #4 from Luca Gugelmann 2008-12-30 15:15:15 MST ---
Further testing showed that once every few dozen queries the AF_UNSPEC case
returns a correct answer. I tried to reproduce it and looking at the wireshark
logs stumbled upon the following behavior:
- on an AF_INET query a request for the A record goes out and the correct
answer comes in. Everything ok.
- on an AF_INET6 query a request for the AAAA record goes out and "not
implemented" is the router's answer (as expected). (This is repeated 4 times.)
- on an AF_UNSPEC query a request for the A record goes out, then a request for
the AAAA record goes out, then the answer for the AAAA query comes in (not
implemented) and finally the answer to the A query. Note that my router answers
the queries in reverse order. In this case getaddrinfo fails. Once in a while
the order in which the answers come in is correct (I'm on a wireless network,
so I assume sometimes the first packet is delayed). When the order of the
answers is consistent with the order of the queries (that is answer to A first,
AAAA later) getaddrinfo returns the correct ip.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.