This service will be undergoing maintenance at 00:00 UTC, 2016-09-28. It is expected to last about 1 hours
Bug 24888 - BIND 9 not serving up local information
BIND 9 not serving up local information
Product: Red Hat Linux
Classification: Retired
Component: bind (Show other bugs)
i386 Linux
high Severity high
: ---
: ---
Assigned To: Bernhard Rosenkraenzer
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2001-01-24 17:41 EST by Wade Minter
Modified: 2005-10-31 17:00 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-01-24 17:41:30 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:

Attachments (Terms of Use)

  None (edit)
Description Wade Minter 2001-01-24 17:41:27 EST
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 ""{
        type master;
        file "";

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

> server
Default server:

** server can't find SERVFAIL

The file looks like:

                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

www             IN A  
mail            IN CNAME
courthouse      IN A  
kenbridge       IN A  
victoria        IN A  
dundas          IN A  

/var/log/messages only says:

Jan 24 17:48:19 courthouse named[1692]: dns_master_load: no TTL specified
Jan 24 17:48:19 courthouse named[1692]: dns_zone_load: zone loading master file no ttl
Comment 1 Bernhard Rosenkraenzer 2001-01-24 17:53:47 EST
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

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