Windows Server 2008 DNS

I have an FTP/https server in my DMZ.  I need to access the server as https://servername.domainname.com from both the external public domain and the inside interface, because when sharing a file or folder the software uses the url that was used to access the server.

Our internal domain is domain.internal.com so when I use DNS to access the site I get https://servername.domain.internal.com (and of course this link does not work when received by an external user).

I can use a host file entry to get around this by using the DMZ, local IP address 172.17.10.5 with the fqdn of servername.domain.com (just leaving out .internal)

How can I accomplish this using Windows 2008 DNS so I don't have to bother the users?
BTExperthelpAsked:
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.

smckeown777Commented:
Just create a new Forward Lookup zone in the DNS console called 'domainname.com'
Then add an A record for 'servername' which points to the internal IP address...

That should take care of this for all users...
0
lruiz52Commented:
Exactly what smckeown777 suggested.

Its called Split-brain DNS or Split DNS. check out the link below for visual instructions on how to set it up.

http://www.thesuperkev.com/2012/10/setting-up-split-dns-in-windows-server.html
0
DrDave242Commented:
I recommend something slightly different. Instead of creating a forward lookup zone named domainname.com, create one named servername.domainname.com. Inside that zone, create a blank host record and give it the local IP address of the server you need to reach.

This way, servername.domainname.com will be resolved by your internal DNS server, while other .domainname.com names will still be resolved by the public DNS, and you won't have to create records for them.
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
BTExperthelpAuthor Commented:
Thanks DrDave242, worked just the way I want.
0
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.

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.