server1.lan on site one, server2.lan on site two, server3.lan again on site one
Hi @Sob, the above is what the current scenario is.
Thanks all, for the replies. Redesigning the domain structure on an existing setup is a lot, therefore, will avoid that for now. Utilizing the DNS hosting service of the registered domain is an option I will look at.
At this moment, as a quick workaround to reduce maintenance on the static list, I created a dstnat on a Remote router to redirect udp traffic to the Main router and maintain the DNS entries on the Main router.
[chain=dstnat action=dst-nat to-addresses=<Main-router-IP> to-ports=53 protocol=udp in-interface-list=!WAN dst-port=53 log=yes log-prefix=""]
Question:-
1. With redirecting traffic approach shown above, does that mean that the originating router's DNS server setting will be totally ignored OR, will it be used either in Parallel or as a fallback if the redirect doesn't resolve the query or when the link to the Main router site is down?
2. DHCP only assigns router IP to the clients. Will having the DHCP assignment include both the router IP and public DNS IPs, mitigate the issue when the redirecting approach fails?
Thanks