Server name resolution

We have a development server that is hosting a website.

If we type in the ip address ex. http://11.11.11.111/site/index.php in a web browser it calls up the site everytime.

If we type in the server name and domain ex. http://server.domain.com/site/index.php in a web browser it calls up the site sometimes.

If we type in the server name only ex. http://server/site/index.php it seems to call up the site everytime as well.

Not a big issue but why doesn't it like to see the domain.com added sometimes?
LVL 8
sharkbot221984Asked:
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.

jar3817Commented:
Do you have external nameservers listed on your client that don't know about the domain.com domain?  Check "ipconfig /all" and see if any nameservers other than internal ones for your domain are listed.
0
sharkbot221984Author Commented:
Yes, every machine points to an internal dns first, then to at least 2 other external dns servers for our isp.  Some also use opendns, it varies greatly.
0
jar3817Commented:
I bet that is your problem. In an active directory environment (or really any environment) you really shouldn't have external nameservers listed. Even if your internal dns is listed first it doesn't really matter. I bet if you remove all but the internal dns on a test machine that site will work fine by FQDN every time.
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
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!

sharkbot221984Author Commented:
I stripped out the extra nameservers and the FQDN worked, then I added back in an external and it still works (for now).  I will keep testing to see when it fails again, then strip out the external again and see if that brings it back, but I think you hit the nail on the head.
0
sharkbot221984Author Commented:
It's still working for me, however not for others that I didn't remove the external name servers for, so I am sure it's solved.  

One more question though, why specifically shouldn't we use external namer servers?
0
Henrik JohanssonSystems engineerCommented:
The reason is as said that the clients failover/rotate to use the external DNS servers and try to ask the external server about an internal host/resource which the external DNS servers isn't aware of what to answer and don't know where to forward the unresolved query.

Never use external DNS servers for direct resolving on any internal client. Instead configure internal DNS server(s) to use forwarders to forward unresolved queries to the external servers.
0
sharkbot221984Author Commented:
Thanks, I think I will quietly switch all internal machines to point only to the DNS server and then double check that that server has external servers to forward onto.
0
jar3817Commented:
Assuming you're using dhcp, just get rid of those servers from the scope and when the clients renew their lease they'll have the correct servers.
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
Windows Server 2003

From novice to tech pro — start learning today.