Internal Domain same as External Address, DNS Stripping headers

I did a bunch of searches on here with similar issues, but to no avail. The issue I am having is we have our company AD Domain name the same as our external website running on a Windows Server 2012. This is a new AD setup for our company, and the reason we decided to keep the name the same is because we will be implementing single sign on with Office 365 in the future. When our internal employees access our company website it will go to the website like normal, but it strips out all of the headers of the website. All the content is up to date, and no links are broken, just images and structures are all stripped out. I've verified all the entries and everything looks normal. DNS flushing and registering doesn't work. I've never encountered this issue before, so if anyone has any ideas that would be great. Let me know what information you need. Thanks!!
genysisitAsked:
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.

ktaczalaCommented:
in DNS, add a cname called www and point it to your external website ip address.
0
genysisitAuthor Commented:
An "A Record" Already exists for www that points to the ip address of the website. Can't add a cname with www if the "A Record" exists. Also the website is hosted outside of our network. This wasn't an issue, until they moved it to a hosted solution. Like I said everything works, but it strips everything. It's really strange.
0
Don S.Commented:
It sounds like parts of the website are being served by one or more subdomain at the hosted site.  Check to see if you maybe need more than just the www A record to get everything.
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
genysisitAuthor Commented:
So dons6718 I took into account what you said and I did need to add a bunch of subdomains that were not in there, but I started to look deeper into it, and I found out that I had the parent directory being forwarded to the same machine, and I already had the machine_name.domain.com already pointed to it's correct IP. Once I took those out everything started to work perfectly. Still doing some testing to make sure that will be fully successful before full deployment, but I appreciate you pointing me in the right direction
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.