This document obsoletes ripe-429 Link: /publications/docs/ripe-429/ .

Since 2004, DNSMON Link: https://atlas.ripe.net/dnsmon/ has provided a comprehensive and independent overview of the quality of the service provided by infrastructure-level Domain Name System (DNS) servers. The background and history of the service can be found in "RIPE 342" [1], which this document obsoletes.

DNSMON is built on top of the Test Traffic Monitoring (TTM) network [2], and it uses the same probes RIPE Atlas service Link: https://atlas.ripe.net using RIPE Atlas anchors Link: https://atlas.ripe.net/anchor as vantage points for its measurements. Measurements are carried out by sending normal DNS queries to monitored servers at regular intervals. All results are available to the public.

The RIPE NCC's DNSMON measurements benefit the entire Internet community by providing an objective and impartial global overview of TLD-level DNS operations. As part of this service, we monitor some interesting infrastructure domains, including the root, free of charge. root and some ccTLD zones. The list of currently monitored domains is included in the appendix Link: #appendix . 

If requested by the zone operators, we will also additionally configure monitoring for the DNS servers of:

• Any TLD (ccTLD, gTLD etc)
• ccTLDs and IDN ccTLDs from the RIPE NCC service region [1 Link: #1 ]
• ccTLDs and IDN ccTLDs operated by RIPE NCC members [2 Link: #2 ]
• Any Tier-1 ENUM domain (for example, 1.3.e164.arpa)

  Fees are charged for this service on a cost-recovery basis. Subscribers receive additional benefits, which may change from time to time. These are documented within the DNSMON operational service documents [3].

  ---

  [1] ftp://ftp.ripe.net/ripe/docs/ripe-342.pdf Link: ftp://ftp.ripe.net/ripe/docs/ripe-342.pdf
  [2] http://www.ripe.net/ttm Link: http://www.ripe.net/ttm
  [3] http://dnsmon.ripe.net/ Link: http://dnsmon.ripe.net/

  <>#include virtual="/ssi/ripefoot2.inc"> example: 1.3.e164.arpa)

  There is no additional cost to the domain owners for monitoring as part of the DNSMON service.

  ---

  [1] We maintain a list of ISO 3166 Link: http://www.iso.org/iso/country_codes/iso_3166_code_lists/country_names_and_code_elements.htm defined country codes on our FTP Site. See: https://www.ripe.net/participate/member-support/info/list-of-members/list-of-country-codes-and-rirs Link: https://www.ripe.net/participate/member-support/info/list-of-members/list-of-country-codes-and-rirs .
  For a list of defined IDN ccTLDs, see: https://www.iana.org/domains/root/db Link: https://www.iana.org/domains/root/db .
  For an overview of countries in the RIPE service region, see: https://www.ripe.net/participate/member-support/info/list-of-members Link: https://www.ripe.net/participate/member-support/info/list-of-members .
  [2] For a list of member organisations, see: https://www.ripe.net/participate/member-support/info/list-of-members Link: https://www.ripe.net/participate/member-support/info/list-of-members .
  Information on how to become a member can be found here: https://www.ripe.net/participate/member-support/become-a-member Link: https://www.ripe.net/participate/member-support/become-a-member .

  ---

  Appendix

  . root
  a.root-servers.net.
  b.root-servers.net.
  c.root-servers.net.
  d.root-servers.net.
  e.root-servers.net.
  f.root-servers.net.
  g.root-servers.net.
  h.root-servers.net.
  i.root-servers.net.
  j.root-servers.net.
  k.root-servers.net.
  l.root-servers.net.
  m.root-servers.net.
  in-addr.arpa.
  ip6.arpa.
  com.
  net.
  org.
  int.
  e164.arpa.
  3.4.e164.arpa.
  4.4.e164.arpa.
  9.4.e164.arpa.
  ao.
  aq.
  at.
  au.
  be.
  ca.
  cf.
  ch.
  cl.
  срб. (xn--90a3ac)
  cv.
  cz.
  de.
  dk.
  ee.
  es.
  eu.
  fi.
  fr.
  ga.
  gd.
  gg.
  gq.
  gw.
  hk.
  ie.
  il.
  ir.
  is.
  je.
  jp.
  li.
  lu.
  ml.
  mx.
  nl.
  no.
  np.
  nu.
  nz.
  om.
  pl.
  pt.
  rs.
  se.
  si.
  tk.
  ua.
  uk.
  va.
  xn--j6w193g. (香港.)