Skip to main content

Secondary DNS Service for ccTLD Operators

RIPE-659
Publication date:
27 Oct 2015
State:
Obsoleted
Author
  • RIPE NCC
File(s)
PDF (93.6 KB)

Updated by

The RIPE NCC offers a best-effort secondary name service to the other RIRs, along with some country code top-level domain (ccTLD) operators who are in the start-up phase of their operations. There is no associated cost to the zone operators for receiving secondary services by the RIPE NCC. Appendix 1 lists the currently supported zones at the time of writing this document.

In 2014, the RIPE community provided the RIPE NCC with a set of guidelines regarding the requirements and policies for providing ccTLD services. These guidelines are recorded in this RIPE Document and direct the operational decisions of the RIPE NCC when adding or terminating secondary services to operators.

DNS Secondary Service Guiding Principles

  1. RIPE NCC should only provide secondary DNS for ISO3166 ccTLDs and IDN ccTLDs
  2. RIPE NCC should exchange letters with ccTLD operators, to be renewed periodically
  3. The agreement to provide secondary DNS will have a finite lifetime, to be reviewed along with the refresh letter
  4. Eligibility criteria to be used by the RIPE NCC:
    • Size of zone (number of registrations)
    • Number and diversity of other name servers
    • Usage of commercial DNS/name service
  5. For ccTLD operators who already receive secondary DNS service from the RIPE NCC, the eligibility criteria will be applied no earlier than May 2016
  6. Additions and removals will be reported to the DNS Working Group

Appendix 1 – List of ccTLDs for which RIPE NCC provides secondary services (dated 20 October 2015)

ad xn--mgba3a4f16a py
ae is qa
al jm xn--wgbl6a
am jo rs
xn--y9a3aq xn--mgbayh7gpa sa
ar kg sd
ba kz sm
bg xn--80ao21a sn
bi lk sv
bj lv sy
bt ly xn--ogbpf8fl
ci ma sz
cm mc th
cr md tj
cu mg to
cw mm tr
dz mt tt
er mu ua
et mw ug
gd nc uy
gp ne va
gs np vg
gu ph vn
gy ps zw
ir