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/[email protected]/
[db-wg] Re: Proposal to change the syntax of "nserver:" attribute
- Previous message (by thread): [dns-wg] Re: [db-wg] Proposal to change the syntax of "nserver:" attribute
- Next message (by thread): [db-wg] Re: Proposal to change the syntax of "nserver:" attribute
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Havard Eidnes
he at uninett.no
Fri Jun 2 13:22:47 CEST 2006
Hi, it's possible that I've overlooked the real background of this issue, so please forgive me for asking: > Motivation: > > We plan to automate management of DNS delegation in the > e164.arpa zone (ENUM). The provisioning system, with the RIPE > Database as a front end, must support IPv6 glue records. While I can agree that out of completeness it is good to have the support for glue records in the software, I still wonder if anyone has specifically asked for being able to name the name servers for these delegation points within the delegated domain? This would be the only real reason for registering the glue information, as otherwise the glue information is not needed, and in fact might be extraneous information more likely to cause confusion and a maintenance problem than actually being helpful. Anyone for a "detect unneeded glue" feature? ;-) After all, there's a strictly limited number of delegations which the RIPE database software needs to handle. Regards, - Håvard
- Previous message (by thread): [dns-wg] Re: [db-wg] Proposal to change the syntax of "nserver:" attribute
- Next message (by thread): [db-wg] Re: Proposal to change the syntax of "nserver:" attribute
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]