109/8 - not a BOGON

Tim Wilde twilde at cymru.com
Tue Oct 20 14:46:04 UTC 2009


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 10/20/2009 8:01 AM, Shane Short wrote:
> I've found pinging a polite email to the whois contact on the ASN
> -sometimes- gives useful results, but not always.
> 
> Be aware that you're not only dealing with router black-holes, but
> seemingly some people have applied bogon filtering to their BIND name
> servers also.
> 
> If you can provide a non bogon IP within the same AS, it can be useful
> for the person at the other end-- shows them they have a problem.

References to documents on bogon best practices are a good idea when
trying to contact WHOIS contacts as well - our bogon reference page and
the IANA IPv4 address space assignments page are probably good places to
start on that:

http://www.team-cymru.org/Services/Bogons/
http://www.iana.org/assignments/ipv4-address-space/

Shane makes a good point about BIND and other configs - we actually
stopped including static bogons in our BIND and BGP/JunOS templates
earlier this year because we found they were being used and not updated,
despite our warnings not to do so.

Best regards,
Tim Wilde

- -- 
Tim Wilde, Senior Software Engineer, Team Cymru, Inc.
twilde at cymru.com | +1-630-230-5433 | http://www.team-cymru.org/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkrdzSwACgkQluRbRini9tgJaACfRnjhFKCv7sKUuNc98r+sn0cG
DDUAn2K5ASv8Pmi+UCbLw0NM6k64r+AF
=Lo8x
-----END PGP SIGNATURE-----




More information about the NANOG mailing list