Since my name was mentioned in this thread ...
Please be assured that we are working on any residual reverse DNS problems as I type this message.
We do not post announcements regarding service disruptions to the members-discuss mailing list. We announce disruptions on our service announcement page as soon as any issue is discovered: http://www.ripe.net/lir-services/service-announcements
Additionally this particular issue was announced on specific rDNS announcement page:
http://www.ripe.net/lir-services/service-announcements/reverse-dns-services-issues
Because we expected significant impact of this particular incident we also mention it directly on the RIPE NCC's news and annoucments section on the homepage.
We are working on the rDNS issue and would like to ask anyone who is experiencing problems relating to this to send reports to
dns-help at ripe.net with details about what DNS responses you are getting and what the difference is to what you are expecting.
Updates will be posted to the service pages mentioned above as soon as they are available and we will send updates to the dns-wg at ripe.net and ncc-announce mailing lists as necessary. We will also add any updates to our twitter feed @RIPE_NCC.
Regarding the RIPE NCC's 24/7 procedures: we have 24/7 call out coverage in place for our infrastructure in general and for our DNS services in particular. All outages are monitored around the clock and our engineers respond swiftly to any incidents. We always announce that we are working on particular incidents as detailed above, as we did last night. We do not have a 24/7 call centre that can be contacted outside of regular office hours.
After this particular incident is over, we will publish a post-mortem analysis.
Daniel Karrenberg
Chief Scientist
RIPE NCC

The RIPE NCC uses cookies. Some of these cookies may have been set already. More information about our cookies can be found in our privacypolicy. You can accept our cookies either by clicking here or by continuing to use the site.