1. It is my understanding
that WinXP even with SP2 still cannot actually do
DNS resolution (lookup)
over IPv6, only over IPv4.
2. For dual stack, you should configure
your DNS server(s) to publish both
A (IPv4) and AAAA (IPv6)
records (and corresponding IPv4 and IPv6 PTR
records in appropriate
reverse zones for each). The DNS server(s) ideally
should be accessible
over both IPv4 and IPv6.
3. *BSD nodes (maybe also Linux, not sure)
can do DNS resolution over
either IPv4 or IPv6. I
understand that Vista (NG of WinXP) should also
be able to do this. If
you have ONLY WInXP nodes, it is in theory
superfluous to have your
DNS servers accept connections over IPv6,
as that will never be
used (though clients can still obtain both A and AAAA
records over IPv4, and
make actual connections to the looked-up nodes
over IPv6, assuming AAAA
records are present).
Note that what protocol you communicate
with the DNS server has nothing
to do with what kind of addresses (IPv4,
IPv6 or both) are retrieved.
Most client computers (DNS resolvers) that
support IPv6 will (and should)
use the IPv6 addresses preferentially over
IPv4 when both are returned
from the DNS.
If you have multiple DNS servers, ALL
should publish both A and AAAA
records.
Currently, with limitations of WinXP SP2, I
would recommend running in
a dual stack network (all nodes support and
have addresses for both IPv4
and IPv6), and make DNS servers accept
connections over both IPv4 and
IPv6.
I don't believe any node I've worked with
allows you to configure one (set
of) DNS address(es) for IPv4 lookups and a
different one (set of) addresses
for IPv6 lookups.
It all kind of comes together at the DNS
server.
Someday, it will be possible to have pure
IPv6 only network segments,
with DNS servers holding only AAAA records.
There are two problems
with that today - WinXP DNS resolution and
issues of returning more
than 512 bytes of root hint data in a
single UDP packet (a limitation of
the worldwide DNS system design a lot of
people are trying to find
solutions to as we speak). Until then,
deploy dual stack - it will work
great.
Any MS experts out there who can clarify
DNS resolver situation of
MS clients for certain?
Lawrence Hughes
InfoWeapons Corp. - www.infoweapons.com
From: [EMAIL PROTECTED] on behalf of mustafa sahin
Sent: Mon 1/2/2006 1:58 AM
To: [email protected]
Subject: ipv6 dns server.
Hi all,
My problem is; I defined an ipv6 dns server to my WinXP dual stack client. It also has another dns server with ipv4 address. It checks firstly ipv4 dns-server, not hte ipv6 one. To fix this problem i removed the other ipv4 dns-server address and write the ipv4 address of my ipv6 dns server. It works with this opinion. Does anyone have and idea how i can activate 2 different dns servers; one is for ipv4 querries one is for ipv6. Or how can i make ipv6 dns-server as a first option to resolve the name to ip in my client.
Thanks everyone who reads this messege. Happy new year..
-
Mustafa
My problem is; I defined an ipv6 dns server to my WinXP dual stack client. It also has another dns server with ipv4 address. It checks firstly ipv4 dns-server, not hte ipv6 one. To fix this problem i removed the other ipv4 dns-server address and write the ipv4 address of my ipv6 dns server. It works with this opinion. Does anyone have and idea how i can activate 2 different dns servers; one is for ipv4 querries one is for ipv6. Or how can i make ipv6 dns-server as a first option to resolve the name to ip in my client.
Thanks everyone who reads this messege. Happy new year..
-
Mustafa
