Bug 882803

Summary: MX line in example.com.db causes bind to fail on startup
Product: OpenShift Container Platform Reporter: Jason Shepherd <jshepherd>
Component: DocumentationAssignee: Bilhar <baulakh>
Status: CLOSED WORKSFORME QA Contact: ecs-bugs
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.0.0CC: jokerman, libra-onpremise-devel, lmeyer, mmccomas
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-01-16 02:32:35 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jason Shepherd 2012-12-03 06:53:29 UTC 
Description of problem:

In section '5.2.2.2. Configuring Sub-domain Hostname Resolution', when including the line, 'NS	ns1.${domain}.' in example.com.db the command to start bind:

'service named start'

fails with "unknown RR type '15'"

Removing the line so example.com.db looks like this works:

$ORIGIN .
$TTL 1 ; 1 seconds (for testing only)
example.com IN SOA ns1.example.com. hostmaster.example.com. (
2011112904 ; serial
60 ; refresh (1 minute)
15 ; retry (15 seconds)
1800 ; expire (30 minutes)
10 ; minimum (10 seconds)
)
NS ns1.example.com.
$ORIGIN example.com.
ns1 A 127.0.0.1

https://github.com/markllama/bind-local/blob/update-external-ip/var/named/dynamic/example.com.db

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

1.0
Comment 2 Luke Meyer 2012-12-11 21:41:38 UTC 
I don't think this is true. I'm wondering if it was a cut-n-paste error by the reporter. Note that whitespace is significant in this file, and BZ appears to have stripped it... 

Need to verify the bug exists prior to making any changes.
Comment 3 Luke Meyer 2013-01-16 02:32:35 UTC 
I did a cut and paste from the docs and it looked fine. Feel free to re-open this if you can find a way (e.g. particular browser?) to cut and paste this that demonstrates the problem.