To:
Michael Richardson <mcr@sandelman.ottawa.on.ca>
CC:
dnsop@cafax.se
From:
Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Date:
Sun, 27 Jul 2003 19:52:29 +0859 ()
In-Reply-To:
<12275.1059255030@marajade.sandelman.ottawa.on.ca> from MichaelRichardson at "Jul 26, 2003 05:30:30 pm"
Sender:
owner-dnsop@cafax.se
Subject:
Re: proposal for a compromise on DNS discovery
> >> But, a DNS server will be? > > Daniel> Reality check: home networks are, if connected to the Internet, > Daniel> attached via a gatewaying device. The de vice of choice for a > Daniel> large number of networks is a $60 router from on of any number of > Daniel> vendors. These boxes provide DHCP, DNS forwarding and > Daniel> NAT. Perhaps some other environment would provide a better > Daniel> strawman? DHCP is pretty prevalent in home networks. > > Right, exactly. > > I simply do not believe that there are environments where there will be > a local (on wire) DNS server, but not a local DHCP server. The home > environment is entirely the opposite - local DHCP server in SOHO router > that gets the DNS info from the ISP via DHCP and/or PPP and passes it on via > DHCP. Right. Assuming that there is DHCP server even at home, there is no reason to have stateless (nor statefull) autoconfiguration by ND, which is why IPv6 is broken. However, there is still some configuration required at home to let the local DHCP server gets the ISP via DHCP, but definitely not by PPP, because PPP is for dial up over non-IP infrastructure. The simple way for home environment is to to let ISPs offer the DNS servers for their customer sites, which was impossible with addresses with site local scope. Masataka Ohta #---------------------------------------------------------------------- # To unsubscribe, send a message to <dnsop-request@cafax.se>.