Active Directory DNS: single entry for external domain?

Sorry for the convoluted title.

I have the following situation:

A web server that lives in our company intranet has an address in a private range in the domain mycorp.localdomain. Certain license restrictions prevent us from changing this address. Port 443 is made public using port-forwarding over a public address on our gateway. So far so good.

Externally, we use a hosted Linux server with Bind9 as the authoritative name server for the mycorp.com domain. This server resolves our web server fqdn to the external, public address, so:

superwebsite.mycorp.com -> 209.85.148.103 (apologies to google)

Internally, we use an W2k3 Active Directory server as a dns server. This server is authoritative for our intranet domain and resolves the internal fqdn of our server to the private address, so:

superwebsite.mycorp.localdomain -> 192.168.1.25

We have recently purchased a commercial SSL certificate for superwebsite.mycorp.com, so we need our internal AD Server to resolve the public fqdn to the private address, so:

superwebsite.mycorp.com -> 209.85.148.103

We also would like to serve Subversion repositories from this server, so it is important that the external URL be the same as the internal, otherwise developers will have trouble with their workspaces...

How can I tell Active Directory to resolve this one specific fqdn to the private address? Obviously I can't create the zone superwebsite.mycorp.com inside the intranet: this would cause the AD DNS server to consider itself authoritative and ignore the real authoritative server outside of the intranet.

Thanks!
alpha-lemmingAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
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.

.Commented:
I would do what you suggested, create a zone on your windows dns server. It means managing the same zone twice , depending on numbers though you could create an entry in he users hosts files.
Bruno PACIIT ConsultantCommented:
Hi,

What you can to solve your problem is :

1) on your internal DNS server create a new DNS zone named "superwebsite.mycorp.com" (a DNS zone with the full fqdn of the web server). Like that, your DNS server is authoritative for the zone "superwebsite.mycorp.com" but not for "mycorp.com".
2) in the new DNS zone create a DNS A record with no name, pointing to the internal IP address of the web server. DNS record with no name will be shown in the list as "same as parent" meaning that requests to "superwebsite.mycorp.com" will be resolved as a host name.
3) you may also have to configure IE exclusions depending on how your internal clients reach internet. If they are configured to use a proxy server then DNS resolution is not made by the internet browser but is done by the proxy server. So if you want your internal users to reach the extranet web server on the internal IP address and resolve the name using the new DNS zone on the internal DNS server you must make things so that internet browser don't use proxy for this URL. You can do that adding the "superwebsite.mycorp.com" name in IE proxy exclusions.

Have a good day.

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
SteveCommented:
Hi alpha-lemming,

you have two viable options as touched upon by the guys above:

Hosts file entries to override DNS.
You can add the entry to the Hosts file on internal clients so they are forced to use the internal address for the external FQDN.
this depends on how many clients you have as it could be a pain. its also a bit of a naughty solution but is perfectly valid.

new zone.
You existing dns server can host the external DNS zone without a problem. it does mean you'll have to manually store entries for anything yor clients may access from inside but works fine in many systems.
If you have a lot of DNS entries this may be a bit more admin than you'd like, but is otherwise the safest option.
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
Active Directory

From novice to tech pro — start learning today.