Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

External DNS to web not resolving internally

Status
Not open for further replies.

CSEguy3

MIS
Jan 7, 2007
12
US
We've been having internet speed issues that I thought I had traced to DNS resolving with our ISP. I tried testing with some other root DNS servers, but it didn't help as much as I thought. For giggles I tried testing overall speed on our SBS2k3 box (main DC) and it goes like greased lightning compared to client PC's/laptops. Bandwidth isn't really a problem, I tested our DSL line and we're getting roughly 2.5-3MBps down/~400kbps up. Everyone's default gateway is the router with the primary DNS being the main DC. The only change we've made since our recent move is having a second building just down the road about 300 yards. That building is connected via T1 with a router on each end. Here in the main building, that T1 router is connected into the same switch as our servers and router/firewall device from Multitech. I don't think it's related to having our SR2024's daisy chanined through the gigabit ports instead of the fiber ports as I tried plugging myself into the same switch as the servers/router with no change in DNS resolution speed. Any ideas are much appreciated as I'm running out of them!
 
I'm trying to figure out if your question is in the subject line or in the post content. They seem to be two totally different issues.

Are you using a proxy server or ISA on the SBS box?

When you manually configure a client to use an external DNS server (the same one that the server has set up in its Forwarders tab) is the speed any different?

The speed issue probably isn't DNS, since the server is going to be caching queries and giving them to clients out of its cache, which is not a slow thing. And once the site IP is resolved, you should have quick page loads. Have you actually tried doing speed tests from the user desktops? Have you done a traceroute from the server to a remote host and then tried the same traceroute from a client to make sure that the first few hops are the same? Sounds like perhaps the clients are actually being routed out the T1 to the other office.

ShackDaddy
Shackelford Consulting
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top