Project

General

Profile

Actions

Bug #20618

closed

nameserver role can't coexist with nsupdate

Added by David Galloway almost 7 years ago. Updated about 6 years ago.

Status:
Resolved
Priority:
Low
% Done:

0%

Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Crash signature (v1):
Crash signature (v2):

Description

When adding records to the ansible inventory, and thus, adding DNS records to the BIND master, nsupdate is still able to add records and somehow overwrites changes made by the ansible playbook.

The current solution is to pause the OVH queue, wait until no dynamic records need to be updated, then run the nameserver role.

I haven't completely debugged why but it takes about 2 minutes for the zone files to be populated. So the front.sepia.ceph.com zone file is done first, then while the rest of the zone files are populated and uploaded, nsupdate is making changes to the front.sepia.ceph.com zone file. Then when named is reloaded at the end, the A records we want added are missing.

PTR records do get created, however, because nsupdate doesn't touch reverse zone files.


Files

named_output.log (64 KB) named_output.log David Galloway, 07/13/2017 05:04 PM
Actions #1

Updated by David Galloway almost 7 years ago

I think an elegant solution might be to populate the zone files locally (on the machine running the nameserver role), then ship them all at once and quickly reload named in hopes of beating nsupdate.

Actions #3

Updated by David Galloway about 6 years ago

  • Status changed from 12 to Resolved
Actions

Also available in: Atom PDF