People may also want to read RFC 3646 which defines DHCPv6 options to
configure a DNS resolver.
We have considered _other_ ways to automatically configure a DNS
resolver in IPv6, but we haven't managed to reach consensus on any of
those proposals yet.
Margaret
At 9:55 AM +0200 8/15/05, Harald Tveit Alvestrand wrote:
Since nobody's mentioned the draft name yet, and we generally tell
people "go read the drafts"....
draft-ietf-dnsop-ipv6-dns-configuration-06.txt
Or - "there are 3 options. We can't pick one".
The document was approved by the IESG in July (but seems to be
waiting for an IESG note).
Harald
--On torsdag, august 11, 2005 16:09:54 +0200 Alexandru Petrescu
<alexandru(_dot_)petrescu(_at_)motorola(_dot_)com> wrote:
ljitsch van Beijnum wrote:
On 11-aug-2005, at 11:22, Brian E Carpenter wrote:
However, what may well be missing in the mix
is input from people who actually deploy and operate our stuff, and
live with its limitations and quirks every day. We need to understand
the indirect consequences of our choices: not "can it be coded and will
it interoperate?" but "will it drive service providers and users
crazy?"
Lack of a way to configure DNS resolvers automatically in IPv6
continues to drive me crazy.
I'm not sure I get it... DHCP distributes DNS resolvers, right? I'm
not sure whether the DHCPv4 can distribute DNS IPv6 resolver addresses
or is that restricted to DHCPv6. Would be nice if both did, just like
both dig/v4 and dig/v6 return both v4 and v6 addresses. I think PPP
over IPv6 doesn't do it.
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf