Our internal office network has the same top-level domain as our company online presence, e.g.
For the outside world, any public hosts (eg.
www.ourdomain.com, etc.) are configured in the DNS of our domain hoster, AWS Route 53.
For the office intranet, we are running a simple
dnsmasq for DHCP and DNS (and VPN, but that's another story); name resolution for internal servers and desktop machines (e.g. laptops with DHCP addresses) in the office works fine. The
dnsmasq instance is not available to the public.
So far, we tell
dnsmasq about our public servers by maintaining a file
/etc/hosts.dnsmasq that is included into the main
/etc/dnsmasq.conf by a line
addn-hosts=/etc/hosts.dnsmasq, is similar to the wellknown
/etc/hosts and has the following sample contents:
188.8.131.52 blog 184.108.40.206 download 220.127.116.11 www
We maintain this file manually which is becoming cumbersome. We would like to get rid of it and improve our
dnsmasq setup so it does the following:
dnsmasqhas "own" DNS info (e.g. DHCP or static IP address associated with a hostname) for a query from the internal office network, serve that
- otherwise, query the public DNS and forward the result back to the asker on the intranet
Q: Is this doable with with
dnsmasq ? Does it require a subdomain for the office network ? (which we'd like to avoid, if possible) If so, how ? I have a feeling I must have gone through the
dnsmasq docs a hundred times; they're great, but I could just be looking at the solution, not seeing it.
Also: From my understanding, such a setup is different from split-brain DNS as we're not using one name server returning different responses depending on where the query comes from, but use a public and a private name server for the same domain.
Is this a common setup ? If not, is there a canonical way for organizations to configure their DNS when they use the same TLD for both public and private presences ?