| Summary: | 5.2.2. Configuring BIND and DNS | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Luke Meyer <lmeyer> |
| Component: | Documentation | Assignee: | Alex Dellapenta <adellape> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | ecs-bugs |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 2.0.0 | CC: | adellape, alyoung, baulakh, fhornain, 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: | 2014-01-09 05:17:12 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: | |
|
Description
Luke Meyer
2013-12-10 21:41:26 UTC
Turns out that the spacing for the .db file in the 1.2 manual *also* doesn't cut/paste correctly, because it includes tabs. I did some fiddling with BIND conf and discovered that it doesn't matter if you use tabs or spaces, and doesn't matter if everything lines up; what *does* matter is that the series of lines that start with space.... *must* start with space. And things that have spaces between them must have space :) Just doesn't matter if it's one space or many. But cut and paste to a terminal generally doesn't seem to work if it includes a tab.
I think this should do:
cat <<EOF > /var/named/dynamic/${domain}.db
\$ORIGIN .
\$TTL 1 ; 1 seconds (for testing only)
${domain} IN SOA ns1.${domain}. hostmaster.${domain}. (
2011112904 ; serial
60 ; refresh (1 minute)
15 ; retry (15 seconds)
1800 ; expire (30 minutes)
10 ; minimum (10 seconds)
)
NS ns1.${domain}.
MX 10 mail.${domain}.
\$ORIGIN ${domain}.
ns1 A 127.0.0.1
EOF
*** Bug 1051662 has been marked as a duplicate of this bug. *** The OSE 2 Deployment Guide has been updated to address this BZ. |