Article ID: 126501, created on Aug 10, 2015, last review on Nov 26, 2015

  • Applies to:
  • Odin Business Automation Standard 4.5

Symptoms

DNS zones are not synchronized between OBAS and a slave name server until the named service is restarted on the slave server.

In /var/log/messages there are records like

Mar 25 04:19:05 hspc pdns[17520]: 1 domain for which we are master needs notifications
Mar 25 04:19:05 hspc pdns[17520]: Queued notification of domain 'sup-test123.com' to xx.xx.xx.xx
Mar 25 04:19:05 hspc pdns[17520]: Queued notification of domain 'sup-test123.com' to xx.xx.xx.xx
Mar 25 04:19:06 hspc pdns[17520]: Received unsuccesful notification report for 'sup-test123.com' from xx.xx.xx.xx, rcode: 9
Mar 25 04:19:06 hspc pdns[17520]: Removed from notification list: 'sup-test123.com' to xx.xx.xx.xx
Mar 25 04:19:06 hspc pdns[17520]: Received unsuccesful notification report for 'sup-test123.com' from xx.xx.xx.xx, rcode: 9
Mar 25 04:19:06 hspc pdns[17520]: Removed from notification list: 'sup-test123.com' to xx.xx.xx.xx
Mar 25 04:19:09 hspc pdns[17520]: No master domains need notifications

Cause

On the slave server BIND is installed into /usr/local/sbin/ directory, while by default it is installed in /usr/sbin/, therefore OBAS failes to execute rndc reload during adding or changing DNS records or zones.

Resolution

To resolve the issue, please create symlinks on the name server in question and check if rndc reload is working from the default location:

[root@ns2 ~]# ln -s /usr/local/sbin/rndc /usr/sbin/rndc
[root@ns2 ~]# /usr/sbin/rndc reload
server reload successful

Search Words

Restarting slave named: /usr/sbin/rndc reload

Received unsuccesful notification report

624ca542e40215e6f1d39170d8e7ec75 caea8340e2d186a540518d08602aa065 400e18f6ede9f8be5575a475d2d6b0a6 70a5401e8b9354cd1d64d0346f2c4a3e

Email subscription for changes to this article
Save as PDF