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. But
the bureaucratic process requires this has to be with the approval of
the owners of
the public ip address others this will not happen.
Anyway, can you explain how you do this ? The book on DNS and BIND will not
get you anywhere if that's all you will rely on.
I made my living (very good living) until I retire doing Domain Name and
IP address Administration back during
the days when munnari.oz was the authority for Australia until 2001. So,
I know what I'm
talking about if that's what you're asking.
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
