-----BEGIN PGP SIGNED MESSAGE-----

>>>>> "Daniel" == Daniel Senie <[EMAIL PROTECTED]> writes:
    Daniel> At 04:36 PM 7/25/2003, Michael Richardson wrote:

    >> >>>>> "Syam" == Syam Madanapalli <[EMAIL PROTECTED]> writes:
    Syam> I think the following approach probably will yield a
    Syam> better method for DNS Discovery.
    >> 
    Syam> As DHCP may not be available in all netwokrs
    Syam> especially in small networks like Home Networks,
    >> 
    >> 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. 

]      Out and about in Ottawa.    hmmm... beer.                |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] [EMAIL PROTECTED] http://www.sandelman.ottawa.on.ca/ |device driver[
] panic("Just another NetBSD/notebook using, kernel hacking, security guy");  [


  
  

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Finger me for keys - custom hacks make this fully PGP2 compat

iQCVAwUBPyLy9YqHRg3pndX9AQHy0gP7B3fYZ6pFaPkhbJT2VuHLz25iVwbWztXF
0d3ypeHkg5rmApqmKWpD2Cr1gDOIun1qx3+g4dLWM5bipPsUeDqrsZ/JzjAsT5Qj
LIwyJfBjlUMlf8hHX46HylrL0dRmLjtY6wDp3Yo+xgtdxfCUdDRju3OtCru/oG8p
L4/KSXLWrik=
=+p7V
-----END PGP SIGNATURE-----
#----------------------------------------------------------------------
# To unsubscribe, send a message to <[EMAIL PROTECTED]>.

Reply via email to