Forum Discussion
Changing ZoneRunner NOTIFY Source Address
Hey guys/gals, I know this post is very old... but
I'm having a very similar problem. My ISP provider will not process NOTIFY on one address and perform a zone transfer to another IP.
My specific problem is caused by the egress path used for the NOTIFY is different than the ingress path for the DNS servers. I think this is because NOTIFY messages use Common partition egress and for external DNS listeners I've placed them in an /EXT/ partition. F5 is behind an ASA with NAT to those /EXT/ listeners.
I've been told by a few F5 experts to leave the BIND implementation alone, e.g. don't manually modify its files. Further, antonioc states it doesn't work to add notify-source to the named.conf.
Which means my only option is to change the NAT rule and create new listeners on the self-ips that are also used for egress NOTIFYs.
Any other ideas?
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
