Hello Don
On 03-Mar-01, you wrote:
There is a built in DNS cache in MiamiDx, but no option to set the size.
All you can do is enable or disable it. There is also an option to have
separate caches for forward and reverse DNS resolution.
Check out the Database/SysCtl/dns.cache.size option in
What is BIND - is it part of Voyager, or part of the ISP`s or web host's
software?
Bind is the most commonly found implemenation of the domain name service
on the internet. Most of the time you use the one of your provider.
It's the server that is in charge to find for you which IP
On 02-Mar-01, Matt Sealey wrote:
BIND is the name server software that sit on your ISP's DNS servers.
While regarded as the definitive nameserving solution, it's got some
really annoying niggles.
What makes it worse is that these niggles are now an accepted part of
DNS, so if you think
On 02-Mar-01, Uffe Holst wrote:
But some weeks ago I noticed that Voyager quite often had difficulties
looking up domain names. Some asked me what DNS I used and it turned
out to most probably to be one of Deutche Telecom's DNS servers. I
changed this to the DNS my ISP recommends and then
On 02-Mar-01, Ken Shillito wrote:
David Gerber wrote (in a response to Don Cox):
(snip)
This is because of the BIND disease. It takes a query, checks if it's
in
the
cache. If it isn't it drops it, starts a background sysquery and
expects
to
have it in the cache the next time the
On 2 Mar 2001 21:42:09 +, Ian Greenway wrote:
I often wondered why that strangely inconsistent error message kept
appearing. Would it be possible for V to work round this in some way,
like to retry the DNS request a configurable number of times before
fail?
This is not the job of the
On Thu, 01 Mar 2001 21:18:24 +, Don Cox wrote:
Question: How does NetInfo find the IP address if Voyager cannot?
TCP stack is MiamiDx, OS is AmigaOS 3.9
The problem is the same on 2 different ISPs.
This is because of the BIND disease. It takes a query, checks if it's in the
cache. If
