Comment # 16
              on bug 4018
              from  Chris Maynard
        (In reply to comment #15)
> Which still hasn't happened...
Not sure when it was done, but c-ares was updated to c-ares-1.9.1 at some
point.  Can someone test/verify if that is sufficient enough to resolve this
bug?
The following is essentially the crux of the bug, as I understand it.  I mean,
the lack of IPv6 support was the reason for looking into alternatives to
c-ares, was it not?:
(In reply to comment #3)
> Basically, as adns, it refuses to query v6 nameservers (and wrongly fallback
> to localhost) making it useless on v6-only nets.
(P.S. c-ares 1.10.0 was released on 12-May-2013, which includes some
IPv6-related fixes, so maybe another update is in order?)
         
      
      
      You are receiving this mail because:
      
      
          - You are the assignee for the bug.
 
          - You are watching all bug changes.