Friday, January 27, 2017

domain name system - DNS for private network - should router be the DNS server?



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?


Answer



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.


No comments:

Post a Comment

linux - How to SSH to ec2 instance in VPC private subnet via NAT server

I have created a VPC in aws with a public subnet and a private subnet. The private subnet does not have direct access to external network. S...