[dns-operations] How do you manage multiple domains under a ccTLD?

[Karl Dyson]

On Thu, 7 Nov 2024 at 16:16, me aharen <aharen at outlook.com> wrote:

> Hello,
>
> I am interested to learn how ccTLD operators handle zone file management.
> For example, I am the owner of .IO ccTLD and I would like to manage this
> domain. Do I only create a single zone file .io and all the entries to that
> file? Or do I need to to create a zone file for each domain that gets added
> to the list. Ex, a customer bought the domain hello.io, ministry.gov.io
> etc.
>
> Managing multiple zone files for each customer seems a tough task to
> manage, in the case of BIND, config needs to updated to include zone
> information for the new domain. Hence, I am interested to know the common
> deployment strategy to manage multiple domains under a ccTLD.
>
> When it comes to software, BIND has zone files, where each customer zone
> needs to be created in the cofig. Or is just a single zone file?
>
> Apprreciate any feedback, suggestions.
>
> Regards,
> Aharen
>


Hello,

Typically, TLDs are delegation centric zones, and whether you operate
separate zone files for each zone *you* are running is kind of up to you
and your choice of administrative approach.

However, noting that where customers register a domain in a TLD, you are
likely not running the authoritative DNS for the child zone for the
registered domain, and are likely only adding the relevant delegation to
the parent (TLD) zone, together with any supporting records (such as glue,
and/or DS, for example).

It would be on the customer to then run the authoritative DNS for the
delegated child zone (which may involve one or more of running it
themselves, utilising the services of their registrar or ISP, or some other
authoritative DNS service).

[with my Nominet hat on]

Nominet take registrations in a number of second level domains (SLDs) under
the uk TLD, such as co.uk, me.uk, net.uk, etc, as well as in the uk TLD
itself, and we operate separate zone files for each of those.

Thanks,
Karl
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.dns-oarc.net/pipermail/dns-operations/attachments/20241107/a90ca7cf/attachment.html>