[dns-operations] Dumb question: why is it that some registries limit the nameservers that can be delegated to?

Michele Neylon - Blacknight michele at blacknight.com
Thu Sep 11 15:06:11 UTC 2014


For gTLDs the nameservers have to be registered via a registrar
Some of the ccTLDs also demand payment and other oddness for adding them
I suspect a lot of this is legacy .. no idea though



Mr Michele Neylon
Blacknight Solutions
Hosting, Colocation & Domains
http://www.blacknight.press for all our news & media
Intl. +353 (0) 59  9183072
Direct Dial: +353 (0)59 9183090
Twitter: http://twitter.com/mneylon
Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty
Road,Graiguecullen,Carlow,Ireland  Company No.: 370845

-----Original Message-----
From: dns-operations [mailto:dns-operations-bounces at dns-oarc.net] On Behalf Of Colm MacCárthaigh
Sent: Thursday, September 11, 2014 3:53 PM
To: dns-operations at lists.dns-oarc.net
Subject: [dns-operations] Dumb question: why is it that some registries limit the nameservers that can be delegated to?

Many registries, if not most, don't let you delegate a zone to arbitrary name-servers. Instead those nameservers need to be "registered" in some way.

Typically anyone can register a name server, and it once it's done, many zones can be delegated to that name server. A small number of CC-TLDs also require contact details for the name servers, but I only know of two that do that.

Registering doesn't require setting up glue, and it doesn't look it's being done to detect cyclic dependencies between zones, which is also the only limitation in the DNS that I can think of that require some kind of workaround.

So why is it that name servers need to be registered? What's the benefit of doing it? and if anyone can register a name server, what's the point?

dns-operations mailing list
dns-operations at lists.dns-oarc.net
dns-jobs mailing list

More information about the dns-operations mailing list