-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> nscd is not installed. I have not used it at any point. Did try on
> another machine and against different nameservers with the same result.
> One machine has search in resolv.conf the other doesn't.
>
> # curl
www.newegg.com
> curl: (6) Couldn't resolve host 'www.newegg.com'
You'll have to provide more information. strace output,
wireshark/tcpdump logs, ...
The problem I saw and which I fixed was that the server answering for
that domain deliberately doesn't reply to IPv6 (T_AAAA) queries. I.e.,
it depends on the client to time out. That's terribly bad practice and
the provider should change that.
Anyway, I think I fixed that in the new lookup code and, as I said, it
works for me. I cannot imagine what you're seeing.
So, make really sure you're using the -4 rpms and then run
strace -o LOG getent ahosts
www.newegg.com
and also capture the net traffic (just port 53 data) and stuff it all
into a new BZ.
There are two namservers in resolv.conf which might be the tripping
point? Sorry for failing to mention that before.
P.S John, I believe this is about the new glibc in fedora rawhide only
resolver code behaving differently than the old code and not about