To:
"Eric A. Hall" <ehall@ehsco.com>
Cc:
dnsop@cafax.se
From:
Ralph Droms <rdroms@cisco.com>
Date:
Sat, 08 Nov 2003 07:06:03 -0500
In-Reply-To:
<3FABB683.8010805@ehsco.com>
Sender:
owner-dnsop@cafax.se
Subject:
Re: Sense of the WG on DNS discovery
Eric - good point. I was thinking of the usual deployment of DHCP servers and meant "misconfiguration" to apply to DHCP servers intended to give consistent replies. Receiving different answers from different servers doesn't violate any part of the DHCP spec itself. Although the usual practice (in DHCPv4) is to accept the configuration parameters from one server and ignore the others, I'll review the words in RFC 3315 and the DNS config option doc to confirm that combining information from multiple responses is within the spec. We have an opportunity to clarify the DNS config option spec if necessary, as it is currently still in the RFC Editor's publication queue. - Ralph At 09:13 AM 11/7/2003 -0600, Eric A. Hall wrote: >Ralph Droms wrote: > > > We discussed the issue of receiving multiple responses to the DNS > > configuration information option in an ipv6 WG meeting. Turns out, in > > theory, the order of appearance of DNS recursive name servers in the > > list doesn't matter because every server should return the same > > response to a given query. More generally, receiving multiple > > different responses from DHCP servers (either IPv4 or IPv6) represents > > a misconfiguration and is an operational problem - which could occur > > with other DNS configuration mechanisms as well. > >Doesn't that dis-prove the claim that "A minimal DHCPv6-lite server >co-located with a recursive name server [c]ould just respond with its own >address"? (see <20030803000619.94C1E18E3@thrintun.hactrn.net> and its >thread-context neighbors) > >So going this way means additional DNS-specific maintenance would be >mandatory after all. > >-- >Eric A. Hall http://www.ehsco.com/ >Internet Core Protocols http://www.oreilly.com/catalog/coreprot/ > >#---------------------------------------------------------------------- ># To unsubscribe, send a message to <dnsop-request@cafax.se>. #---------------------------------------------------------------------- # To unsubscribe, send a message to <dnsop-request@cafax.se>.