Bug 43827 – DNS Entries still containing the old master after backup2master

Bug 43827 - DNS Entries still containing the old master after backup2master


Summary:	DNS Entries still containing the old master after backup2master

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	backup2master
Version:	UCS 4.2
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UCS maintainers
QA Contact:	UCS maintainers

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2017-03-13 12:45 CET by Christina Scheinig
Modified:	2020-07-03 20:53 CEST (History)
CC List:	3 users (show)

See Also:	35462
What kind of report is it?:	Bug Report
What type of bug is this?:	3: Simply Wrong: The implementation doesn't match the docu
Who will be affected by this bug?:	2: Will only affect a few installed domains
How will those affected feel about the bug?:	2: A Pain – users won’t like this once they notice it
User Pain:	0.069
Enterprise Customer affected?:	Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2017022721000143, 2017083121000286
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Christina Scheinig

2017-03-13 12:45:13 CET

The old master had the ipaddress 192.168.0.150. Searching the host_entries I still can find the ip for several relativeDomainName entries:


udm dns/host_record list --superordinate zoneName=test.local,cn=dns,dc=test,dc=local

DN: relativeDomainName=ucs-sso,zoneName=test.local,cn=dns,dc=test,dc=local
ARG: None
  a: 192.168.0.153
  a: 192.168.0.150
  a: 192.168.0.151
  name: ucs-sso
  zonettl: 80600 seconds

DN: relativeDomainName=gc._msdcs,zoneName=test.local,cn=dns,dc=test,dc=local
ARG: None
  a: 192.168.0.153
  a: 192.168.0.150
  a: 192.168.0.151
  name: gc._msdcs
  zonettl: 80600 seconds

DN: relativeDomainName=DomainDnsZones,zoneName=test.local,cn=dns,dc=test,dc=local
ARG: None
  a: 192.168.0.153
  a: 192.168.0.150
  a: 192.168.0.151
  name: DomainDnsZones
  zonettl: 3 hours

DN: relativeDomainName=ForestDnsZones,zoneName=test.local,cn=dns,dc=test,dc=local
ARG: None
  a: 192.168.0.153
  a: 192.168.0.150
  a: 192.168.0.151
  name: ForestDnsZones
  zonettl: 3 hours

DN: relativeDomainName=master,zoneName=test.local,cn=dns,dc=test,dc=local
ARG: None
  a: 192.168.0.150
  name: master
  zonettl: 3 hours

Comment 1 Stefan Gohmann

2017-09-01 06:52:21 CEST

Happens again in a support case.

Comment 2 Michael Grandjean

2018-01-17 11:46:12 CET

Just as a remark: This worked fine at Ticket#2018011221000555

Comment 3 Ingo Steuwer

2020-07-03 20:53:30 CEST

This issue has been filed against UCS 4.2.

UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.