Bug 84932

Summary: BIND - Caching Nameserver RFC1912 Section 4.1
Product: [Retired] Red Hat Linux Reporter: Need Real Name <rnspayne>
Component: caching-nameserverAssignee: Jason Vas Dias <jvdias>
Status: CLOSED ERRATA QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.0CC: mitr
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
URL: http://ietf.org/rfc/rfc1912.txt
Whiteboard:
Fixed In Version: caching-nameserver-7.3-3 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-08-25 23:03:04 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Need Real Name 2003-02-24 01:52:29 UTC
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 19:03:35 UTC
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 23:03:04 UTC
This is now fixed (caching-nameserver-7.3-3).


Comment 3 John Flanagan 2004-12-21 19:52:17 UTC
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.

http://rhn.redhat.com/errata/RHBA-2004-568.html