Search Again: Re: Problems resolving From: Men & Mice Support Date: Tuesday, October 26, 2004 Time: 2:52:52 pm 94 ms is not slow. If your server had sent these queries, the total lookup time would have been far less than a second. The browser doesn't time out for at least 5 seconds. If you saw noticeable delays while running the trace, it was probably from trying to get the server names looked up - while dig took care of the queries to the servers themselves, it relied on your local DNS server to look up their names (f.root-servers.net, c.gtld-servers.net, etc.). The problem you're describing, where browsers routinely time out on the first try, typically indicates a network performance problem. It can usually be solved by configuring your server to forward to a server provided by your ISP or NSP. This is done in the server options window. Chris Buxton Men & Mice - Making DNS Easy Customer Service and Sales Engineer At 3:43 PM -0500 10/26/04, Alan Ordway wrote: >I seem to be having problems with resolution. What is happening is >that when someone tries to go to a website that the dns has not >cached the ip for, the web browser ends up timing out with a can not >find server. However if the user tries again right away the page >loads fine. >If from the command line (OS X 10.3.5) I try a dig, I get immediate >results from our DNS but from the rest of the stream it is quit a >bit slower. Below is an example of digging google. >Do I have a DNS problem or is it a network problem? I don't know >what else to check > >aordway$ dig @ns.ihmc.us www.google.com +trace > >; <<>> DiG 9.2.2 <<>> @ns.ihmc.us www.google.com +trace >;; global options: printcmd >. 492808 IN NS F.ROOT-SERVERS.NET. >. 492808 IN NS G.ROOT-SERVERS.NET. >. 492808 IN NS H.ROOT-SERVERS.NET. >. 492808 IN NS I.ROOT-SERVERS.NET. >. 492808 IN NS J.ROOT-SERVERS.NET. >. 492808 IN NS K.ROOT-SERVERS.NET. >. 492808 IN NS L.ROOT-SERVERS.NET. >. 492808 IN NS M.ROOT-SERVERS.NET. >. 492808 IN NS A.ROOT-SERVERS.NET. >. 492808 IN NS B.ROOT-SERVERS.NET. >. 492808 IN NS C.ROOT-SERVERS.NET. >. 492808 IN NS D.ROOT-SERVERS.NET. >. 492808 IN NS E.ROOT-SERVERS.NET. >;; Received 356 bytes from 65.212.118.10#53(ns.ihmc.us) in 1 ms > >com. 172800 IN NS B.GTLD-SERVERS.NET. >com. 172800 IN NS C.GTLD-SERVERS.NET. >com. 172800 IN NS D.GTLD-SERVERS.NET. >com. 172800 IN NS E.GTLD-SERVERS.NET. >com. 172800 IN NS F.GTLD-SERVERS.NET. >com. 172800 IN NS G.GTLD-SERVERS.NET. >com. 172800 IN NS H.GTLD-SERVERS.NET. >com. 172800 IN NS I.GTLD-SERVERS.NET. >com. 172800 IN NS J.GTLD-SERVERS.NET. >com. 172800 IN NS K.GTLD-SERVERS.NET. >com. 172800 IN NS L.GTLD-SERVERS.NET. >com. 172800 IN NS M.GTLD-SERVERS.NET. >com. 172800 IN NS A.GTLD-SERVERS.NET. >;; Received 504 bytes from 192.5.5.241#53(F.ROOT-SERVERS.NET) in 94 ms > >google.com. 172800 IN NS ns1.google.com. >google.com. 172800 IN NS ns2.google.com. >google.com. 172800 IN NS ns3.google.com. >google.com. 172800 IN NS ns4.google.com. >;; Received 168 bytes from 192.26.92.30#53(C.GTLD-SERVERS.NET) in 55 ms > >www.google.com. 900 IN CNAME www.google.akadns.net. >. 3600000 IN NS A.ROOT-SERVERS.net. >. 3600000 IN NS B.ROOT-SERVERS.net. >. 3600000 IN NS C.ROOT-SERVERS.net. >. 3600000 IN NS D.ROOT-SERVERS.net. >. 3600000 IN NS E.ROOT-SERVERS.net. >. 3600000 IN NS F.ROOT-SERVERS.net. >. 3600000 IN NS G.ROOT-SERVERS.net. >. 3600000 IN NS H.ROOT-SERVERS.net. >. 3600000 IN NS I.ROOT-SERVERS.net. >. 3600000 IN NS J.ROOT-SERVERS.net. >. 3600000 IN NS K.ROOT-SERVERS.net. >. 3600000 IN NS L.ROOT-SERVERS.net. >. 3600000 IN NS M.ROOT-SERVERS.net. >;; Received 275 bytes from 216.239.32.10#53(ns1.google.com) in 87 ms > > >-- >Alan Ordway

Messages In This Thread: Problems resolving by Alan Ordway on Oct 26, 2004 at 1:49:53 pm Re: Problems resolving by Men & Mice Support on Oct 26, 2004 at 2:52:52 pm Re: Problems resolving by Alan Ordway on Oct 27, 2004 at 11:32:53 am