Service for the RADb whois protocol has now been restored. We were experiencing
extensive DDOS activity directed at the whois service host(s).
Regards,
Larry Blunk
Merit
NTT also seemed to suffer, I wonder if it's the same issue there...
Rubens
People do prefix filtering based on *DB may think twice...
How come? What situations would you run into that are so urgent about updating prefix lists that the task can’t be put off for a few hours?
The whois.radb.net IPv4 address changed earlier today, the new IP is
129.250.120.86.
If you mirror RADB through NRTM, I recommend you verify that your mirror
software picked up the DNS change! (IRRd for instance might require a
reseed & restart)
Kind regards,
Job
Those of you who have cron jobs doing an automatic pull can be quite surprised
by scenarios like this.
And of *course* you're doing it from a cron job. Depending on a NOC monkey
to do it every day to pick up newly created prefixes is just *asking* for
trouble tickets to get created when you're not accepting a perfectly valid
but only two week old prefix.....
How come? What situations would you run into that are so urgent
about updating prefix lists that the task can’t be put off
for a few hours?Those of you who have cron jobs doing an automatic pull can be quite
surprised by scenarios like this.
doing it from cron, smart. installing result with no checks, not so
smart.
randy
Ideally you would have your own local mirror or similar.
Since there is the near realtime mirroring that occurs, other servers get the data within 5-30 minutes.
This means you can point at one of the other IRR servers.
- Jared