Non-Publishable IP's

[Henri J. Schlereth]

> > 	A bit on your terminology.  The 192.168.0.0/16 prefix is
> > delegated for use in private networks. It is not reserved. Please
> > review RFC 1918 for details.
 Per your suggestion I have reviewed RFC 1918 at
 http://www.faqs.org/rfcs/rfc1918.html.
 
 The quote marks are mine but I cite:
 
 
 RFC 1918
 
 3. Private Address Space
 
 The Internet Assigned Numbers Authority (IANA) has "reserved" the
 following three address blocks for private internets:
 
 10.0.0.0 - 10.255.255.255 (10/8 prefix)
 172.16.0.0 - 172.31.255.255 (172.16/12 prefix)
 192.168.0.0 - 192.168.255.255 (192.168/16 prefix)
 
 So the usage of reserved is correct as documented in the RFC.
 
 Anyway, what matters is that he can go ahead and create
 reverse zone files as well as forward zone files.
 
 
> > Note also that all RFC 1918 space does
> > have authoritative DNS servers in the Internet, primarly to assist
> > folks who have improperly configured firewalls. Leaking queries for
> > RFC 1918 space from private networks into the Internet does happen.
> > 
 
 That makes sense.  That was also why I was suggestion that if ethan uses a
 single server that bind 8.2.2P5 has enough features to restrict
 external access and queries.
 
 Henri
 
> > --bill
> > 
> 
> 


-- 
-------------------------------------------------------------
Register Linux User #142063  http://counter.li.org
ICANN at Large Member #202266   http://www.icann.org
Founding Member of Something or the Other.
-------------------------------------------------------------