RFC2136 client update after bind restart not working(?)
-
hi there, perhaps i am missing something.
when bind starts it sets the A record of a zone that is configured in the zone.
i have a rcf2136 client in place to update the A record.the update proces works fine after x days(forced from rfc2136 client) or when wan ip changes.
but when BIND starts (pfsense boot) or reloads (i.e. when WAN reloads) and the WAN ip is the same, BIND sets the pre-configured A record, and RFC2136 isnt updating it because it hasnt changed from its perspective.
is there some mechnism to force a rcf2136 update after bind (re)start even when WAN ip hasnt changed from the rfc2136 clients perspective?
-
//edit
for now i replaced my bind zone cname entry with a ddns provider that is updated via the pfsense ddns client that is holding the current ip until the client changes it.