Bug 671281

Summary:	after adding a zone, bind needs a restart before the new zone will work.
Product:	[Retired] freeIPA	Reporter:	Michael Gregg <mgregg>
Component:	ipa-admintools	Assignee:	Rob Crittenden <rcritten>
Status:	CLOSED WONTFIX	QA Contact:	Chandrasekar Kannan <ckannan>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	benl, dpal
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:	2011-01-21 00:20:42 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Michael Gregg 2011-01-20 23:41:55 UTC

Description of problem:
after a dns zone is created with ipa dnszone-add, bind needs to be restarted before it starts resolving.

Version-Release number of selected component (if applicable):
ipa-server-2.0-0.2011011418gita68b2d2.fc14.x86_64

How reproducible:
always

Steps to Reproduce:
1. ipa dnszone-add newzone2
2. ipa dnsrecord-add newzone2 a --a-rec=1.2.3.4
3. dig a.newzone2
  
Actual results:
a.newzone2 not found without a named restart.

After a named restart, a.newzone2 is found.

Expected results:
If the dns plugin can be modified to not need a bind restart, great, otherwise, maybe a bind restart after a warning.
Or, a bind restart when --restart-bind is specified along with the dnszone-add.

Comment 1 Dmitri Pal 2011-01-21 00:20:42 UTC

There is already a doc bug about it: https://bugzilla.redhat.com/show_bug.cgi?id=670310

Filing and deferring the ticket. 
https://fedorahosted.org/freeipa/ticket/826

This is not going to be fixed for 2.0.

Comment 2 Michael Gregg 2011-01-21 00:26:51 UTC

Sounds good. 

Closing as duplicate.