Are you talking about recursive clients failing over?
Or other nameservers trying to talk to yours, non-recursively?
Recursive clients don't use NS records at all and you need to approach
the failover problem in a completely different way (e.g. relying on the
client failing over from one resolver IP address to another, or
implementing an Anycast solution).
If you're talking about nameserver-to-nameserver traffic, then just
publish multiple NS records for the relevant zone(s) and the
nameserver-selection algorithm embedded in every known
iterative-resolver implementation will take care of the load-balancing
and failover; to summarize, faster-responding nameservers will be chosen
over slower-responding ones.
- Kevin
On 9/16/2011 11:17 AM, babu dheen wrote:
Hi,
Can anyone let me know how i can resolve the below requirement.
Requirement:
We have two offices. One is main office and another one is remote
branch office. Now my company client requirement is that if main
office DNS server is not reachable, all DNS query should be sent to
branch office DNS server. How this can be acheived using BIND?
For example, my company mail website is; mail.mycompany.com which is
pointed as below in ISP name server.
mail.mycompany.com IN NS ns1.mainoffice.com
mail.mycompany.com IN NS ns1.branceoffice.com
Is the above record is correct or not?
Please suggest.
Regards
papdheen M
_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
