DNS -> Getting to our website without having to use www.mydomain.com

Hi Everyone,

In my network when we type our domain name in the address bar of a web browser (ie - mydomain.com) it will not resolve our website. Instead it usually resolves to a google page or times out. Our website is hosted outside our network by a hosting company. Right now we can only get to our website by typing in www.mydomain.com. It seems so simple but I haven't found a fix for this and was wondering if anyone was willing to help.

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

MetMcCommented:
I'm not an expert on this but I do have a little experience.  It was over a year ago that I had to deal with an issue like this and if I remember correctly it had to do with the reverse DNS pointer record either not existing or not being valid.

See if this description sounds like the problem you're having:

http://www.simpledns.com/kb.aspx?kbid=1052

I am sure there are some very experienced people on here that explain how it all works.
MetMcCommented:
Just remembered what the problem was.  Our email was hosted by a company that by policy would not do reverse dns for its clients.  I ended up moving all of the dns info to our ISP because of that.
PapertripCommented:
2 things need to happen here.

1.  Create an A record for mydomain.com that points to the same IP as www.mydomain.com
2.  Contact your hosting company and ask them to configure your website to listen to requests for http://mydomain.com.

This is not a reverse DNS issue.
Defend Against the Q2 Top Security Threats

Were you aware that overall malware worldwide was down a surprising 42% from Q1'18? Every quarter, the WatchGuard Threat Lab releases an Internet Security Report that analyzes the top threat trends impacting companies worldwide. Learn more by viewing our on-demand webinar today!

DrDave242Senior Support EngineerCommented:
The above is correct, but there is one potential caveat: if your internal (AD) domain name is also mydomain.com, creating that blank host record in step 1 will cause problems.  If your internal domain is named something else (as it should be), you're in the clear.
WindhamSDAuthor Commented:
Thanks guys! Yea, unfortunately our internal and external domain are named the same... Is there any way out of this without changing it or should I tell my users to add the www?
DrDave242Senior Support EngineerCommented:
You'll be better off just telling the users to add the www prefix.  Blank host records in an AD domain are used to locate domain controllers, and you don't really want to go messing with that.  Users will still have problems accessing the website (since a DNS query for the domain name may return the IP of the website, or it may return the IP of one of your DCs), and you may find yourself with AD authentication and/or replication issues as well.

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
WindhamSDAuthor Commented:
Thanks guys!!
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.