DMZ DNS Configuration Best Practice - TechRepublic
DMZ DNS Configuration Best Practice - TechRepublic
Networks
REGISTER NOW or LOG IN to post
QUESTION
LOCKED
Hello all,
I just inherited a network where they are using public IPs for everything in the DMZ. The firewall is configured in “drop in”
mode and all DMZ servers have public IP’s.
My question is in regards to configuring DMZ DNS servers. Our exchange server is in the DMZ and authenicates to internal
DC’s. This servers primary dns points to internal dns server and it’s secondary points to a dmz dns server. Can you tell me
what the configuraton would look like for this setup.
The DMZ dns servers are configured with our internal dns zone records for our 2 interal DC’s. Isn’t it a bad thing to host
internal dns records on public facing servers?
Please help!
This conversation is currently closed to new comments.
ALL ANSWERS
Clarifications
by mwoods269
· about 12 years, 8 months ago
In reply to DMZ DNS configuration best practice
Clarifications
Next ask yourself if your Exchange Server is in the DMZ, is it configured as a Bridgehead or a Front End Exchange?
Last question you should ask yourself is, are non DMZ DNS servers domain name public or private.
Armed with answers to those questions, how the network is configured might make sense.
Summary of network
by mwoods269
· about 12 years, 8 months ago
In reply to DMZ DNS configuration best practice
Fatpipe ISP load balancer hosting external DNS records for our domain
– no forwarders configured
– zone transfers all from any server for the internal .local zone
– hosts forward lookup zones for DMZ as well as our internal resources
– both point to themselves for DNS and to the Fatpipe for secondary dns
– both point to themselves for dns and to each other for secondary dns
– zone transfers to servers listed in name servers tab (2 internal and 1 dmz
The Exchange server is standalone and serving email for our users.
DNS on DMZ
by cg it
· about 12 years, 8 months ago
In reply to Summary of network
typically DNS servers in a DMZ [meaning behind the perimeter firewall and in front of the local network firewall,
typically are for authoritative name servers for a FQDN. These authoritative name servers provide public address to
FQDN resolution for Internet WhoIs queries. These DNS servers can also provide alias support for the local network in
translating a public name to a private name eg .com to a .local
DNS servers behind the local network firewall provide local network name to address resolution for local network
More Newsletters Forums Resource Library Join / Search
queries. Typically in an Active Directory or Directory Services environment. Sign In
When the local DNS server can not answer queries they forward that query to other name servers for resolution.
Example, a web site using your FQDN .com can’t be answered by your internal DNS servers because they can only
resolve a private name .local to an address. So it forward those to the Internet root-hint servers. These servers put out
a WhoIs query eg. WhoIs .com if your DMZ DNS servers are the authoritative DNS servers for your domain name, they
answer the query .com = your public IP address. Therefore the answer to the query is your public IP address. Traffic is
then sent to that address over the specific protocol port. example you host your web site .com on a web server in your
DMZ. Traffic would be sent to your public IP address over port 80. you forward that port traffic [port 80] through your
perimeter router to your web server which will then provide the web page.
So this is why in my original post I asked, are you sure? DNS servers in a DMZ play a role if those DNS servers are the
authoritative DNS for your public domain name. They provide name to public address resolution for your FQDN.
Without that, no one would know that FQDN domain.com is your public IP address and then send traffic to you such as
email.
Well Explained v/ v/
by robo_dev
· about 12 years, 8 months ago
In reply to DNS on DMZ
And, call me crazy, but there are significant security risks to exactly how your expose DNS and AD to your DMZ.
Since LDAP, by default, is not encrypted, you really need to look at technology such as ADFS (Active Directory
Federated Services) to effectively ‘proxify’ and sign/encrypt AD LDAP traffic to/from DMZ.
Of course the best answer is to ‘say no’ and not allow AD to cross the firewall in the first place….
AD DNS really doesn’t have to cross into the DMZ. AD only need DNS for the local LAN. Doesn’t care about
anything else.
START OR SEARCH
START NEW DISCUSSION Join /
More Newsletters Forums Resource Library Search
Sign In
DOWNLOAD NOW
DOWNLOAD NOW
LEARN MORE
LEARN MORE
RELATED DISCUSSIONS
RELATED FORUMS
DOWNLOAD NOW
DOWNLOAD NOW
LEARN MORE
Email Address
I agree to the
Terms of Use
and
Privacy Policy
. I understand I will
receive a complimentary subscription to TechRepublic's News and
Special Offers newsletter, and Top Story of the Day newsletter (you
can opt out at any time).
S b ib
Join /
More Newsletters Forums Resource Library Sign In Search
SERVICES
About Us FAQ
Membership Advertise
RSS Feeds
Site Map
EXPLORE
TechRepublic Academy
TechRepublic Premium