> -----Original Message-----
> From: Barry Margolin [mailto:barmar@alum.mit.edu]
> Sent: Wednesday, October 27, 2004 06:45 AM
> To: comp-protocols-dns-bind@isc.org
> Subject: Re: primary lame server
>
> In article , rioguia@speakeasy.net wrote:
>
> > I have a lame primary name server testy.substantis.com.
> > My files appear to be formatted correctly (my /etc/host and resolve.conf =
> > are shown below) because named-checkconf returns a zero status. I also a=
> > ttempted to use DNSWalk but can't find any documentation on how to use it=
> > (sample command lines would be appreciated.

>
> It looks like testy isn't successfully loading the zone file for
> substantis.com.
>
> Since you haven't posted any of your configuration files, I don't know
> how you expect us to figure out what you did wrong.
>
> >
> > I do see in the the following errors in the logs
> > rndc: connect failed: connection refused
> >
> > Oct 27 00:55:48 testy kernel: process `nslookup' is using obsolete setsoc=
> > kopt SO_BSDCOMPAT
> > Oct 27 04:55:48 testy named[3907]: lame server resolving 'substantis.com'=
> > (in 'substantis.com'?): 69.17.65.22#53
> > Oct 27 01:00:20 testy kernel: process `dig' is using obsolete setsockopt =
> > SO_BSDCOMPAT

>
> What you need to look at are the log messages that occur when you start
> named. They'll tell you what zone files it's loading, and if it got any
> errors while doing this.
>
> --
> Barry Margolin, barmar@alum.mit.edu
> Arlington, MA
> *** PLEASE post questions in newsgroups, not directly to me ***
>
>
>

thanks for your quick response. please excuse the double posting (i misread a bounced email).

my external configuration files and my internal localhost files are as follows:

// /home/chroot-dns-ext/etc/named.conf for TrinityOS - 11/25/02
// Config file for a full authoritative --EXTERNAL-- DNS server

options {
//Remember, this is already CHROOTed. /var/named IS correct
directory "/var/named";

//Do NOT have the server listening on localhost or the internal interface
listen-on port 53 {
69.17.65.22;
};

// Clean the cache every 6 hours (default is 1).
cleaning-interval 360;

// Do NOT respond to DNS queries for any domains other than local zones
//
// All remote DNS lookups for this host and any internal machines will
// be served from the INTERNAL DNS server
// recursion no;

// Uncommenting this might help if you have to go through a
// firewall and things are not working out:
query-source address * port 53;
};

zone "." {
type hint;
file "root.hints.db";
};
// number 1 server http, dns, imap
zone "22.65.17.69.in-addr.arpa" in {
type master;
notify no;
file "named.69.17.65.22";
allow-transfer { 69.17.65.161; };

};
// number 2 server http, dns, imap
zone "161.65.17.69.in-addr.arpa" in {
type master;
notify no;
file "named.69.17.65.161";
allow-transfer { 69.17.65.161; };

};
// our first primary zone
zone "substantis.com" {
type master;
notify no;
file "named.substantis";
allow-transfer { 69.17.65.161; };
allow-query { 127/8; 192.168.0/24; };
};
// our second primary zone
zone "lubuto.org" {
type master;
notify no;
file "named.lubuto";
allow-transfer { 69.17.65.161; };

[EDITED FOR BREVITY'S SAKE]

//our eighth primary zone
zone "nelsonbeaudoin.com" {
type master;
file "named.nelsonbeaudoin";
notify no;
allow-transfer { 69.17.65.161; };

};



; /home/chroot/-dns-ext/var/named/named.substantis.com
$TTL 3H
substantis.com. 1D IN SOA testy.substantis.com. postmaster.substantis.com. (
2004102702
2H
1H
1W
1D )
substantis.com. 1W IN NS testy.substantis.com.
substantis.com. 1W IN NS ns2.speakeasy.net.
substantis.com. 1W IN NS ns1.speakeasy.net.
substantis.com. 3H IN MX 10 mail.substantis.com.
substantis.com. 3H IN MX 20 ns1.substantis.com.

substantis.com. IN TXT "v=spf1 a mx a:ns1.substantis.com -all"
localhost.substantis.com. 1W IN A 127.0.0.1
substantis.com. 3H IN A 69.17.65.22
testy.substantis.com. 1W IN A 69.17.65.22
ns1.substantis.com. 1W IN A 69.17.65.161
www.substantis.com. 3H IN A 69.17.65.22
mail.substantis.com. 3H IN A 69.17.65.22

; /home/chroot/-dns-ext/var/named/named.69.17.65.22
; ################################################## ##########
; Start of Authority (Inverse Address Arpa) 69.17.65.22/32
; Filename: named.69.17.65.22 server number 1
; ################################################## ##########
@ 604800 IN SOA testy.substantis.com. postmaster.substantis.com. (
2004092902 ; serial
10800 ; refresh (3 hour)
3600 ; retry (1 hour)
604800 ; expire (7 days)
86400 ) ; minimum (1 day)
;
; ################################################## ##########
; Specify Name Servers for all Reverse Lookups (IN-ADDR.ARPA)
; ################################################## ##########
@ 604800 IN NS testy.substantis.com.
@ 604800 IN NS ns1.substantis.com.
;
; ################################################## ##########
; Iverse Address Arpa Records (PTR's)
; ################################################## ##########
22.65.17.69.in-addr.arpa. 86400 IN PTR testy.substantis.com.
; 22.65.17.69.in-addr.arpa. 86400 IN PTR ns2.substantis.com.
; 22.65.17.69.in-addr.arpa. 86400 IN PTR mail02.substantis.com.

I AM ALSO PROVIDING MY LOCAL REVERSE LOOKUP (ALONG WITH THE /ETC/RESOLV.CONF AND /ETC/HOSTS FILES PREVIOUSLY POSTED, THESE ARE THE ONLY FILES I KNOW THAT AFFECT THE LAME SERVER ISSUE.

; "/home/chroot-dns-int/var/named/db.127.0.0"
; ################################################## ##########
; Start of Authority (Inverse Address Arpa) for 127.0.0.0/8
; Filename: db.127.0.0
; ################################################## ##########
@ 604800 IN SOA testy.substantis.com. postmaster.substantis.com. (
2004092201 ; serial
10800 ; refresh (3 hour)
3600 ; retry (1 hour)
604800 ; expire (7 days)
86400 ) ; minimum (1 day)
;
; ################################################## ##########
; Specify Name Servers for all Reverse Lookups (IN-ADDR.ARPA)
; ################################################## ##########
@ 604800 IN NS testy.substantis.com.

; ################################################## ##########
; Iverse Address Arpa Records (PTR's)
; ################################################## ##########
1 86400 IN PTR localhost.substantis.com.


[root@testy named]# cat /etc/hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 testy.substantis.com testy localhost
[root@testy named]#

[root@testy named]# cat /etc/resolv.conf
search substantis.com
nameserver 127.0.0.1

# nameserver 66.92.159.2
# nameserver 216.231.41.2
[root@testy named]#

[root@testy named]# cat /etc/host.conf
#Lookup names via /etc/hosts first then fall back to DNS.
order hosts, bind
# We have machines with multiple IP addresses.
multi on
[root@testy named]#