Why is RFC1918 space in public DNS evil?

Valdis.Kletnieks at vt.edu Valdis.Kletnieks at vt.edu
Mon Sep 18 18:21:10 UTC 2006

On Mon, 18 Sep 2006 17:57:43 +0200, Peter Dambier said:

> It can make sense:
> I am sending my mails mostly from lumbamba.peter-dambier.de (
> my router is krzach.peter-dambier.de (
> my mailer is echnaton.peter-dambier.de (
> My traceroute looks ok although some of the hosts are RFC1918
> If somebody looks into my email headers they find information that makes
> sense although they could not ping the hosts.
> As long as you do not allow AXFR, nobody can see the information about
> RFC1918 hosts. So there is no risk.

Unless of course you're leaking it in Received: headers..

Or DNS requests across the public Internet (remember, we *started* with the
question of having this stuff on a public-facing DNS server..)..

Or all the other myriad ways this stuff tends to leak out.  AXFR is the *least*
of your problems.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 226 bytes
Desc: not available
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20060918/b102d979/attachment.sig>

More information about the NANOG mailing list