fallback to forwarder if master zone does not have requested record

Moser, Stefan (SIDB) stefan.moser at atos.net
Thu Oct 13 14:57:46 UTC 2011

Hi all,


in customer migrations, when we shift customers from an old DNS
environment to a new DNS environment, there are sometimes situations
where we have to keep the same domain (let's say "example.com") both on
the old DNS-server and on the new DNS-server. E.g., there was an A
record "mail.example.com" on the old DNS-server "dns-old", and an A
record "sap.example.com" on the new DNS-Server "dns-new". It would be
beneficial, if DNS-clients of "dns-new" could resolve both
"mail.example.com" and "sap.example.com", across both DNS-servers. I
can't think of a meaningful BIND configuration to "mix" both zones,
because of the inherent zone / authoritative model that DNS and BIND
have and that makes forwarders, masters and slaves mutually exclusive.
What would be needed was some kind of "fallback forwarder" that would
forward requests it cannot find in a zone that it is authoritative for.


Any ideas?



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20111013/ee54c89c/attachment.html>

More information about the bind-users mailing list