Bug 891435

Summary:	dhcpnamedforward.pp is only needed for Bind running with DHCP
Product:	OpenShift Container Platform	Reporter:	Brenton Leanhardt <bleanhar>
Component:	Documentation	Assignee:	Bilhar <baulakh>
Status:	CLOSED CURRENTRELEASE	QA Contact:	ecs-bugs
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	1.0.0	CC:	jokerman, libra-onpremise-devel, mmccomas
Target Milestone:	---	Keywords:	Documentation
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-02-05 18:20:01 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 Brenton Leanhardt 2013-01-02 22:22:49 UTC

Description of problem:
The deployment guide mentions using make to build dhcpnamedforward.pp.  In reality most users will never need to use this.  The is only to allow Bind to work with /var/named/forwarders.conf.  This is only needed when the Bind server does not have a fixed IP address.  This is extremely rare out side of development.

It is important to note that this has nothing to with with the OpenShift Broker.  Only in development should a user run a DNS server on their broker.  I would suggest completely removing that step from "Procedure 5.8. To Configure the Required OpenShift Enterprise Plug-ins"

Comment 2 Bilhar 2013-01-15 01:05:38 UTC

This will be available in the next release.

Comment 5 Luke Meyer 2013-02-05 18:20:01 UTC

These are released AFAIK, apparently not in the errata release.