Ben Leslie wrote:
On Thu Dec 07, 2006 at 16:52:21 +1100, O Plameras wrote:
Peter Hardy wrote:
O Plameras wrote:
The authority to associate NAME to ip address has to be propagated up
to the ROOT servers. You mean
to say that AARNET can do this without the express approval from the
owners of 203.7.132.1 ? NO, aarnet.edu.au cannot, otherwise it is
against
the rules and perhaps against the law.
The rest of my responses is implied by the above.
I'd strongly suggest you get hold of a good book on DNS, and find out
how it works before trying to explain it to anybody else. I found the
introductory chapters of "DNS and BIND" (
http://safari.oreilly.com/0596100574 ) to be most illuminating.
I have first, second, and third editions. I have the third edition in
front of me.
The book covers the technical process. Unfortunately, it does not cover
the bureaucratic
processes. The processes not covered by the book is the one that I am
revealing to you.
For example, technically aarnet.edu.au can propagate up to the ROOT
Servers.
Technically aarnet.edu.au doesn't need to propagate anything "up" to
the ROOT servers. That is not the way DNS works, rather the client
contacts the ROOT servers and then goes down from there (ignoring any
caching).
So really, aarnet.edu.au doesn't need to propagate anything at all.
Do you mean once aarnet.edu.au enters www.example.aarnet.edu.au IN A
203.7.132.1
it will be propagated ? This is wrong. aarnet.edu.au is only a branch in
the DNS trees.
What does aarnet.edu.au has to do to propagate ? If you can answer this
last question
correctly then we can proceed with the discussion.
O Plameras
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
