This is a policy describing under which circumstances we manage DNS zones. It is split in two different services: managing the registration of the zone, and hosting the zone on the central DNS servers.
We can manage registration of DNS zones under any of the following circumstances:
The domain is the associatedDomain for an organization in SUKAT.
There is overhead in managing domain registration (handling payments, keeping our customer contact information up to date). Since vanity domains related to projects come and go there is less work involved if the interested parties just manages the registration and content of the domains themselves.
Zones may be hosted on our central DNS servers under any of the following circumstances:
If we add or remove authoritative DNS servers we also need to update all zone delegations pointing to them. This is easily done as long as we have administrative access to the delegations (like for zones we have registered ourselves). This becomes a lot more tricky for zones where the registration has been performed by an external party, possibly many years ago. It creates a big hindrance in our ability to modify our DNS server layout. In the worst case the zone has been registered with someones personal account at a registry such as .se which won't even tell us the contact information of the registrant in that case.