At 23:40 11/03/2007 -0400, you wrote:
No, a "colo" is an abbreviated term for "co-location" which is a
datacenter that many companies and individuals rent space, power, and
sometimes bandwidth from.
I rent 1U's worth of space, 15a worth of power, and 10mb worth of internet
bandwidth from a company in Manhattan to host my server.
Yes, and I suppose Jim does same for the List. I am a bit embarrassed
too...because I forgot.. :)
Your idea of DNS replication is, for the most part, correct. They don't
spend much time keeping each other updated. There is a "primary" DNS and
(there should be at least) one or more "secondary" DNS servers. All
changes happen on the primary. When the primary is notified to reload the
zone file after the changes have been made, it will automatically send out
an update to the secondary servers.
I will never ask about a "zone file." NO. Do not explain it to me. If you
do, I know you will have to kill me. I don't want to die! Please? LOL!
When the secondary server gets the update, it looks at the "serial number"
of the zone. If the serial number is newer than the one it currently is
using, it will update itself. If it is not, it won't.
Damn, that's another level of control/complexity. But, there is a certain
symmetry to it. Okay. UWin! I do grasp this topic, but I remain such a
noob! LOL! Elegant how it all works. I never thought it would get this
complex back in 1975. Back then it was so much simpler......(the World was
smaller).... :)
DHSinclair wrote:
Got it! Really great answer. Can I believe that a "colo" is just a
duplicate machine
somewhere else physically that has a replicated database of the local
authoritative
DNS? I'll imagine that these two machines spend their time keeping each
other up
to date......and handle DNS calls from the clients of the network to
which they are
attached....
