<div>
could you please explain it better.. you have an internal dns behind a firewall .. this is fine.. in the dmz you don't need nor want a dns server .. protecting this server will be a problem.
</div>


could you please explain it better.. you have an internal dns behind a firewall .. this is fine.. in the dmz you don't need nor want a dns server .. protecting this server will be a problem.

<div>
Are you hosting your own External DNS? Usually domain controllers also hold the DNS role as well. They site on the internal network and query based on forwarders and or root hints in your DNS configuration. <br />
<br />
I would then also ensure that you use a 3rd party DNS provider which is much more flexible when it comes to DR scenarios. <br />
<br />
Will.
</div>


Are you hosting your own External DNS? Usually domain controllers also hold the DNS role as well. They site on the internal network and query based on forwarders and or root hints in your DNS configuration.

I would then also ensure that you use a 3rd party DNS provider which is much more flexible when it comes to DR scenarios.

Will.

<div>
We have a firewall and AD / DNS Servers which is all internal. My superior has suggested adding a DNS on DMZ where our internal DNS will forward to that as an added layer of security. I'm taking this is not a recommended setup?
</div>


We have a firewall and AD / DNS Servers which is all internal. My superior has suggested adding a DNS on DMZ where our internal DNS will forward to that as an added layer of security. I'm taking this is not a recommended setup?

<div>
<div class="content wysiwyg-content">
We're a windows based shop and have been tasked to setup DNS on a DMZ to forward external lookups. From what I've reviewed this will set us to a single point of failure and should be running core. If that is the case do the servers on the DMZ need to be part of the domain? I'm guessing not...<br />
<br />
Can anyone provide any other suggestions or recommendation should we move forward with this design?
</div>
</div>


We're a windows based shop and have been tasked to setup DNS on a DMZ to forward external lookups. From what I've reviewed this will set us to a single point of failure and should be running core. If that is the case do the servers on the DMZ need to be part of the domain? I'm guessing not...

Can anyone provide any other suggestions or recommendation should we move forward with this design?

DNS DMZ design?

The Domain Name System (DNS) is a hierarchical, globally distributed system responsible for associating the name of a computer, service or other resource into an IP address for connecting to the Internet or a private network. Most prominently, it translates domain names to the numerical IP addresses needed for the purpose of computer services and devices worldwide.

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.

Active Directory

Security is the protection of information systems from theft or damage to the hardware, the software, and the information on them, as well as from disruption or misdirection of the services they provide. The main goal of security is protecting assets, and an asset is anything of value and worthy of protection.  Information Security is a discipline of protecting information assets from threats through safeguards to achieve the objectives of confidentiality, integrity, and availability or CIA for short. On the other hand, disclosure, alteration, and disruption (DAD) compromise the security objectives.