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]/

[dns-wg] RIPE's MNAME recommendation

Previous message (by thread): [dns-wg] RIPE's MNAME recommendation
Next message (by thread): [dns-wg] RIPE's MNAME recommendation

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Bruce Campbell list-ripe-dns-wg at vicious.dropbear.id.au
Fri Sep 30 19:24:33 CEST 2005

On Fri, 30 Sep 2005, Daniel Karrenberg wrote:

> So the recommendation should be to put into the MNAME field the domain
> name of an authoritative name server that allows AXFRs and is the
> intended target for dynamic updates.

Going back to the original poster's question, Registrars (whether RIPE 
members or not), imho, should only be checking that the MNAME field is 
syntactically correct, not whether it represents a reachable host.

Of course, there is nothing stopping the Registrant from temporarily 
changing the MNAME field to point to something 'valid' whilst interacting 
with the Registrar, and to put it back to their Registrar-invalid version 
afterwards.

Apart from that, RIPE-203 is still good advice.

-- 
   Bruce Campbell

Previous message (by thread): [dns-wg] RIPE's MNAME recommendation
Next message (by thread): [dns-wg] RIPE's MNAME recommendation

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ dns-wg Archives ]