This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/dns-wg@ripe.net/
[dns-wg] Announcement: Redirecting reverse DNS updates
- Previous message (by thread): [dns-wg] Domain cleanup proposal
- Next message (by thread): [dns-wg] Fingerprinting DNS implementations.
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
RIPE Database Manager
ripe-dbm at ripe.net
Mon Dec 8 13:08:47 CET 2003
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', 'ip6.arpa' or 'ip6.int', 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', 'ip6.arpa', 'ip6.int' 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
- Previous message (by thread): [dns-wg] Domain cleanup proposal
- Next message (by thread): [dns-wg] Fingerprinting DNS implementations.
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]