content-type: text/plain; charset="utf-8"
X-RT-Original-Encoding: utf-8
Content-Length: 1468

Yeah I know - was just using it to show that windows did have valid ipv6
and its tools were working.

So when will the code be updated?

On Mon, Jun 19, 2017 at 12:15 AM, Mark Andrews via RT <bind9-bugs@isc.org>
wrote:

>
> In message <rt-4.2.8-55908-1497699850-308.45401-3-0@isc.org>, "John
> Poznicek vi
> a RT" writes:
> > nslookup works and defaults to using ipv6 for dns
> > > nslookup
> > Default Server:  pfsense.local.lan
> > Address:  2001:470:1f11:9c4::1
>
> We need to update the windows code that retrieves the list of name
> server addresses from the system from GetNetworkParams to
> GetAdaptersAddresses based on a little Googling.
>
> * GetNetworkParams only returns the IPv4 addresses.
> * GetAdaptersAddresses returns both IPv4 and IPv6 addresses
>   depending upon the calling arguments.
>
> Populating resolv.conf with the nameserver address rather that
> reading them from the system with GetNetworkParams/GetAdaptersAddresses
> will let 'dig -6' work.  This does have the obvious limitation that
> the contents are likely to get out of date as the OS will not be
> updating it.
>
> 'dig -6 @<servername>' works regardless of the method used to
> populate the default server list.
>
> e.g.
>         dig -6 @f.root-servers.net soa .
>
> Note: the nslookup above is Microsoft's version not BIND's.
>
> --
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org
>
>
>