www is external. Internal domain is same as external domain no web resolution for outside web site

I have a domain I created as mydomain.com internally which is a public domain as well.  My web site is www.mydomain.com. I have a DNS entry internally for www pointing to the external IP.  Ping inside hits external IP but browser fails.  Root domain mydomain.com still resolves internally to inside ip address.  I've created a delegation record for www. Fails. Internal DNS for www resolves but browser fails.  I've installed IIS and told it to redirect to www. Outside the domain (different location) works.  Something with Windows DNS I'm missing.  Please advise.
David BirdPartnerAsked:
Who is Participating?

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

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.

Patrick BogersDatacenter platform engineer LindowsCommented:

If your external domain is same as internal please login to your external DNS GUI and change the www record there. It seems you created some conflict.
Needless to say is it best practice to NOT have the same domain internally and externally (better call your internal domain mydomain.local) *just a tip*

David BirdPartnerAuthor Commented:
Yeah, learned that.  Already deployed. Working with what I already screwed up. hehe.
www at godaddy is already pointed to external IP.  @ with godaddy is external and www is external IP.  Missing something inside. Thoughts?
Not sure you can do what you are trying to do.

Here's what we have.  We also have an internal domain that is the same as our external one. IN DNS we have WWW set to point to the internal domain server and we get an Intranet page. If you try and hit that from the outside, we get our Internet page. We cannot hit the external site from inside the firewall by using the www.mydomain.com name. We have another reference for the external site in our external DNS records. So if we want to hit the external web site from inside, we browser to the alternate name and that takes us there like it does any other external web site.

This may also be affected by how you have your firewall configured.
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Patrick BogersDatacenter platform engineer LindowsCommented:
Sure.. ping hits but browser fails... sounds like caching on the browser site, what if you clear the cache on that browser or try another one?
David BirdPartnerAuthor Commented:
Did that. Cleared cache on the inside DNS server, on the client machine (ipconfig /flushdns) and on the browser(s), all history, cookies, cache etc.
Same result.  
My thoughts are that when the web tries to resolve, it is following the root domain path, which still resolves internally. I can't change that piece. I created a split DNS to handle WWW for external resolution, but that is not helping either.
David BirdPartnerAuthor Commented:
Sorry, created delegation record for www on DNS server.
Patrick BogersDatacenter platform engineer LindowsCommented:
Wait... in the forward lookup zone for mydomain.com in your local DNS, did you create a A-record called www which points to the external adress? (maybe stupid but need to ask for my understanding)

BTW: Split horizon DNS is your second headache, please undo it while you can.
David BirdPartnerAuthor Commented:
Yes, I put www as an A record pointing external. Removed the split as it would no longer resolve at all.  Just trying to be complete in things I have attempted. At this point, all I have in DNS is the A record pointing to external IP for WWW.  Nothing else in system at this point. Ping is resolving externally at www.domain.com, but browser is failing to load page.
Patrick BogersDatacenter platform engineer LindowsCommented:
Hmm this should be working.

Are you sure the A record is correct e.g. no trailing spaces?
On the DNS server itself can you browse to the URL?
Does the website has some kind off redirect in it and secondly, is the URL reachable from the outside?
Qlemo"Batchelor", Developer and EE Topic AdvisorCommented:
Sure the web site does not redirect www.mydomain.com to mydomain.com? That is the most probably cause for most folks.

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
David BirdPartnerAuthor Commented:
- yes DNS entry is correct and ping from cmd works properly.
- No, even from the DNS server, it fails.
- Probably.  That is my thought, the Web provider is taking the www and routing to route.
- Yes, from outside it is accessible.

Qlemo.  I am certain the issue is a redirect to the root. I have asked the ISP to NOT redirect but rather allow it to use www.  Will let you know their response.
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 2012

From novice to tech pro — start learning today.