We cannot access our site internally, but we can access it everywhere else, why?

Experts,

We're confused.  We moved our corp website to an external hosting provider, and from the external world, we can hit the site just fine.  It seems to work everywhere BUT internally.  We are able to ping the IP of the site, we can tracert by the URL and the public IP successfully, but we cannot get any internal browser to bring the page up.  Not by URL or IP address.  What are we missing!?

Thanks!
cocosysengAsked:
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.

David PiniellaCommented:
When you resolve the DNS address of the site internally, does it resolve the public IP or the address from before you moved it?

What is the error you're actually getting? 404 not found, 500/503 or Page cannot be displayed or what, exactly?

Check the logs of the hosting provider, verify that your connection attempts are actually getting to the site and that the IP that you're coming from (your org is probably NAT'ing your internal users out) is not blocked from that site.
0
duncanb7Commented:
If it is not blocked by firewall from your internal network for blocking all http access, it should be
DNS propagation delay issue .Normally, the company website domain if change to
other new  hosting provider that will take within 48 hours to propagate the domain around
the world, so it will see some region can  view your page , some are not.
Up this moment, how long you transfer your site to the new hosting provider, one or two day ?

Maybe wait for one more day

Duncan
0
cocosysengAuthor Commented:
When we try to resole it internally, it resolves according to our DNS record with the current live public IP.
Tracert's confirm this, as our external DNS from our ISP is able to hit it just fine.

When we try to bring the page up internally, we get a 'page canot be displayed'.  If we enter in the IP address, we get a splash page from the vendor, not the site.
0
Top Threats of Q1 & How to Defend Against Them

WEBINAR: Join WatchGuard CTO and our Threat Research Team on Aug. 2nd to hear the findings from our Q1 Internet Security Report! Learn more about the top threats detected in the first quarter and how you can defend your business against them!

cocosysengAuthor Commented:
We transferred the site to the new hosting vendor Friday afternoon last week.  It works fine externally, in fact, it started working almost immediately.  it seems to be isolated to just the internal network here.
0
duncanb7Commented:
Please wait for one more day( I experienced this for 3 or 4 days).  And contact your hosting provider and
ask them what is wrong on the server with DNS record.

If possible, could you try  one command of "nslookup http://yourcompany.com" at window command shell
and "nslookup http://yahoo.com" to see any issue

Duncan
0
cocosysengAuthor Commented:
nslookup for both our site and yahoo returned correct information, bot the live IPs for yahoo and our corporate site were returned....   So I guess this is still a waiting game then?
0
duncanb7Commented:
Be sure your IP/domain you typed on browser and nslookup is same.
just waiting one more day. nslookup connection is working but doesn't
mean browser will work since nslookup will use different DNS server to resolve the domain.

Duncan
0
duncanb7Commented:
And one more thing, supposed your hosting company will make sure everything
transfer is okay to any issue whatever it is caused by   internally or externally.

Duncan
0
Joshua GrantomSenior Systems AdministratorCommented:
Also make sure that both records

@
www

are set to the new public IP address in your internal dns.
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
Joshua GrantomSenior Systems AdministratorCommented:
I would also make sure that your local host file has not been changed. The host file is located here

C:\Windows\System32\drivers\etc\

Open "hosts" with notepad and make sure there is not a line

mywebsite.com             Old internal ip address
0
cocosysengAuthor Commented:
That worked!  we got it!  We added a blank record to allow clients to just resolve domain.com and the www. record.  it fired right up!  Thanks all!!!
0
Joshua GrantomSenior Systems AdministratorCommented:
Awesome, Glad we could help!
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.