Split DNS with Windows 2008 Server

I have a DNS server that is on a DC that in the past typically stored the internal IP addresses for various hosts...  This makes sense for my domain environment.  But.. We also host various websites.  My question is in regards to the hosting / DNS resolution of websites.  So, for example..  On GoDaddy.com we'll use their DNS server and simply create A records pointing to the public IP of my web server.  I then have  NAT rule that sends all HTTP traffic to the private IP of my web server.  My internal DNS server returns this private IP address when queries are made against it...  Since only internal requests exists it works just fine.  That makes sense and is very simple.  Now...  I would like the ability to point GoDaddy to my DNS server directly and have it answer the public DNS queries.  I also need my DNS server to still answer private requests for users will be hitting these websites internally also..  As I understand I need to setup split DNS.  This would be two zones. One for private and one for public requests...  My only question is how to tell the DNS server to allocate one zone for private and one for public?
gopher_49Asked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
footechConnect With a Mentor Commented:
I second the recommendations by Netflo.
Note that if the hostnames that you're trying to serve to both internal and external clients are using the same domain name, there is no way to specify more than one zone with the same name.  For instance, if both internal and external clients are trying to reach a host in the domain "example.com", you can't have two zones named "example.com" (on the same server) whereby responds to internal clients and one responds to external.
Even if the domain names are different, I would never recommend having your DC's DNS exposed to the internet.
0
 
NetfloConnect With a Mentor Commented:
I would recommend keeping your setup the way it is, for security purposes. To achieve your goal you would ideally need to introduce another server and place it in your DMZ done. Note this server does not replicate or talk to your internal DNS servers. You would also need to administer two zones, internal and external DNS names.
0
 
gopher_49Author Commented:
I'm going to keep my current config for now...  One I learn how to manage both DNS via websitepanel.net's solution I'll then move to the second DNS server config...  Everything works really well now..  Just trying to figure out how to allow end users/web developers to point to my DNS versus them creating host records.  For now this is fine...  The public IP's the host records are pointing to are about to be in a cluster and even upon hardware failure there is no need to change the IP address it's pointing to..

Thanks.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.