About RIPE NCC | Contact  | Search | Sitemap    
Homepage RIPE NCC  
RIPE Database
     
RIPE Database:
RIPE NCC Navigation Ends
About the RIPE Database
Update RIPE Database
Support Information
DB Document Library
DB Software and Tools
DB Statistics
DB Related projects
*DB Terms and Conditions
Link to routing registry Routing Registry
Link to Resources DB News Archive News Archive
RIPE NCC Navigation Ends
Click here for the RIPE NCC E-Learning Centre
Next Section

RIPE Database

Redirecting reverse DNS updates

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@ripe.net> will automatically be forwarded to <auto-inaddr@ripe.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@ripe.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@ripe.net> for questions, comments or suggestions.

See also: The Reverse DNS (RDNS) project


 

Next Section
     About RIPE NCC | Service Announcements | Site Map | LIR Portal | About RIPE | Contact | Legal | Copyright Statement
RIPE NCC Homepage Go to the RIPE NCC LIRPortal Go to the RIPE Community pages