Bug 84932 - BIND - Caching Nameserver RFC1912 Section 4.1
BIND - Caching Nameserver RFC1912 Section 4.1
Product: Red Hat Linux
Classification: Retired
Component: caching-nameserver (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jason Vas Dias
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2003-02-23 20:52 EST by Need Real Name
Modified: 2007-04-18 12:51 EDT (History)
1 user (show)

See Also:
Fixed In Version: caching-nameserver-7.3-3
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-08-25 19:03:04 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2004:568 normal SHIPPED_LIVE Updated caching-nameserver package 2004-12-21 00:00:00 EST

  None (edit)
Description Need Real Name 2003-02-23 20:52:29 EST
Description of problem:

RFC1912, section 4.1 lists a set of zones that should be included in all name
servers.  It lists:

primary         localhost               localhost
primary         0.0.127.in-addr.arpa    127.0
primary         255.in-addr.arpa        255
primary         0.in-addr.arpa          0

The caching-nameserver package includes the first two of these, but not the
latter two.

Version-Release number of selected component (if applicable): N/A

How reproducible:

This is a configuration error, not a software bug.
Comment 1 Need Real Name 2003-03-10 14:03:35 EST
Given that new installations are set to "localhost.localdomain," the informal
TLD "localdomain" should be added to the list of authoritative domains that is
included in the default BIND configuration on Red Hat Linux.
Comment 2 Jason Vas Dias 2004-08-25 19:03:04 EDT
This is now fixed (caching-nameserver-7.3-3).
Comment 3 John Flanagan 2004-12-21 14:52:17 EST
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


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