110565 - IPv6: DNS: Win32 builds do not query for AAAA records

Status: RESOLVED FIXED

(Core :: Networking, defect, P1)

Description

[Shin'ichiro TAYA]

On Win32 platform, IPv6 support is missing.
There are two problems

1.No DNS support for IPv6 address resolution.
mozilla uses async DNS resolv function for Win32/IPv4, but there is no async
version of IPv6 resolve function on Win32.

2.IPv4 mapped IPv6 address
mozilla converts IPv4 address to IPv4 mapped IPv6 address internally
And try to connect on AF_INET6 socket.
But WinXP doesn't support IPv4 mapped IPv6 address.
If mozilla use same method to support IPv6 like other OSes that suport IPv4
mapped IPv6 address, IPv4 connection will be broken on WinXP.

Comment 1

[Wan-Teh Chang]

This is really an NSPR bug.

We can either change the product to NSPR, or
open an NSPR bug and make this bug depend on
the NSPR bug.

Comment 2

[neeti]

nspr

Comment 3

[davew-bugz2]

Also affects Windows 2000 using Microsoft research IPv6 stack as of Mozilla1.1b

Does problem #1 (no DNS support) stop IPv6 support in the browser? It's pretty
normal to use IPv4 DNS transport to return IPv6 records (AAAA, A6, etc).

Comment 4

[John G. Myers]

I believe problem #1 is an inability to look up AAAA records at all.

Comment 5

[Wan-Teh Chang]

My statement in comment #1 is wrong.  This should
be a Browser:Networking bug.  Problem #1
(WSAAsyncGetHostByName can't look up IPv6 addresses)
is definitely a Necko issue.

Problem #2 (Windows XP doesn't support IPv4-mapped
IPv6 addresses) can be handled in NSPR.  I opened
NSPR bug 175340 for problem #2 and made this bug
depend on it.

Comment 6

[Doug Turner (:dougt)]

-> gordon

Comment 7

[Darin Fisher]

just to summarize what this means for necko... the XP_WIN codepath needs to
simply be the same as the XP_UNIX codepath.  of course, this may impact
performance negatively, so perhaps support for IPv6 is a good reason to start
using a thread pool for the XP_UNIX DNS impl.

Comment 8

[Jo Hermans]

*** Bug 182088 has been marked as a duplicate of this bug. ***

Comment 9

[benc]

Based on wtc's comments, I've narrowed the scope of the summary.

Comment 10

[Olivier Cahagne]

*** Bug 218388 has been marked as a duplicate of this bug. ***

Comment 11

[Darin Fisher]

-> me

Comment 12

[Darin Fisher]

ok, this is fixed now that my patch for bug 205726 is in =)

NOTE: it is only fixed if you are running WinXP (or if you have a sufficiently
upgraded version of ws2_32.dll on your system).