> ---Reply to mail from Chip Christian about read-rfc1918-for-details.iana.net
>
> > Yeah, we noticed this this morning. I'm surprised there wasn't more
> > uproar. It's definitely new. I noticed it because I had built tcpd w/
> > -DPARANOID, and was allowing 2 machines from outside my control telnet
> > access over a leased line into one of my boxes. Well, when their
> > addresses started resolving to a not resolvable name, I started dropping
> > them immediately. The solution of course was to start serving up an empty
> > reverse zone.
> >
>
> it isnt affecting us, as we have an internal dns server which has maps for
> our IPs (RFC 1918) that we use.. Perhaps doing mapping internally even if
> its an empty zone will help..
Which is exactly what I did (empty zone; see above). For my own RFC 1918
addresses I'd already been serving the right zones.
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
