Search Engine: Elastic

Article ID: 130485, created on Mar 21, 2017, last review on Mar 21, 2017

  • Applies to:
  • Operations Automation 7.0
  • Operations Automation 6.0

Symptoms

There is a significant delay during DNS records data propagation between two or more NS servers registered in OSA system.

Comparing the DNS zone details of some updated zone reveals that new data is still missing on one of the DNS servers, which causes a delay in DNS resolution of the update domains.

Update PowerDns or Update named tasks are scheduled on constant basis every 5 minutes.

Cause

The system is currently under increased load of DNS updates, and the events are getting queued up, delaying the timely propagation of DNS records. The default behavior of the DNS service controller is to process 20 DNS zone updates every 5 minutes.

Resolution

It is possible to change the default interval of scheduling DNS update tasks and make it lower than 5 minutes.

CAUTION: the change may bring additional load on the system and lead to degraded performance. It is not recommended to apply the changes on permanent basis.

The following scripts may be used to commit the change:

Example of script usage:

# python changeBINDinterval.py 60

The command will change the interval of DNS zone updates from default 5 minutes (300 seconds) to 1 minute (60 seconds).

It is required to restart OA service to commit the change afterwards.

OA >= 7.0

# service pa-agent stop
# service pa-agent start

OA < 7.0

# service pem stop
# service pem start

0871c0b47b3b86ae3b1af4c2942cd0ce caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 5356b422f65bdad1c3e9edca5d74a1ae 1941880841f714e458ae4dc3d9f3062d 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0

Email subscription for changes to this article
Save as PDF