Can not resolve external websites from my LAN

All DNS experts:

I am experiencing an issue where I am unable to resolve external websites from my LAN.  We have internal DNS using Windows 2008 Servers and this functions correctly, however I think I something is not configured correctly so I am able to correctly resolve external websites.

We would be grateful to any suggestions or assistance.
rmessing171ConsultantAsked:
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.

Todd WedlakeSystems AdministratorCommented:
Is your DC facing the internet or do you have a firewall between your network and the internet?

from your DC can you get to www.google.com 
from your workstations, can you get to www.google.com


so what happens if you go to

http://www.google.com?

what happens when you go to

http://74.125.224.72/

if you cannot get to the first but can get to the 2nd, then you have a DNS issue internally.  DNS on your DC should be pointing to (or at least include) your internet provider's DNS servers (or at the very least google's DNS servers of 8.8.8.8 and 8.8.4.4).  That is unless you're using a firewall at which point you would want your DNS on servers that workstations authenticate into to point to the firewall and the firewall should be configured to use either google DNS or your internet providers's 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
DrDave242Commented:
Open the DNS console on your DC. Right-click the server's name in the left pane and select Properties. In the properties window, check the Forwarders and Root Hints tabs. The Forwarders tab will generally contain one or more public DNS servers, either your ISP's servers or well-known public servers like 8.8.8.8.

If that tab is empty, it's probably not a problem, as long as the Root Hints tab is correctly populated. It should look like this:
Root hints listThere should be entries for everything from a.root-servers.net through m.root-servers.net, and each one should have a unique public IPv4 address. (The ones you see in the screenshot should match the ones on your system.)

It may simplify things if you can post screenshots of both of those tabs here.
0
rmessing171ConsultantAuthor Commented:
It turns out we have Split DNS enabled with our company domain.  I needed to update the internal DNS split DNS for the Company's Domain and add an A Record with the sub-domain that I was unable to reach.

Thank you to all who assisted me with suggestions.
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.