Bogus in-addr.arpa NS RRs

[Erik-Jan Bos <]

RIPE List, Hostmaster,

maybe you already heard about this, but please be aware that there is
bogus in-addr.arpa info out there. This is really service affecting, we
already had some major complaints at SURFnet.

Can Hostmaster please contact the site SCITEX.COM  (SCITEX Corp. Ltd.,
8 Oak Park Drive, Bedford, MA 01730). After this is done w'all need to
flush some caches I am afraid.

Thanks to Hans van Staveren for forwarding this to us.

------- Forwarded Message

Date:    Tue, 19 Jul 1994 15:30:36 +0700
From:    Hans van Staveren sater@localhost
To:      netmaster@localhost
Subject: [Joseph Malcolm: ns.nasa.gov handing out bogus information for IN-ADDR
	  .ARPA]

Hiero

- ----- Forwarded message # 1:

Received: from top.cs.vu.nl by zephyr.cs.vu.nl id aa00497;
          19 Jul 94 1:56 MET DST
Received: from zephyr.cs.vu.nl by top.cs.vu.nl id aa00721;
          19 Jul 94 1:55 MET DST
Received: from hearnvax.nic.surfnet.nl by zephyr.cs.vu.nl id aa00491;
          19 Jul 94 1:55 MET DST
Received: from ruulet (ruulet.let.ruu.nl) by HEARNVAX.nic.SURFnet.nl (PMDF
 V4.2-12 #3330) id 01HEVGFQPSHS00F9Z4@localhost; Tue,
 19 Jul 1994 01:55:56 +0200 (MET-DST)
Received: from relay1.UU.NET by ruulet.let.ruu.nl (PMDF #2703 ) id
 01HEVGFEP3PS001J58@localhost; Tue, 19 Jul 1994 01:55:40 GMT
Received: by relay1.UU.NET (relay) id QQwzdk19431; Mon,
 18 Jul 1994 19:06:46 -0400
Received: from odin.UU.NET by relay1.UU.NET with SMTP (relay) id QQwzdk19427;
 Mon, 18 Jul 1994 19:06:44 -0400
Received: by odin.UU.NET (maildrop) id QQwzdk16643; Mon,
 18 Jul 1994 19:06:37 -0400
Date: Mon, 18 Jul 1994 19:06:37 -0400
From: Joseph Malcolm jmalcolm@localhost
Subject: ns.nasa.gov handing out bogus information for IN-ADDR.ARPA
To: bind@localhost
Errors-to: postmaster@localhost
Reply-to: bind@localhost
Message-id: <QQwzdk16643.199407182306@localhost
X-Envelope-to: binders@localhost
Content-transfer-encoding: 7BIT

If any name server administrators out there have been wondering where
those bogus records for in-addr.arpa have been coming from, I think I
have an answer.

(This also explains why the nifty-neato login in newer binds to throw
bogus info away isn't working - of course a root server can be trusted
for in-addr.arpa...)

I've reached someone at the Internic, who will get ahold of the
appropriate parties at NASA.

jmalcolm@localhost [/apps/dns/etc] 1-227> dig @128.102.16.10 in-addr.arpa ns

; <<>> DiG 2.0 <<>> @128.102.16.10 in-addr.arpa ns 
; (1 server found)
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10
;; flags: qr rd ra; Ques: 1, Ans: 1, Auth: 1, Addit: 1
;; QUESTIONS:
;;      in-addr.arpa, type = NS, class = IN

;; ANSWERS:
in-addr.arpa.   555875  NS      ird.scitex.com.

;; AUTHORITY RECORDS:
IN-ADDR.ARPA.   555875  NS      ird.scitex.com.

;; ADDITIONAL RECORDS:
ird.scitex.com. 172800  A       149.115.100.3

;; Total query time: 5110 msec
;; FROM: odin.UU.NET to SERVER: 128.102.16.10
;; WHEN: Mon Jul 18 18:40:33 1994
;; MSG SIZE  sent: 30  rcvd: 100

- ----- End of forwarded messages

------- End of Forwarded Message

__
 
Erik-Jan.