Can you somehow send DDNS update twice for zone?

[Simon Hobson]

SoLoR <solor at outlook.com> wrote:

> Im runing both DHCPv4 and DHCPv6 server, v4 is serving local IPs and v6 is
> serving public ips. Both are currently updating in to lets say
> lan.domain.com and everything is working as it suppose to however i dont
> like that if you resolve host from outside (lets say test.lan.domain.com)
> you will get local A and public AAAA record. So i decided it would be good
> to split configuration in bind in to internal and public view for that
> doimain. In internal view resolving hosts in lan.domain.com would give both
> A and AAAA records, but in public view you would only get AAAA. However here
> is a problem, to get this to work i would need to somehow convince dhcpv6
> server to send AAAA record update TWICE, one for public and one for
> internal, however since its technically same domain i cant find combination
> that would work. I tried adding 2 ips in to primary, in hope it will update
> both primary and i can separate them in bind with proper matching key/ip,
> without success, i tried double zone statements with different key/primary
> combination, no luck... 
> 
> So bottom line, is there a way for dhcp to send dns update for same zone
> twice? Or i guess other option would be to somehow pass update from one view
> to the other in bind...

AFAIK there is no way to do this directly - there will be other ways such as that suggested by Tony.

However, I would question whether this is actually what you want to do.
For services which are to be externally accessible, I would expect those to have static entries. In general, I would expect other internal host to not appear in the DNS at all - so they would not have AAAA record in your public view.

Also, what are you doing for reverse lookups ? The same problem would apply there unless you configure the relevant ip6.arpa zone in one view to be a forwarder or slave of the same zone in the other view. But from a privacy perspective, having public reverse lookups gives a name to each IP address - making the use of privacy addressing moot.