|
|
 |  |
Re: Slow DNS problemsFrom: Men & Mice Support Date: Tuesday, September 5, 2000
Time: 11:48:16 amAt 1:18 PM -0500 9/4/00, Dennis J. Bonsall, Jr. wrote:
>> What else is running on the DNS servers, if anything?
>>
>
>The only thing running on the DNS servers is QDNS itself.
>
>> How fast is your net connection?
>
>I have a 2Mbps connection. However, the machines that seem to be
>the most adversly
>affected are the two web servers, and they are connected via a
>10Mbps connection
>(the local network) to the DNS servers.
>
>> Have you made any changes to the root server lists in your server prefs?
>
>I have not.
So your network connection should be plenty fast enough to do your
own resolving, rather than forwarding queries to your provider's
servers. Roughly how much of that bandwidth is available at any given
time? If other queries work OK, then the answer is probably, "a
sufficient amount".
Your reverse zone is handled by your ISP, I see. So your main server
needs to resolve your web server's reverse lookup request through the
standard recursive routine. This is obviously not working.
I noticed some irregularities in the setup of the reverse zone.
Specifically, in the delegation and authority records.
from f.root-servers.net:
238.63.in-addr.arpa. NS ns1.qwest.net.
238.63.in-addr.arpa. NS ns2.qwest.net.
ns1.qwest.net. A 216.111.65.217
ns2.qwest.net. A 205.171.16.250
from ns1.qwest.net:
152.238.63.in-addr.arpa. NS dns.ibsway.com.
152.238.63.in-addr.arpa. NS dns2.ibsway.com.
(no A records given)
from f.root-servers.net:
ibsway.com. NS ns.ibsway.com.
ibsway.com. NS ns2.ibsway.com.
ns.ibsway.com. A 63.238.152.2
ns2.ibsway.com. A 63.238.152.5
from ns.ibsway.com:
** dns.ibsway.com. CNAME ns.ibsway.com.
ns.ibsway.com. A 63.238.152.2
ibsway.com. NS top.net.
ibsway.com. NS dns2.top.net.
top.net. A 63.238.152.2
dns2.top.net. A 207.239.216.2
201.152.238.63.in-addr.arpa. PTR www1.webbuilders.com.
152.238.63.in-addr.arpa. NS res3.ns.digex.net.
152.238.63.in-addr.arpa. NS res1.ns.digex.net.
152.238.63.in-addr.arpa. NS top.net.
152.238.63.in-addr.arpa. NS news.top.net.
res3.ns.digex.net. A 165.117.128.5
res1.ns.digex.net. A 206.205.242.132
top.net. A 63.238.152.2
Note the record marked with "**". That may be what's tripping up
QuickDNS. Everything before that is perfectly kosher. Pretty much
everything after that is screwy and sloppy, but workable.
____________________________________________________________________
Chris Buxton Men & Mice
cbuxton@menandmice.com We Make DNS Easy!
|

Return to Digital Point Solutions' Home Page |