* Mark Kamichoff:
Hi -
The problem is that the DNS server of your ISP does not conform to the
RFC and only answer to the query with a void answer. It never
answer to the A query, so the glibc resolver can only conclude the
whole query has no answer.
Just a thought, many DNS ALGs on
Hi -
The problem is that the DNS server of your ISP does not conform to the
RFC and only answer to the query with a void answer. It never
answer to the A query, so the glibc resolver can only conclude the
whole query has no answer.
Just a thought, many DNS ALGs on firewalls (eg,
Mark Kamichoff a écrit :
Hi -
The problem is that the DNS server of your ISP does not conform to the
RFC and only answer to the query with a void answer. It never
answer to the A query, so the glibc resolver can only conclude the
whole query has no answer.
Just a thought, many DNS
On Mon, Mar 16, 2009 at 05:16:13PM +0100, Aurelien Jarno wrote:
I don't think this behaviour is allowed by the RFC. Then the problem
is in the firewall and not the DNS, but the result is exactly the same
for the user.
Correct, I'm just moving the finger pointing to the firewall instead of
the
Mark Kamichoff a écrit :
On Mon, Mar 16, 2009 at 05:16:13PM +0100, Aurelien Jarno wrote:
I don't think this behaviour is allowed by the RFC. Then the problem
is in the firewall and not the DNS, but the result is exactly the same
for the user.
Correct, I'm just moving the finger pointing to
Hello,
it seems that DNS resolver is grossly confused, and sends
two DNS requests on same socket back to back (strace below is
from 'lynx http://www.jeep.com'). In first one DNS server
responded only to second packet sent by resolver, and resolve
failed (after that mdns was tried, and
Processing commands for cont...@bugs.debian.org:
forcemerge 516218 519774
Bug#516218: getaddrinfo not working while gethostbyname works
Bug#519774: libc6: causes many programs not to be able to resolve dns addresses
Forcibly Merged 516218 519774.
thanks
Stopping processing here.
Please
forcemerge 516218 519774
thanks
On Sun, Mar 15, 2009 at 07:20:42AM +0100, Petr Vandrovec wrote:
Hello,
it seems that DNS resolver is grossly confused, and sends
two DNS requests on same socket back to back (strace below is
from 'lynx http://www.jeep.com'). In first one DNS server
Package: libc6
Version: 2.9-4
Severity: grave
Justification: renders package unusable
This problem is with libc6 2.9-4, althogh my system shows below it's
using 2.7-18. I downgraded to avoid the problem.
After upgrading to 2.9-4 most programs on my system are no longer able
to resolve dns
9 matches
Mail list logo