Date: Mon, 14 Mar 1994 23:28:17 +0000 () From: Dave Richards <dar@mail.dit.tec.co.us> To: questions@FreeBSD.org Subject: DNS question/lame server Message-ID: <Pine.BSF.3.91.940314231256.1913A-100000@mail.dit.tec.co.us>
next in thread | raw e-mail | index | archive | help
Hi everyone, I have what is probably a nasty DNS question.... none of
the documentation I've read, including the O'Reilly 'DNS & BIND' book,
seems to cover my case for setting up named. I've already checked
the mail database archives for this question, and have investigated each
possible cause. I can't see that I've done anything wrong, other than
using an existing windows nt box as our second dns server (it seems to
download the zone info from the primary okay). The problem has been with
us for about a week.
1st DNS server: freebsd dit.tec.co.us 209.38.1.2
2nd DNS server: winnt dit.tec.co.us 209.38.1.1
direct T1 connection, no external (ISP) nameservers
all our DNS entries resolve for the outside world great, just long
waits to connect
Here's the problem:
100+ people with 75 sec. timeouts every day waiting to get their mail via
Pop3
"Lame server" errors from bind in the messages logfile on the primary
here are some screens from my console:
========================================
bash# vi /var/log/messages
Mar 13 14:11:40 mail named[66]: starting. named LOCAL-960717.011537 Wed
Jul 17 01:15:37 1996 jkh@whisker.cdrom.com:/usr/src/usr.sbin/named
Mar 13 14:11:40 mail named[67]: Ready to answer queries.
Mar 14 07:55:51 mail named[67]: Lame server on '3.1.38.209.in-addr.arpa'
(in '1.38.209.IN-ADDR.ARPA'?): [166.93.8.2].53 'NS2.ROCKYMTN.NET': lear
nt (A=128.63.2.53,NS=128.9.0.107)
Mar 14 09:59:40 mail named[67]: Lame server on '3.1.38.209.in-addr.arpa'
(in '1.38.209.IN-ADDR.ARPA'?): [166.93.1.3].53 'NS1.ROCKYMTN.NET': lear
nt (A=128.9.0.107,NS=128.9.0.107)
Mar 14 10:43:39 mail named[67]: Lame server on '3.1.38.209.in-addr.arpa'
(in '1.38.209.IN-ADDR.ARPA'?): [166.93.1.3].53 'NS1.ROCKYMTN.NET': lear
nt (A=128.9.0.107,NS=128.9.0.107)
Mar 14 10:53:40 mail named[67]: Lame server on '3.1.38.209.in-addr.arpa'
(in '1.38.209.IN-ADDR.ARPA'?): [166.93.8.2].53 'NS2.ROCKYMTN.NET': lear
nt (A=128.63.2.53,NS=128.9.0.107)
Mar 14 16:55:52 mail named[67]: Lame server on '3.1.38.209.in-addr.arpa'
(in '1.38.209.IN-ADDR.ARPA'?): [166.93.1.3].53 'NS1.ROCKYMTN.NET': lear
nt (A=128.9.0.107,NS=128.9.0.107)
Mar 14 22:13:33 mail named[67]: Lame server on
'221.1.38.209.in-addr.arpa' (in '1.38.209.IN-ADDR.ARPA'?):
[166.93.1.3].53 'NS1.ROCKYMTN.NET': le
arnt (A=128.9.0.107,NS=128.9.0.107)
Mar 14 22:15:32 mail login: login from 209.38.1.221 as dar
Mar 14 22:23:34 mail named[67]: Lame server on
'221.1.38.209.in-addr.arpa' (in '1.38.209.IN-ADDR.ARPA'?):
[166.93.1.3].53 'NS1.ROCKYMTN.NET': le
arnt (A=128.9.0.107,NS=128.9.0.107)
Mar 14 22:33:36 mail named[67]: Lame server on
'221.1.38.209.in-addr.arpa' (in '1.38.209.IN-ADDR.ARPA'?):
[166.93.8.2].53 'NS2.ROCKYMTN.NET': le
arnt (A=128.63.2.53,NS=128.9.0.107)
Mar 14 22:47:28 mail su: dar to root on /dev/ttyp0
======================================
bash# vi /etc/namedb/named.boot
; $Id: named.boot,v 1.3 1995/03/23 08:43:02 rgrimes Exp $
; From: @(#)named.boot 5.1 (Berkeley) 6/30/90
; boot file for secondary name server
; Note that there should be one primary entry for each SOA record.
; example sortlist config:
; sortlist 128.3.0.0
directory /etc/namedb
; type domain source host/file backup
file
primary 0.0.127.IN-ADDR.ARPA localhost.rev
primary dit.tec.co.us dit.tec.co.us
cache . named.root
; example secondary server config:
; secondary Berkeley.EDU 128.32.130.11 128.32.133.1
ucbhosts.bak
; secondary 32.128.IN-ADDR.ARPA 128.32.130.11 128.32.133.1
ucbhosts.rev.bak
; example primary server config:
; primary Berkeley.EDU ucbhosts
; primary 32.128.IN-ADDR.ARPA ucbhosts.rev
========================================
bash# vi /etc/namedb/dit.tec.co.us
; From: @(#)localhost.rev 5.1 (Berkeley) 6/30/90
; $Id: PROTO.localhost.rev,v 1.1 1995/03/21 16:33:44 wollman Exp $
;
; This file is automatically edited by the `make-localhost' script in
; the /etc/namedb directory.
;
@ IN SOA dit.tec.co.us. root.dit.tec.co.us. (
8 ; Serial
3600 ; Refresh
300 ; Retry
3600000 ; Expire
3600 ) ; Minimum
IN NS ns1.dit.tec.co.us.
IN NS ns2.dit.tec.co.us.
dit.tec.co.us. IN A 209.38.1.2
dit.tec.co.us. IN MX 10 mail.dit.tec.co.us.
ditinet IN A 209.38.1.254
mail IN A 209.38.1.2
www IN A 209.38.1.1
ns1 IN CNAME mail
ns2 IN CNAME www
ftp IN CNAME www
ii_dit_mis IN A 209.38.1.3
ii_dit_edu IN A 209.38.1.4
ditwan IN A 204.56.53.254
254.1.38.209.in-addr.arpa. IN PTR ditinet.dit.tec.co.us.
221.1.38.209.in-addr.arpa. IN PTR ppp-1.dit.tec.co.us.
2.1.38.209.in-addr.arpa. IN PTR mail.dit.tec.co.us.
1.1.38.209.in-addr.arpa. IN PTR www.dit.tec.co.us.
1.1.38.209.in-addr.arpa. IN PTR ftp.dit.tec.co.us.
3.1.38.209.in-addr.arpa. IN PTR ii1.dit.tec.co.us.
4.1.38.209.in-addr.arpa. IN PTR ii2.dit.tec.co.us.
254.53.56.204.in-addr.arpa. IN PTR ditwan.dit.tec.co.us.
========================================
any help to this beginning DNS admin-wanna-be would be greatly
appreciated!
Thanks,
Dave
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.91.940314231256.1913A-100000>