On all our domain controller's we have in place Google Public DNS IP addresses as forwarders.
•8.8.8.8
•8.8.4.4
Not sure if this is good practice, any thoughts on this or recommendations?
Windows Server 2008DNS
Last Comment
lhrslsshahi
8/22/2022 - Mon
Mahesh
Its not best practise to set forwarders to public DNS on all AD \ DNS servers
If you have multiple sites having multiple DC \ DNS servers, then I prefer to enter forwarder DNS IPs on one DNS server in a given site.
Even in multisite organizations also, some times they preffer to route internet traffic through hub location.
For Microsoft, either root hints or forwaders must be set on all DNS servers to enable internet name resolution.in case of forwader fails root hints can \ will be used as fall back.
But in real world scenario, organization security policies wanted that internet traffic should be routed from perticular DC servers \ routers \Proxy devices.
hope that helps
Mahesh
*** Hopeleonie ***
You should add the DNS Servers from your Internet Provider.
Adding too much Servers will not bring you anything! Best practise is to have 2 - 3 Servers.
For an example: If you have 5 DNS Servers and the first will do the name resolution all other Servers are useless.
If you have multiple sites having multiple DC \ DNS servers, then I prefer to enter forwarder DNS IPs on one DNS server in a given site.
Even in multisite organizations also, some times they preffer to route internet traffic through hub location.
For Microsoft, either root hints or forwaders must be set on all DNS servers to enable internet name resolution.in case of forwader fails root hints can \ will be used as fall back.
But in real world scenario, organization security policies wanted that internet traffic should be routed from perticular DC servers \ routers \Proxy devices.
hope that helps
Mahesh