Problem with hint file?
andlil at towerrecords.com
andlil at towerrecords.com
Tue Dec 21 19:22:25 UTC 1999
Syslog doesn't seem to have anything of interest to say about it. Also,
Yes, there is a corefile generated. Below, I've included the syslog
output, the contents of my named.conf file, and the contents of one of the
zone files, I can send the contents of the named.run files or the corefile
if anyone would like to see them
Syslog Output:
----------------------
Dec 21 10:51:36 mts named[30298]: starting. named 8.2.2-P5 Mon Dec 20
13:13:58
CST 1999 ^Iroot at mts:/var/tmp/bind/src/bin/named
Dec 21 10:51:36 mts named[30298]: limit "max number of open files" not
supported
on this system - ignored
Dec 21 10:51:36 mts named[30298]: limit "max number of open files" not
supported
on this system - ignored
Dec 21 10:51:36 mts named[30298]: master zone "towerrecords.com" (IN)
loaded (se
rial 1999122101)
Dec 21 10:51:36 mts named[30298]: master zone "37.30.172.in-addr.arpa" (IN)
load
ed (serial 1999122101)
Dec 21 10:51:36 mts named[30298]: master zone "38.30.172.in-addr.arpa" (IN)
load
ed (serial 1999122101)
Dec 21 10:51:36 mts named[30298]: master zone "0.0.127.in-addr.arpa" (IN)
loaded
(serial 1999122101)
Dec 21 10:51:36 mts named[30298]: hint zone "" (IN) loaded (serial 0)
Dec 21 10:51:36 mts named[30298]: listening on [127.0.0.1].53 (lo0)
Dec 21 10:51:36 mts named[30298]: listening on [172.30.37.133].53 (en1)
Dec 21 10:51:36 mts named[30298]: listening on [172.30.37.135].53 (et1)
Dec 21 10:51:36 mts named[30298]: Forwarding source address is
[0.0.0.0].3039
Dec 21 10:51:36 mts named[52316]: Ready to answer queries.
Named.Conf:
--------------------
options {
directory "/etc/named";
};
zone "towerrecords.com" {
type master;
file "db.towerrecords.com";
};
zone "37.30.172.in-addr.arpa" {
type master;
file "db.172.30.37";
};
zone "38.30.172.in-addr.arpa" {
type master;
file "db.172.30.38";
};
zone "0.0.127.in-addr.arpa" {
type master;
file "db.127.0.0";
};
zone "." {
type hint;
file "named.cache";
};
db.towerrecords.com:
---------------------------------
$TTL 3600
@ IN SOA mts.towerrecords.com. root.towerrecords.com. (
1999122101 ; Serial
10800 ; Refresh 3 hours
3600 ; Retry 1 hour
604800 ; Expire 1 week
86400 ) ; Minimum TTL 1 day
IN NS mts.towerrecords.com.
loopback IN A 127.0.0.1
localhost IN CNAME loopback
mts IN A 205.166.37.5
;
; 172.30.37.0 Network
;
bigipint IN A 172.30.37.1
ncr01 IN A 172.30.37.11
ncr02 IN A 172.30.37.12
ncr03 IN A 172.30.37.13
ncr04 IN A 172.30.37.14
ns1 IN A 172.30.37.132
ns2 IN A 172.30.37.133
;
; 172.30.38.0 Network
;
bigipext IN A 172.30.38.1
towerfw5 IN A 172.30.38.2
king IN A 172.30.38.15
queen IN A 172.30.38.16
ace IN A 172.30.38.17
towerbabel IN A 172.30.38.20
tbabel IN A 172.30.38.20
www IN A 172.30.38.129
bigipvip IN A 172.30.38.129
ftp IN A 172.30.38.140
Kevin Darcy
<kcd at daimlerchr To: bind-users at isc.org
ysler.com> cc:
Sent by: Subject: Re: Problem with hint file?
kcd at daimlerchry
sler.com
12/20/99 07:11
PM
andlil at towerrecords.com wrote:
> Hi, I just built BIND 8.2.2P5 on an AIX box and am having a problem. I
am
> probably missing something really obvious, but I'm stumped.
>
> The issue is, if I try to start named with an essentially "normal"
> named.conf file (for instance one that I grabbed off of a BSDI box of
mine
> that is running BIND 8.2 also, or the one generated from my old
named.conf
> file |'ed through named-bootconf), the service starts, and within 1
second
> or less, dies.
>
> If, however, I rename the hint file or remove the entry for the hint zone
> in my named.conf file, named runs fine. (Well, it runs fine for local
> zones, but obviously cannot perform externa lookups).
>
> Any ideas? I've tried at least 4 different hint files and all seem to
> exhibit this issue.
What does syslog have to say about this? Is there a core file?
- Kevin
More information about the bind-users
mailing list