[PLEASE LEARN TO TRIM YOUR REPLIES]
On Mon, Sep 01, 2003 at 06:48:18PM +0000, Shane Hollis wrote:
> > *NO*. Time to propogate is IRRELEVANT when you're talking about the server,
> > or location.
> Not quite ... if one person at a university of 10 000 people asks for a change
> then the Uni's DNs gets the IP and all people at the university have instant
> access to that IP. Yes?
Huh? lets clarify... what do you mean by 'change' ? If you instead mean
'query', or 'lookup', then yes.
> That negates incorrect caching and trouble for all 10 000 people.
um... "huh?"
> A big server
> in the states (Server A) regulalry gets hit by many other servers (Server B -
> Z) who serve lots of people. If the big server(A) is correct then it will
> give all those other servers (B-Z) correct info. They in turn only need one
> person to ask for the new IP address. This means that one person from each of
> those servers(B-Z) only needs ask and the correct info is available to all
> the people. The size of the server doesn't determine the look up speed but it
> does determine the number of users who now have access to the correct
> information.
Yes, that is how DNS is designed to work. but the best bit? that 'ServerA'
for a domain can be *ANYWHERE*.. doesnt have to be in the states. you just
need to have the connectivity required to sustain the domain you're
hosting... for example, you wouldnt host slashdot behind a Jetstart
connection. (or its DNS, for that matter... (well, you probably could, but
it'd be struggling))
> In an ideal world anybody who does a lookup will get to the correct site every
> time. In the real world there are stuff ups with caching and it doesn't
> happen.
OK.. you're now starting to make a little bit of sense. but, it's silly to
not do caching, or big popular sites' DNS servers would buckle under the
huge amount of queries everytime they're accessed.
the usage of TTL's and caching are a tradeoff for this.
> Having your IP registered in a big central server does several things.
Aha... now what you're talking about are 'glue' records stored on the
relevant TLD name servers, right?
> 1: - Quick return time for lokups as you are working on the backbone of the
> internet not a small byway.
There is no 'backbone' to the internet, there are several. it's a web, you
know that, right?
anyway, yes, it's beneficial to have a name server for a big site in a well
connected location, along with the relevant content server (web, nntp, etc).
> 2: - Less steps to return the lookup as you are closer to the places many
> people will use and so your cache or info is more up to date. (ie if most of
> my work is for say an american company then having the record in the USA
> means the servers that most need to know the info are closer to their home so
> less steps ( ie don't have to go to NZ and then a local ISP to find it).
It's a coupla hundred milliseconds, what's the big deal?
A query for an A record that is not cached is fetched directly, from any
server that takes care of it's own unknowns... now, this will 99% of the
time, be your ISP. they should not be forwarding. I, on the other hand, do,
(to my ISP), since my server only does lookups for me, which is no big deal.
It does not lookup for lots and lots of people, like an ISP server does.
> 3: - More people able to access the same lookup as there are more people using
> the same DNs server to look up the same address. Therefore less traffic on
> the net. To me it makes sense that if my domain is primariy used by USA
> people then register your domain record in the states. If it is used mostly
> by Taiwanese, register it in Taiwan.
Bzzzzzzzzzt. It *does* *not* *matter*. the DNS records are not served from
your registrar, only the glue record is, which is sent to a relevant root
server for the TLD... they're served from there, and that record tells the
world where to go for that domain. The records are served from *YOUR* DNS
server.
*YES* - if the domain is used in the states, has a lot of traffic, then by
all means, *YES* - serve it from the states.
> We are only talking a small matter of degree but I know trying to find some of
> those esoterric chinese hacker addresses has been a pain because it sometimes
> takes multiple goes before I can get a return on a dig or host lookup owing
> to the speed and stability of some of their networks.
Honestly, come on... they specifically 'damage' their implementation of DNS
to avoid being found... same as spammers... *sigh*
> Anyway, my head hurts a lot, I am going to bed.
So does mine, from banging my head against the wall trying to understand why
you're so obstinate about this..
This will be my last post on this thread.. and this is one time that I will
not feel afraid to say that I hope I *NEVER* do business with you...
I've had enough, I simply cannot be bothered trying to help you correct your
understanding. if this mail seems at all bitchy, it is probably, I'm
frustrated with your inability to listen.
Mike.
--
Mike Beattie <[EMAIL PROTECTED]> ZL4TXK, IRLP Node 6184
Never underestimate the power of very stupid people in large groups.
