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
On Sat, 23 Jan 2016 14:02:52 -0500, Daniel Corbe said:
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. 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.....
On Jan 23, 2016, at 1:50 PM, Max Tulyev <maxtul@netassist.ua> wrote:
People do prefix filtering based on *DB may think twice...
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
On Sat, Jan 23, 2016 at 12:42:07AM -0500, Larry J. Blunk wrote:
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
participants (8)
-
Daniel Corbe
-
Jared Mauch
-
Job Snijders
-
Larry J. Blunk
-
Max Tulyev
-
Randy Bush
-
Rubens Kuhl
-
Valdis.Kletnieks@vt.edu