Learn F5 Technologies, Get Answers & Share Community Solutions Join DevCentral

Filter by:
  • Solution
  • Technology
Answers

A way to force DNS express zone reload?

Is there a way to manually trigger a DNS express zone transfer on BIG-IP? A client requires the ability to reload/refresh the DNS express zone when changes are made on the master nameserver.

0
Rate this Question

Answers to this Question

placeholder+image
USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER
Comments on this Answer
Comment made 18-Nov-2014 by G. Scott Harris 1648
I agree, this is what NOTIFY is for. However the client's specific requirement is to be able to manually initiate a zone transfer from BIG-IP. Quote: "we can't rely on NOTIFY in all instances". I found the command to load the dns express db from tmsh but the description states that this will load the db from the file system on BIG-IP into running config. I haven't been able to test yet to see if it also does a zone xfer.
0
Comment made 18-Jul-2016 by dmgeurts 64

Did you find an answer to this? I have noticed that disabling a zone and reenabling will cause the F5 to issue an XFR but this is crude and will cause a temporary outage on the zone.

Note to self: read down further in the future. Fbusta posted the same suggestion a month ago...

0
placeholder+image
USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER

This works for me:

Go into the DNS Express zone properties for your domain and then select State -> DISABLED, click update. Then State -> Enabled, update.

1
placeholder+image
USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER

Hmmm, can't imagine there's another way other than restarting DNS Express itself, even then I'd test to make sure;

bigstart restart zxfrd

DNS Express services will of course be down for a short time.

0
Comments on this Answer
Comment made 18-Nov-2014 by What Lies Beneath 6708
You might also want to look into why NOTIFY can't be relied upon. Its a constant source of pain that the F5 is relied upon to fix everyone else's problems, and testament to its abilities in most cases.
2
Comment made 19-Nov-2014 by G. Scott Harris 1648
Okay. Thanks for the input. I'll pass it along. I'm just assisting in a hands-off, advisory type role and I don't have any direct access to their environment. They tell me manually forcing a secondary zone reload on their servers is faster than NOTIFY.
0
Comment made 19-Nov-2014 by What Lies Beneath 6708
OK, cheers.
0
Comment made 17-Mar-2015 by Jan Šoc 0
Hi. `bigstart restart zxfrd` did not work for me. I remove the dns data by `rm /var/named/config/namedb/db.external.forexampl.com.` and after that, i run `bigstart restart named` and the new file /var/named/config/namedb/db.external.forexampl.com. was created ;-) i know, that this is not so beautiful way, but it works for me.
0
Comment made 30-Oct-2016 by kwkyiu 5

One of the possible scenario is that the master is a multi-master cluster (e.g. Microsoft AD integrated zone) where the serial number did not sync across the cluster. It may break the zone transfer mechanism and requires to 'flush' the zone which likely to be a manual operation.

Anyone had experience on such design?

0