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]/
Provider-based DNS naming?
- Previous message (by thread): Provider-based DNS naming?
- Next message (by thread): Provider-based DNS naming?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Marten Terpstra
Marten.Terpstra at ripe.net
Mon Oct 3 10:43:11 CET 1994
Piet Beertema <Piet.Beertema at cwi.nl> writes * I.e. is there something that can be done to disuade a provider - say * provider.top from registering his customer companies as * company1.provider.top * company2.provider.top etc.. * The rules for registering a domain under .NL explicitly * forbid this (short-form translation: "subdomains under a * domain registered by an organisation may only pertain to * said organisation; registering third parties under the * domain is not allowed"). Hmm, does this only apply to real domains or also to hostnames which is very usual practice for dialin/SLIP type of providers? It basically comes down to the same thing. company.provider.top A a.b.c.d or company.provider.top NS some.where.else in my view is kind of the same, at least in binding the companies domain name and email address to the provider. Even in NL the first one is common practice. -Marten
- Previous message (by thread): Provider-based DNS naming?
- Next message (by thread): Provider-based DNS naming?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]