-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Registration Account wrote:
> I would be interested in others feeling/experience about the very slow
> resolution of browser enquiries of typical ISP - Particularly if you are
> in Australia.
> I ran some stats on my ISP's DNS servers ability to resolve enquiries -
> The stats were surprising in the number of re-try and Drops. My ISP is a
> real one and not a partition of bigpond or optusnet. This is
> particularly noticeable now my speed has increased to min 24000/1000kbps
> via a DSLAM link.
> For others it is interesting that Australia being so isolated; the
> amount of bandwidth available to get out of the country to the nearest
> major hub is limited and ultimate accessibility to TLD's requires an
> enormous amount of hops. A situation you don't every need to think about
> in North America or Europe.
> To illustrate our delima all you need to do is a traceroute on you ISP's
> DNS server(s) in .AU.
> To try to overcome the situation I have set-up my own DNS server - to
> make all my enquiries and rightly or wrongly I have added zones well up
> the TLD ladder - I'll probably get kicked off some of my zones but s far
> o.k (My first zone is a root server in Japan)
> Put simply the enquiry is
> Has anyone (particularly living in AU) noticed a slow response or
> incomplete resolution of DNS from their ISP.
> My apologies first and foremost for what appears to be a parochial
> issue. I hate being that way.
> Scott
> 

You do not normally need to explicitly define any external zones to
setup a cache-only DNS, all you need to define is your internal zones
and any external zones that you own and manage. A cache-only DNS should
speed up address resolution after an address has been initially
resolved. (As I understand it you would need to come to an arrangement
with the controller of the zones host server owners to host a copy of a
zone that people external to your environment can query).

DNS servers usually are organised hierarchically, and the way the query
is actually processed varies. A DNS server can be configured to resolve
the request itself if it does not know about a particular address, in
which case the requester will get an authoritative response and you will
see little of the resolution process, or it can be configured to
effectively to give a "I dont know but I know someone who might"
response, and the DNS server will respond with information on which
server to query for the address. Depending where you are in the domain
hierarchy in relation to your target this can involve a number of
redirections. This is normal.





-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iD8DBQFGUBNyasN0sSnLmgIRAv0DAJ48/T79xF2BSQGKbv8whxxkQ1uwkgCgr6rS
rzndJyvmvPx5fTOhMy2DF/E=
=e4pR
-----END PGP SIGNATURE-----
-- 
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to