[114378] in North American Network Operators' Group
Re: Checking bogon status of new address space
daemon@ATHENA.MIT.EDU (Steve Dalberg)
Fri May 8 10:45:06 2009
In-Reply-To: <20090508053336.GC7171@captain.bridge.anchor.net.au>
Date: Fri, 8 May 2009 07:44:58 -0700
From: Steve Dalberg <steve+nanog@sendithere.com>
To: Oliver Hookins <oliver.hookins@anchor.com.au>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Having recently received some de-bogon'ed addressing in or about this March,
I can tell you that the one problem I had was people that had not updated
their Bind Bogon filters (
http://www.cymru.com/Documents/secure-bind-template.html) and so were not
responding to requests from our address space, so we just moved our dns
cache boxes back to our older Level3 address space. Took a while to figure
that one out though.
Steve
2009/5/7 Oliver Hookins <oliver.hookins@anchor.com.au>
> Hi,
>
> my company has just been allocated some new IPv4 address space, and I want
> to do some sort of automated testing to find out any ASs out there that
> haven't removed the /8 it's on from their bogon list (the allocation to our
> local registry only occurred in November last year).
>
> Has anybody attempted to do this? It is worth bothering? Currently I'm
> considering pulling out all the endpoint ASs out of the BGP table, finding
> at least one subnet for each of them and attempting to ping or reach other
> common ports on a single IP for each AS from our currently working
> address space, and then the new address space and comparing results.
>
> --
> Regards,
> Oliver Hookins
> Anchor Systems
>
>
