Subject: RE: [dhcwg] Re: WG last call ondraft-ietf-dhc-dhcpv6-opt-dnsconfig-02.txt

From: "BELOEIL Luc FTRD/DMI/CAE" <[email-masked]>
Date: Fri, 21 Feb 2003 14:20:45 +0100

[ post by non-subscriber.  with the massive amount of spam, it is easy to miss
  and therefore delete posts by non-subscribers.  if you wish to regularly
  post from an address that is not subscribed to this mailing list, send a
  message to <listname>[email-masked] and ask to have the alternate
  address added to the list of addresses from which submissions are
  automatically accepted. ]

> De : Pekka Savola [mailto:[email-masked]]
>=20
>=20
> On Fri, 21 Feb 2003, BELOEIL Luc FTRD/DMI/CAE wrote:
> > > > Implementation decision, but I guess typically the=20
> results of the
> > > > latest query take precedence.  I don't see a problem=20
> here, myself.
> > >=20
> > > Unpredictable behavior. Difficult to debug.
> > >=20
> > > 	 - Alain.
> >=20
> > Good remark! I understand the point/issue if IPv6 provider=20
> is not the
> > same as IPv4 one. By that way the node may not have the same global
> > vision of the Domain Name System!=20
>=20
> I'm having a difficulty seeing the point.  A similar=20
> situation happens if=20
> the user has manually configured a few nameservers in=20
> /etc/resolv.conf and=20
> then runs either DHCPv4 / DHCPv6.
>=20
Yes

> Is it IETF's business to specify whether or not (and if so, how) the
> entries should be overwritten, prepended/appended, etc. ?=20

I'm really not sure.=20

>  Is this done
> now with DHCPv4?
>=20
No idea.

> I'm not so sure, but something like "DNS servers configured=20
> through this
> option should take precedence if some existed beforehand" would be
> acceptable to me Note *no* RFC2119 upper-case keywords.
>=20

IMO, the "split vision of DNS" remark is useful for service
architectures but may not be taken into account in some protocol
specifications.

--
to unsubscribe send a message to [email-masked] with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/namedroppers/>