Subject: DNS Weather Report 2004-08-24

From: Daniel Roesen <[email-masked]>
Date: Tue, 24 Aug 2004 00:42:27 +0200

DNS WEATHER REPORT for selected infrastructure zones
====================================================
Issue 2004-08-24

Zones analyzed and their SOA contacts:

- .             [email-masked]
- arpa.         [email-masked]
- int.          [email-masked]
- in-addr.arpa  [email-masked]
- ip6.arpa.     [email-masked]
- ip6.int.      [email-masked]

Executive summary: not a single zone without any problems, but ip6.int
situation improved significantly.

The state of the root zone
===========================
- m.root-servers.net is lagging behind the others... general
  SOA serial is 2004082201, m.root has 2004082101

The state of the ARPA zone
==========================
- same SOA serial problem as in the root zone, m.root out-of-sync.
  Interestingly, all the same SOA serial numbers as the root zone
  (coincidence?)

The state of the INT zone
=========================
- in-zone NS RRset doesn't match the delegation NS RRset.

  in-zone RRset:        delegation RRset:
  ns0.ja.net.           ns0.ja.net.
  ns1.cs.ucl.ac.uk.     ns1.cs.ucl.ac.uk.
  ns.icann.org.         ns.icann.org.
  ns.isi.edu.           ns.isi.edu.
  ns.uu.net.            ns.uu.net.
  ns.ripe.net.
  z.ip6.int.

- ns.isi.edu started to be auth again (was lame a few days ago), but
  is not in sync. current SOA serial of the INT TLD: 2004080300,
  ns.isi.edu has 2002080104

The state of the IN-ADDR.ARPA zone
==================================
- same problem with m.root as with the root zone. m.root seems to lag
  exactly one day behind, judging from the SOA serial number.

The state of the IP6.ARPA zone
==============================
- in-zone NS RRset doesn't match the delegation NS RRset.

  in-zone RRset:        delegation RRset:
  ns.apnic.net.         ns.apnic.net.
  ns.icann.org.         ns.icann.org.
  ns-sec.ripe.net.      ns.ripe.net.
  tinnie.arin.net.      tinnie.arin.net.

  Problem known, RIPE sent a reminder to ip6.arpa operators a week ago,
  obviously without any outcome.

The state of the IP6.INT zone
=============================
- ns.isi.edu (one of the INT TLD servers) feels authoritative for the
  IP6.INT zone, but is neither listed in the delegation NS RRset, nor
  in the in-zone NS RRset of IP6.INT.
  Luckily, ns.isi.edu carries ip6.int with the same SOA serial as the
  official servers, so introduces no operational problems so far.

Regards,
Daniel