Can' access our website internally. ERR_CONNECTION_REFUSED

Hi,
We are having problems accessing our website that hosted somewhere else that has the same name as our internal domain.  The site is accessible outside of our network.  We have created an A record for www that points to the public address of the www.ourdomain.com on our internal dns server.  Nslookup on my laptop in the office resolves to the correct internal dns server and its IP and www.ourdomain.com resolves to the correct public address.  I can also successfully ping www.ourdomain.com.
Still, when I open a browser and go to www.ourdomain.com, I get the ERR_CONNECTION_REFUSED.
Any ideas?
Any help would be greatly appreciated.
JasonAsked:
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.

John Gates, CISSPSecurity ProfessionalCommented:
Well this is a textbook example of why Microsoft recommends a .local for internal domains.  So let me ask you this... What browser are you using?  Is you website SSL secured or not?  Let me know and I will help you further... Also, when you put the global ip address of you hosted website does it come up?

-D-
John Gates, CISSPSecurity ProfessionalCommented:
In other words instead of www.ourdomain.com put in the actual global IP and see if the site comes up.
JasonAuthor Commented:
Hi,
Thanks for your reply.  
From what I understand, Microsoft doesn't recommend using .local anymore and now recommend the use of subdomains like ad.domain.com.  I believe this is all due to the November deadline for CAs eliminating the use of SSL certs on any of the .local, .priv, or .int domains.  We must now use FQDNs.  
My boss insisted that we use domain.com and while I recommended ad.domain.com, he insisted we used domain.com.  I've done it successfully in the past during the 2000/2003 days but, aside from doing the A record for www, I don't remember what else I had to do, if anything, to get the external website working.  From what I've read, we have to do split-dns now.  Can you offer guidance with that?
The site does have an SSL attached to it from the people that host the site.
When I try to use the public IP of the website, I get a 404 error.
I appreciate your help on this.
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

JasonAuthor Commented:
...and I'm using Chrome.
John Gates, CISSPSecurity ProfessionalCommented:
Can people get to your domain outside the network?
JasonAuthor Commented:
They can get to www.ourdomain.com as long as you're not inside.
JasonAuthor Commented:
Figured it out.  Created a second zone for www.ctinc.com in the forward lookup zone with the A record for the public IP.

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
John Gates, CISSPSecurity ProfessionalCommented:
Glad you got it sorted.  There were a number of ways to address the issue. Obviously you have external DNS zones for the Internet page.  If you were responsible for the Internet as well as the Internal dns I would have recommended a BIND DNS server with views set up.  Then your internal DNS could have just forwarded requests to the bind server and the bind server could have given the internal IP clients a different set of local IPs and Internet clients the global set.  You had just one URL www.yourdomain.com so what you did was the easiest approach to solve the issue.  You can then do the same if you add ftp, etc..

-D-
John Gates, CISSPSecurity ProfessionalCommented:
Also you can still host a .local for internal clients.  If you set up a PKI infrastructure you can self sign certs for internal clients...  Regardless of Microsoft's new recommendations I still think .local is ok :-)

-D-
JasonAuthor Commented:
Figured it out.
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.