from localhost (localhost [127.0.0.1])
	by phobos.labs.netnoteinc.com (Postfix) with ESMTP id 9E8FE43FAD
	for <jm@localhost>; Fri, 19 Jul 2002 10:39:20 -0400 (EDT)
from dogma.slashnull.org [212.17.35.15]
	by localhost with IMAP (fetchmail-5.9.0)
	for jm@localhost (single-drop); Fri, 19 Jul 2002 15:39:20 +0100 (IST)
from dogma.slashnull.org (localhost [127.0.0.1]) by
    dogma.slashnull.org (8.11.6/8.11.6) with ESMTP id g6JET1J04575 for
    <jm@jmason.org>; Fri, 19 Jul 2002 15:29:01 +0100
from dogma.slashnull.org (localhost [127.0.0.1]) by
    dogma.slashnull.org (8.11.6/8.11.6) with ESMTP id g6JES1J04499 for
    <iiu-admin@iiu.taint.org>; Fri, 19 Jul 2002 15:28:02 +0100
Irish Internet Users post from yyyycc@hackwatch.com requires approval
From iiu-admin@taint.org  Fri Jul 19 15:39:22 2002

As list administrator, your authorization is requested for the
Subject: Re: [IIU] IE nameserver problems

from localhost (localhost [127.0.0.1])
	by phobos.labs.netnoteinc.com (Postfix) with ESMTP id 5B1DF440CC
	for <jm@localhost>; Fri, 19 Jul 2002 11:07:34 -0400 (EDT)
from dogma.slashnull.org [212.17.35.15]
	by localhost with IMAP (fetchmail-5.9.0)
	for jm@localhost (single-drop); Fri, 19 Jul 2002 16:07:34 +0100 (IST)
from dogma.slashnull.org (localhost [127.0.0.1]) by
    dogma.slashnull.org (8.11.6/8.11.6) with ESMTP id g6JF4AJ06915;
    Fri, 19 Jul 2002 16:04:10 +0100
from waterford.wizardr.ie (root@stargate.wizardr.ie
    [194.125.0.34]) by dogma.slashnull.org (8.11.6/8.11.6) with ESMTP id
    g6JERLJ04422 for <iiu@taint.org>; Fri, 19 Jul 2002 15:27:21 +0100
from hackwatch.com (void.nsa.ie [193.120.253.3]) by
    waterford.wizardr.ie (8.9.3/8.9.3) with ESMTP id PAA05822; Fri,
    19 Jul 2002 15:27:17 +0100
From iiu-admin@taint.org  Fri Jul 19 16:07:38 2002

> Four of the IE nameservers are publishing out of date DNS information.
> The four listed below are publishing the IE zone from last Friday.
Last week, when indexing stuff for WhoisIreland.com, I noticed that
ns0.domainregistry.ie and banba.domainregistry.ie were out of synch by a
few days. The other nameservers seemed to give a current SOA at that
time. However the affected secondaries may have been using
ns0.domainregistry.ie for axfr and propagated the error.
This whole thing does seriously bring into question IEDR's decision to
outsource the technical admininstration of .ie to a company that
apparently does not even admin its own DNS.  It is a nice story though -
almost as good as the time that .ie disappeared for 8 hours in July