I want to set up BIND for a private subdomain on a private network, like in the question here: How to configure bind for a private subdomain?
My question is this – should my (linux) router act as the DNS server for this? Or should I have a seperate machine on the network acting as the DNS server? Does it not matter as long as all the machines on the network are configured to resolve to the internal DNS server?
It doesn’t matter where you run it as long as it is reachable from the internal machines.
DNS is a very lightweight service, which can easily coexist with many others on a machine.
However, make sure it keeps working. When DNS fails, dozens of things will stop working and you’ll be wondering what the heck is going on before you figure out DNS is down.
- Should / Can I use DNS Records to list “Private Hosts in Private LANs”?
- How to set up DNS-like access for private IP addresses on a VPN?
- How do I configure SQL Server 2005 to accept a connection to a private or internal IP address on a private network?
- Private DNS zone that resolves private subdomains, and forwards to public nameserver for existing public subdomains
- DNS consolidation, how to serve both internal network and the internet
Leave a comment
- What is the easiest way to upgrade my existing Perl 5.14 to Perl 5.16 on FreeBSD 9 using the ports system?
- Know if mysql has done its job
- Redirect https .com to https .co.uk without a valid SSL cert on .com without DNS change
- Why is it a bad idea to use customer email as from address
- 100% packets dropped on first RX queue on 3/5 raid6 iSCSI NAS devices using intel igb (resolved)