Bug 24888 - BIND 9 not serving up local information
Summary: BIND 9 not serving up local information
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: bind
Version: 7.1
Hardware: i386
OS: Linux
high
high
Target Milestone: ---
Assignee: Bernhard Rosenkraenzer
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-01-24 22:41 UTC by Wade Minter
Modified: 2005-10-31 22:00 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2001-01-24 22:41:30 UTC
Embargoed:


Attachments (Terms of Use)

Description Wade Minter 2001-01-24 22:41:27 UTC
I'm not sure if I'm doing something wrong or bind is acting weird, but
bind-9.1.0-0.b2.1 in beta2 isn't returning information on my local
domains.  I've got this in my named.conf file:

zone "lunenburg.org"{
        type master;
        file "db.lunenburg.org";
};

And the file db.lunenburg.org has proper zone information (copied from a
working bind8 server).  But when I query bind for information in the
lunenburg.org zone, it spits back something like:

> server 192.168.0.1
Default server: 192.168.0.1
Address: 192.168.0.1#53
> dundas.lunenburg.org
Server:         192.168.0.1
Address:        192.168.0.1#53

** server can't find dundas.lunenburg.org.: SERVFAIL
>

The db.lunenburg.org file looks like:

@ IN SOA        courthouse.lunenburg.org.        minter.lunenburg.org.
        (
                2000091501;     Serial
                10800;          Refresh after 3 hours
                3600;           Retry after 1 hour
                604800;         Expire after 1 week
                86400 );        Minimum TTL of 1 day

                IN NS   courthouse.lunenburg.org.

www             IN A            216.235.79.243
mail            IN CNAME        www.lunenburg.org.
courthouse      IN A            192.168.0.1
kenbridge       IN A            192.168.0.2
victoria        IN A            192.168.0.3
dundas          IN A            192.168.0.4

/var/log/messages only says:

Jan 24 17:48:19 courthouse named[1692]: dns_master_load:
db.lunenburg.org:1: no TTL specified
Jan 24 17:48:19 courthouse named[1692]: dns_zone_load: zone
lunenburg.org/IN: loading master file db.lunenburg.org: no ttl

Comment 1 Bernhard Rosenkraenzer 2001-01-24 22:53:47 UTC
Your zone file is not RFC compliant. Prior versions warned you about this, the
current version doesn't accept the file.
It`s just what syslog says: no TTL specified.

The easiest way to specify a TTL is adding it right after the "@" in the first
line, e.g.

@ 3600000 IN SOA courthouse.lunenburg.org. minter.lunenburg.org.


Note You need to log in before you can comment on or make changes to this bug.