Service Announcements
  • All of our services are operating normally.
Check Network Health

RIPE Database - Redirecting reverse DNS updates

Archived This content has been archived and is no longer actively maintained.

From 8 December 2003, as part of the effort to streamline reverse DNS operations, domain updates that contain in-addr.arpa or ip6.arpa type entries sent to <auto-dbm _at_ ripe _dot_ net> will automatically be forwarded to <auto-inaddr _at_ ripe _dot_ net> for processing. This will continue until the two processes are combined into one.

Such updates will be processed as follows:

  • If the update contains only domain objects whose "domain:" attributes end with 'in-addr.arpa' or 'ip6.arpa' , it will be redirected to: <auto-inaddr _at_ ripe _dot_ net>
  • If the update contains a mixture of domain objects whose "domain:" attributes end with 'in-addr.arpa' or 'ip6.arpa', as well as other types of database objects, the message will be rejected. The user will receive an e-mail requesting that the objects be separated and re-submitted.
  • All other e-mails will be processed as normal.
  • It will not be possible to update these domain objects using syncupdates.

Please don't hesitate to contact <ripe-dbm _at_ ripe _dot_ net> for questions, comments or suggestions.

See also: The Reverse DNS (RDNS) project