help i've inherited a .corp domain

I inherited a .corp domain at my new company.  We have several SSL certs and external DNS names that have the .CORP suffix associated with them.  This year all the 3rd party CA vendors have told me that they will not renew my .CORP ssl certificates and that I should figure out how to rename my external DNS names to something other than .CORP.  We do own a public .COM address and could use that on the outside for DNS and certificate generation.  But... I'd have to stand up this domain because it doesn't exist yet, and I'd have to work out some kind of trust between my existing .CORP domain and this new .COM domain.  

I guess my question is,.... is there an easier way to accomplish this?  Migrating all objects from the .CORP domain to the .COM domain would take at least 12 months given the complexity of the environment.

thanks in advance
mppickardAsked:
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.

it_saigeDeveloperCommented:
Actually, you don't have to change your internal domain to .com.  Just use a split DNS where you have (in your case) a .CORP dns tree (this is what your internal computers will primarily use for communication) and a secondary .COM domain so that your internal clients can access externally available internal resources by their respective DNS name.

-saige-
0
aleghartCommented:
You can continue to use .corp TLD internally, but when you publish DNS servers via DHCP, you must _not_ use any public DNS servers.  Some admins will put their own internal DNS servers as primary and secondary, then list a public DNS server as tertiary "backup".  Sounds good on paper...until you start resolving internal hostnames to external hosts that are not under your control.

The mis-use of ".corp" is what stalled ICANN from accepting it for gTLD.  It's considered "high-risk" due to the volume of DNS resolves that actually make it outside the LAN to a public DNS server.

How are you publishing ".corp" hostnames externally?  I'm confused about that.
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
mppickardAuthor Commented:
Yeah I already figured it would be a heap of work.  and we don't publish .corp outside the company just internal.
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
Windows Server 2008

From novice to tech pro — start learning today.