DMZ Name Resolution Best Practice

Hello, my question is more of a design/best practice question, no real issue...

What is the best way to configure DNS/name resolution for servers in the DMZ for both internal name resolution as well as external resolution.

I'll start with Internal:  If you have an application that needs access to a specific service behind the firewall, say for example a DB server.  It obviously isn't best practice to use/hard code an IP address for the DB server in the configuration of the application needing access to the DB server so you are stuck with DNS name.  Somehow we need to resolve the DNS name to an IP.  Is it better to use the hosts file or use some type of DNS server?  If DNS is the best method is it better to have a DNS server in the DMZ that houses a zone copy of internal records or is it better to pinhole the firewall and give access to an internal DNS server?

External:
Use a DNS server in the DMZ that will perform recursive lookups or use an all together external server to perform the recursive lookups?

Any help would be greatly appreciated....

Blake
isoperationsAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Ron MalmsteadInformation Services ManagerCommented:
Well let's start with the purpose of the DMZ.

We put those servers there to segreggate them from the network.  In the event they are comprimised, they do not have full access to the network.  As far as a router/firewall is concerned, it's a seperate network entity.

That being said.... we might not want the dmz servers to be able to resolve all the internal hosts...just the ones they need to function and communicate with directly.

You could give the server access to your internal dns servers through firewall rules....but some might construe that as a  weakening the restrictive purpose of the dmz.

In most cases, people need some traffic types to be able to traverse the dmz, (often times SQL)...but the best practice is to only do it when there is no other solution.

The idea of having another dns server, zone copy, is basically the same thing...unless you manage exactly what records are in the zone.

In short...if there are only a few hosts it needs to contact directly, then I would use a host file, or don't use hostname mappings but rather IP address for everything.  It's usually the pinhole that gets exploited first....so avoid it if you can.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
DNS

From novice to tech pro — start learning today.