[db-wg] Follow-up Announcement - Redirecting Reverse DNS Updates

Dear Colleagues,

As an amendment to our previous announcement "Redirecting Reverse DNS 
Updates", 4 December 2003, we would like to make clear that updates for 
domain objects whose "domain:" attributes end with 'in-addr.arpa', 
'ip6.arpa OR 'ip6.int' will be redirected to <auto-inaddr at ripe.net>.

Please do not hesitate to contact <ripe-dbm at ripe.net> for questions, 
comments or suggestions.

Regards,

RD wrote the following on Thursday 04 December 2003 10:39:
> Dear Colleagues,
>
> 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.net> will automatically be forwarded to
> <auto-inaddr at 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 at 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 at ripe.net> for questions,
> comments or suggestions.
>
> Regards,

-- 
Can Bican
Software Engineering Department
RIPE NCC