From owner-freebsd-questions Wed Aug 13 22:56:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA26087 for questions-outgoing; Wed, 13 Aug 1997 22:56:52 -0700 (PDT) Received: from suntan.tandem.com (suntan.tandem.com [192.216.221.8]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id WAA26082 for ; Wed, 13 Aug 1997 22:56:50 -0700 (PDT) From: grog@lemis.com Received: from papillon.lemis.com by suntan.tandem.com (8.6.12/suntan5.970212) id WAA04030; Wed, 13 Aug 1997 22:56:35 -0700 Received: (grog@localhost) by papillon.lemis.com (8.8.4/8.6.12) id OAA00381; Thu, 14 Aug 1997 14:56:15 +0900 (JST) Message-Id: <199708140556.OAA00381@papillon.lemis.com> Subject: Re: lame server? In-Reply-To: from Doug White at "Aug 9, 97 02:16:32 pm" To: dwhite@resnet.uoregon.edu Date: Thu, 14 Aug 1997 14:56:13 +0900 (JST) Cc: questions@FreeBSD.org (FreeBSD Questions), hostmaster@aureate.com, hostmaster@mci.net Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8250 Fax: +61-8-8388-8250 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Doug White writes: > On Sat, 9 Aug 1997, Paul wrote: > >> Hello, >> Is this something to be concerned about? I have been getting these messages >> in my messages log? >> >> Aug 7 22:19:05 bob named[86]: Lame server on '109.115.98.206.in-addr.arpa' (in >> '115.98.206.IN-ADDR.ARPA'?): [204.70.57.242].53 'ns2.mci.net': learnt (A=192.5.5 >> .241,NS=204.70.128.1) >> >> If it is something I should be concerned about, what can I do to correct it? >> I just purchased the O'Reilly book on dns and bind, but have not had a chance >> to dig into it yet, and it seems my domain is not visible at times from various >> local carriers... up on one down on the other both up both down... it is making >> me kinda nervous? > > They're harmless. As Named references nameservers, if it discovers a dead > server, it makes a notation and avoids the server for a while. No further > action is needed on your part. This isn't a question of a 'dead server', it's a question of a server which is supposed to be authoritative for a zone, but which passes the buck: it isn't. In this case, the caller was looking for the zone 115.98.206.IN-ADDR.ARPA, the reverse lookup zone for addresses beginning with 206.98.115.x. According to nslookup, the name servers for this zone are: + === grog@freebie (/dev/ttyp0) ~ 6 -> nslookup + Default Server: freebie.lemis.com + Address: 0.0.0.0 + + > set type=soa + > 115.98.206.IN-ADDR.ARPA + Server: freebie.lemis.com + Address: 0.0.0.0 + + 115.98.206.IN-ADDR.ARPA + origin = aureate.com + mail addr = hostmaster.aureate.com + serial = 38 + refresh = 172800 (2 days) + retry = 3600 (1 hour) + expire = 1728000 (20 days) + minimum ttl = 172800 (2 days) + 115.98.206.IN-ADDR.ARPA nameserver = vader.aureate.com + 115.98.206.IN-ADDR.ARPA nameserver = www2.thnet.com + 115.98.206.IN-ADDR.ARPA nameserver = ns2.mci.net + vader.aureate.com internet address = 206.98.115.1 + ns2.mci.net internet address = 204.70.57.242 See that last line? ns2.mci.net is supposed to be authoritative for the zone. So let's ask it: + > server ns2.mci.net + Default Server: ns2.mci.net + Address: 204.70.57.242 + + > 115.98.206.IN-ADDR.ARPA + Server: ns2.mci.net + Address: 204.70.57.242 + + *** ns2.mci.net can't find 115.98.206.IN-ADDR.ARPA: Non-existent host/domain So named tries another server, and this time it's lucky: + > server vader.aureate.com + Default Server: vader.aureate.com + Address: 206.98.115.1 + + > 115.98.206.IN-ADDR.ARPA + Server: vader.aureate.com + Address: 206.98.115.1 + + 115.98.206.IN-ADDR.ARPA + origin = aureate.com + mail addr = hostmaster.aureate.com + serial = 38 + refresh = 172800 (2 days) + retry = 3600 (1 hour) + expire = 1728000 (20 days) + minimum ttl = 172800 (2 days) + 115.98.206.IN-ADDR.ARPA nameserver = vader.aureate.com + 115.98.206.IN-ADDR.ARPA nameserver = www2.thnet.com + 115.98.206.IN-ADDR.ARPA nameserver = ns2.mci.net + vader.aureate.com internet address = 206.98.115.1 + ns2.mci.net internet address = 204.70.57.242 This costs you time, so it's not completely harmless. The Right Thing to do is to send mail to the DNS administrator for the zone. They should be grateful--for some reason, reverse delegation causes a lot of headaches (I know, I'm currently fighting DE-NIC about 197.109.192.in-addr.arpa). To contact the administrator, look at this line from above: + mail addr = hostmaster.aureate.com This is a real kludge. BIND uses the symbol @ for other purposes, so you can't put it in the mail address. Replace the first . in the address with a @, and you get the real address: hostmaster@aureate.com. I'm copying him on this message. Paul, the original sender, wrote: >> it seems my domain is not visible at times from various local >> carriers... up on one down on the other both up both down... it is >> making me kinda nervous? Yes, I couldn't find your address (thsos.com) either, at least not from aureate.com's name server. This seems to be a different problem. To look at this: + === grog@freebie (/dev/ttyp0) ~ 8 -> whois thsos.com + Superior Open Systems, Inc. (THSOS-DOM) + 2901 Ohio Blvd. + Corporate Square, Suite 229 + Terre Haute, IN 47803 + US + + Domain Name: THSOS.COM + + Administrative Contact, Technical Contact, Zone Contact: + Sammann, Paul (PS1809) sos@THSOS.COM + 812-232-8160 (FAX) 812-232-7340 + Billing Contact: + Sammann, Paul (PS1809) sos@THSOS.COM + 812-232-8160 (FAX) 812-232-7340 + + Record last updated on 09-Feb-97. + Record created on 09-Feb-97. + Database last updated on 13-Aug-97 04:24:52 EDT. + + Domain servers in listed order: + + BOB.THSOS.COM 208.137.113.1 + NS2.MCI.NET 204.70.57.242 + === grog@freebie (/dev/ttyp0) ~ 9 -> nslookup + Default Server: freebie.lemis.com + Address: 0.0.0.0 + + > server NS2.MCI.NET + Default Server: NS2.MCI.NET + Address: 204.70.57.242 + + > set type=any + > THSOS.COM + Server: NS2.MCI.NET + Address: 204.70.57.242 + + Non-authoritative answer: WHAT? They're supposed to be authoritative. Have you an agreement with MCI to do secondary for you? + THSOS.COM nameserver = NS2.MCI.NET + THSOS.COM nameserver = BOB.THSOS.COM + + Authoritative answers can be found from: + THSOS.COM nameserver = NS2.MCI.NET + THSOS.COM nameserver = BOB.THSOS.COM + NS2.MCI.NET internet address = 204.70.57.242 + BOB.THSOS.COM internet address = 208.137.113.1 + > server BOB.THSOS.COM + Default Server: BOB.THSOS.COM + Address: 208.137.113.1 + + > THSOS.COM + Server: BOB.THSOS.COM + Address: 208.137.113.1 + + THSOS.COM nameserver = bob.THSOS.COM + THSOS.COM nameserver = ns2.mci.net + THSOS.COM + origin = THSOS.COM + mail addr = hostmaster.THSOS.COM + serial = 15 + refresh = 172800 (2 days) + retry = 3600 (1 hour) + expire = 1728000 (20 days) + minimum ttl = 172800 (2 days) + THSOS.COM preference = 5, mail exchanger = mail.THSOS.COM + THSOS.COM nameserver = bob.THSOS.COM + THSOS.COM nameserver = ns2.mci.net + bob.THSOS.COM internet address = 208.137.113.1 + ns2.mci.net internet address = 204.70.57.242 The second time round, I tried vader.aureate.com, and it found you. I'd guess that this is the result of the lame delegation problems at mci.net. So I'll copy their DNS admin man as well. *sigh*. Greg