<<< Chronological >>> Author Index    Subject Index <<< Threads >>>

Re: problems with 194.in-addr.arpa (update)

  • To:
  • From: Geert Jan de Groot < >
  • Date: Mon, 06 Mar 1995 01:22:06 +0100

I have been in touch with the Internic and the problem has
been resolved at the primary root nameserver. It looks like
the secondaries have picked this up too.

If your nameservers have bad NS records for 194.in-addr.arpa,
please restart them.

There is nothing more the RIPE NCC can do at this time. The
bad records need to be timed out, which only time (and a few
restarts!) can do.

Again my apologies for the inconvienence caused by this problem, 
which is was out of our control.

Kind regards,

Geert Jan de Groot 

RIPE NCC staff

----

Old message:

(Message outbox:4283)
 -- using template mhl.format --
Date:    Mon, 06 Mar 1995 00:51:52 MET
To:      ripe-list@localhost, ripe-op@localhost

From:    Geert Jan de Groot <GeertJan.deGroot@localhost
Subject: Severe problems with 194.in-addr.arpa

X-Organization: RIPE Network Coordination Centre
X-Phone: +31 20 592 5065


Probably due to an administrative error, the Internic replaced the
NS records for 194.in-addr.arpa with something incorrect. This means
that reverse-lookups for netnumbers starting with 194.in-addr.arpa
will fail, and anonymous ftp, etc, will likely not work.

The RIPE NCC does not have means to reach the Internic people at
home in the weekend. This means that the problem can only be fixed as
soon as we can get in touch of someone. I have used all means available
to me, but these do not include phone numbers of people at home so
unless someone is monitoring his private mailbox, we will be stuck
with this for Monday at least.

What can you do?
1. Don't call the NCC ;-). The problem is known, but out of
   our control. I have done my utmost to get in touch with the
   Internic already. There is nothing more I can do now.
2. Don't call the Internic either ;-). They have been informed
   though private channels (which doesn't include home phone
   numbers. By calling them you would make their overload worse!
3. Check ns.internic.net for new zone information for this zone.
   As soon as it is updated, please reload your local nameservers
   to delete the old (bad) records in the cache.
4. In emergency cases, consider running a stealth secondary 
   for 194.in-addr.arpa, primary is ns.ripe.net [193.0.0.193].
   To avoid overload, please only consider this in emergency cases!

We fully understand the consequences of this problem, but it is
out of control of the RIPE NCC. We apologise for any inconvienence
caused by (probably) a software error at the Internic.

Kind regards,

Geert Jan de Groot
RIPE NCC

--8<--nip-nip---------------------------------------------------------------
Geert Jan de Groot,                                    'Typos hapen'
RIPE NCC, Kruislaan 409, 1098 SJ Amsterdam, The Netherlands
Internet:GeertJan.deGroot@localhost  Phone:+31 20 5925065  FAX:+31 20 5925090



(Message inbox:2308)
 -- using template mhl.format --
Date:    Sun, 05 Mar 1995 15:18:04 MET
To:      nanog@localhost

From:    Per Gregers Bilse bilse@localhost
Subject: URGENT: ns.internic.net blown

Replied: Mon, 06 Mar 1995 00:14:22 +0100
Replied: staff@localhost
Replied: Per Gregers Bilse bilse@localhost
Replied: nanog@localhost
Organization: EUnet Communications Services BV
Sender:  Per Gregers Bilse bilse@localhost
X-Mailer: Mail User's Shell (7.2.2 4/12/91)

Can somebody get in touch with the right people?  ns.internic.net
has blown 194.in-addr.arpa .  Can't get anybody on the telephone.

--- Forwarded mail from Stef Van Dessel stef@localhost

From: Stef Van Dessel stef@localhost
Subject: NS records for 194.in-addr.arpa
To: ripe-op@localhost
Date: Sun, 5 Mar 1995 14:31:12 +0100 (MET)

hello,

I'm thinking someone screwed up, somewhere.:
NS records for 194.in-addr.arpa are $&"%.

; <<>> DiG 2.0 <<>> @ns.internic.net -x ns 
;; ->>HEADER<<- opcode: QUERY , status: NOERROR, id: 10
;; flags: qr rd ; Ques: 1, Ans: 2, Auth: 2, Addit: 2
;; QUESTIONS: 
;;	194.in-addr.arpa, type = NS, class = IN

;; ANSWERS:
194.in-addr.arpa.	518400	NS	DNS1.KEMA.NL.
194.in-addr.arpa.	518400	NS	NS1.SURFNET.NL.

;; AUTHORITY RECORDS:
194.in-addr.arpa.	518400	NS	DNS1.KEMA.NL.
194.in-addr.arpa.	518400	NS	NS1.SURFNET.NL.

;; ADDITIONAL RECORDS:
DNS1.KEMA.NL.	68866	A	194.53.253.50
NS1.SURFNET.NL.	518400	A	192.87.106.101

;; Sent 1 pkts, answer found in time: 739 msec 
;; FROM: news.INbe.net to SERVER: ns.internic.net  198.41.0.4
;; WHEN: Sun Mar  5 14:24:23 1995
;; MSG SIZE  sent: 34  rcvd: 146

- --
Stef Van Dessel                                        stef@localhost
INnet support                  Posthoflei 3, B-2600 Berchem, Belgium
Office: +32-3-2814983		                  Fax: +32-3-2814985

- --
Stef Van Dessel                                        stef@localhost
INnet support                  Posthoflei 3, B-2600 Berchem, Belgium
Office: +32-3-2814983		                  Fax: +32-3-2814985


--- End of forwarded message from Stef Van Dessel stef@localhost


The correct list of nameservers is:

;; ANSWERS:
194.in-addr.arpa.       518400  NS      ns.uu.net.
194.in-addr.arpa.       518400  NS      layon.inria.fr.
194.in-addr.arpa.       518400  NS      sunic.sunet.se.
194.in-addr.arpa.       518400  NS      munnari.oz.au.
194.in-addr.arpa.       518400  NS      sparky.arl.mil.
194.in-addr.arpa.       518400  NS      ns.ripe.net.
194.in-addr.arpa.       518400  NS      ns.eu.net.


This is causing bad problems for everybody in 194.* .

Hummm ... as a side-issue, is it too much to ask that widely
publicized 24hour emergency telephone numbers exist for root
nameserver operations?

--
bilse, EUnet NOC  +31 20 592 5110; 24hr +31 20 592 5165 (emergencies only)
EUnet Comm. Svcs. +31 20 623 3803; fax  +31 20 622 4657 http://www.EU.net



  • Post To The List:
<<< Chronological >>> Author    Subject <<< Threads >>>