As part of troubleshooting, the query from the application normally goes through nscd, which then makes the query on the wire, caches the result, sends it to the kernel for sorting, and then returns it to the application. It's not yet clear where in that process something is going awry, so knowing for _certain_ that the data are good at some known point and then bad afterwards would probably help.
I flushed the caches with 'nscd -i <cache name>' (hosts, ipnodes). In fact I had to do that in order to force the query generated by ping to get resolved by DNS (so that Wireshark can capture it).
Do you see the same anomalous results if you do "getent ipnodes host.name.here"?
$ getent ipnodes www.sun.com 2002:5f52:81a4:1::1 www.sun.com www.sun.com.podzimek.org 137.254.16.57 www.sun.com www.sun.com.podzimek.org $ getent hosts www.sun.com 137.254.16.57 www.sun.com Well, I have no idea where the 'podzimek.org' suffix comes from. Andrej
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ networking-discuss mailing list [email protected]
