Sunday, March 11, 2018

domain name system - Active Directory: is it good to have 127.0.0.1 as DNS server entry on 2 machines that are 2 DNS servers in a local net?



This is a small local net with 10 computers in an office, they are running ms server 2003 active directory with 2 domain controllers. Each of the 2 DCs is also a DNS server and they syncronize. There are no more than these 2 DCs and 8 client machines in the whole domain.



In the config of the only network card of each computer it is like this:



The 8 client machines have an entry of DC1 as 1st and DC2 as 2nd DNS server. DC1 and DC2 both have 127.0.0.1 as DNS server entry.



Is there anything bad about this entry 127.0.0.1? I thought this is simple and clean and microsoft standard? Would it be better to put the own lan address (192.168.0.11 on DC1 and 192.168.0.12 on DC2) and not the loopback address there?




The DNS servers themselves (on DC1 and DC2) do their external lookups on the dsl-router.


Answer



I think that is perfectly fine.



It wouldn't be a good idea to put their LAN IP because if that ever changes, the DNS resolution may be broken. 127.0.0.1 will never change and will always point to the right ressource so you can just leave this as is.


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...