ongoing issues.

Re: ongoing issues.

From:

Date:

Time:

At 11:05 AM -0400 4/14/00, Adam West wrote:
>> Aside from misspelling your domain (you left out an "e"), I can't
>> find where you've made any errors.
>
>Your right. bad typing on my part.
>
>> These records should not cause DNS Expert to claim you have duplicate
>> A records:
>> www.knowledgeexpress.com. A 209.49.229.30
>> www.knowledgeexpress.com. A 209.49.229.31
>>
>> After all, they're not duplicates; they differ in the address.
>
>Your right again. It actually says, "There is more than one A record with
>the name 'www.knowledgeexpress.com'."
>
>> One reason for occasional reports that your domain can't be found is
>> resolver speed - the potential visitor's resolver doesn't get a
>> response back to the web browser fast enough. Some operating systems
>> have a timeout period of 7 seconds. In that time, the resolver has to
>> locate the root servers, ask a root server, ask your servers,
>> evaluate the answer, and respond to the client.
>
>The web server I am using is a G4 450 w/ WebStar 4.2 on a T-1. You already
>know the DNS Macs, and the client I am using to test is a PB G3 w/ 56k
>running IE 5.0 (which might be some of the problem).
>
>> If the resolver isn't fast enough, this can cause a sporadic "name
>> doesn't exist" error. However, the resolver will continue resolving
>> the name, even after the time limit has been exceeded. If the client
>> tries again while the browser has the name in cache, the name will
>> already be known and an answer will be given back immediately.
>
>> Reasons the resolver might not find the name in time:
>
><snip..>
>
>> All of these factors can slow things down enough to exceed the time
>> limit. As a domain owner, you can really only control a few of these
>> factors. It is to your benefit to have your domain hosted on a
>> relatively large number of servers (more than 2), each of which is
>> connected to the net in a different place, via a different provider.
>> It is also of benefit to have your ISP (or your ISP's bandwidth
>> provider) host your domain.
>
>Assuming that for now I can't host DNS at multiple places, are there any
>QDNS or WebStar specific tricks that can help speed up my part of the
>resolving? Thanks for checking everything out and giving me some great
>info...

Yes, you can host your DNS data at multiple locations, through the
wonders of swapping. You can swap secondary service with others
across the Internet - you configure one of your servers (your
primary, per the license agreement for QDNS) to act as a secondary
for their domains, and they do the same for you.

There's even a mailing list for discussing such matters. To
subscribe, send a message to
<mailto:DNS-swap-on@lists.ironclad.net.au>. It's a very low traffic
list.

Once you've swapped DNS service with someone else, make sure to add
their server to your domain registration records with the various
domain registrars. You want their server to be listed alongside your
own in the root servers and/or TLD servers.

Aside from that, I don't know of any QuickDNS-specific tips. WebSTAR
doesn't enter into the equation until the domain has been resolved.
Some basic points to keep in mind:

o The faster your DNS server, the better, but this generally won't
make a great deal of difference.

o Make sure your bandwidth isn't maxed out. DNS packets don't take
much bandwidth, but they do need to get through quickly. If your
bandwidth is filled, your domains won't get resolved quickly because
the DNS messages will get stuck in a queue.
____________________________________________________________________
Chris Buxton cbuxton@menandmice.com
Men & Mice http://www.menandmice.com
Makers of: QuickDNS Pro

Sales:
888/4-DPOINT

Support:
858/452-3696