Bug 32991 – Serverfail on DNS refresh

Bug 32991 - Serverfail on DNS refresh


Summary:	Serverfail on DNS refresh

Status:	RESOLVED DUPLICATE of bug 28363

Product:	UCS
Classification:	Unclassified
Component:	DNS
Version:	UCS 3.1
Hardware:	Other Linux

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2013-10-28 17:54 CET by Kevin Dominik Korte
Modified:	2018-04-13 13:32 CEST (History)
CC List:	1 user (show)

See Also:
What kind of report is it?:	---
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
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 Kevin Dominik Korte

2013-10-28 17:54:28 CET

When DNS Server Refresh the zone, it writes an error to the daemonlog about a server error. The DNS afterwards works fine, but it takes up a large amount of resources during the refresh.

daemon.log:
Oct 28 17:29:07 dczen-01 named[20163]: zone 41.121.10.in-addr.arpa/IN: refresh: unexpected rcode (SERVFAIL) from master 127.0.0.1#7777 (source 0.0.0.0#0)

root@Master:~# udm dns/reverse_zone list --filter subnet=10.121.41
subnet=10.121.41
DN: zoneName=41.121.10.in-addr.arpa,cn=dns,<base>
ARG: None
  subnet: 10.121.41
  contact: root@<mail>
  retry: 2 hours
  expire: 7 days
  ttl: 1 days
  nameserver: <Master>
  serial: 2
  zonettl: 3 hours
  refresh: 8 hours

Comment 1 Stefan Gohmann

2013-11-11 06:40:19 CET

Can you try the DNS check script from Bug #28363#c1? Does it change the situation?

How can I reproduce it?

Comment 2 Kevin Dominik Korte

2013-11-11 15:26:00 CET


*** This bug has been marked as a duplicate of bug 28363 ***