Hostname / IP resolution

I have a website in IIS 7. Currently, I have my users access the website on the internal network by using the internal IP address, then have the external users access it using the external IP address. I've been trying combinations of the IIS Bindings with the Window server hosts file--using the internal IP in IIS, the external in the IP, to try to resolve all of these to one hostname, crm.mysite.com, but I just can't figure this out--it's as if I have to use the IP address on internal while the hostname works on external, or vice versa. How can I get my hostname/subdomain to work on both internal and external without it resolving to an IP address in the address bar?
saturationAsked:
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.

KimputerCommented:
on your internal DNS, make an A entry for crm.mysite.com, and let it have the IIS7 server internal IP
0
saturationAuthor Commented:
I did make an A entry for it on the DNS with the internal IP address--same issue...So I have three places:

1) DNS entry for the crm.mysite.com on the internal DNS server
2) Windows hosts file with a line for 192.168.15.13      crm.mysite.com
3) An IIS Binding for the same as #2.
0
saturationAuthor Commented:
In addition to my comment above, creating the DNS entry in the internal DNS server had already been completed when I submitted this question, and the problem still remains...Any other help?
0
How do you know if your security is working?

Protecting your business doesn’t have to mean sifting through endless alerts and notifications. With WatchGuard Total Security Suite, you can feel confident that your business is secure, meaning you can get back to the things that have been sitting on your to-do list.

footechCommented:
Remove any HOSTS file entries for the site - they're not needed.  All you need an A record in public DNS which points to the public IP (for clients on the internet), and an A record on your internal DNS which points to the private IP (for clients on your network).  If you have your firewall and NAT set up correctly that's all you need.  Shouldn't need to mess around with bindings in IIS.
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
samriCommented:
also, plesae check on the IIS7.  You may need to adjust this to bind to the internal DNS name, and external DNS name as well.


As I am not familiar with IIS7 -- http://technet.microsoft.com/en-us/library/cc753195%28v=ws.10%29.aspx
0
saturationAuthor Commented:
Thank you!
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.