Penedo wrote:
On 07/12/06, O Plameras <[EMAIL PROTECTED]> 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.
What rules? What law?
There is nothing, technical or otherwise, preventing anyone with control
over a domain name server from putting any type of record under their
domain
which resolves to any value they like, it happens all the time openly
on the
net.
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.
You have all these books and still didn't get something I could
understand
from reading the RFC's as a young programmer fresh out of high school?
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.
The technical process is what matters here. "bind" isn't going to send
cops
to arrest you if it finds that you created an "A" record from your domain
which points to an IP address which isn't under your control and for that
matter, even if the cops DO come knocking at your door there is no law
according to which they can charge you of any wrongdoing. How do you
think
dyndns and no-ip.org work?
Another question - what would be the rational for a limitation such as
you
describe?
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.
A friend of mine created an A record for my static IP address (issued
to me
by my ISP) from his private domain. That name was (for the sake of this
discussion) xxx.bard.org.il. It still resolves to that (no longer
relevant)
IP address today and trace-routing to the "xxx.bard.org.il" will
correctly
reach some place which probably inherited my static IP address after I
left
that ISP.
REVERSE mapping won't work because the ISP is the only one with
control over
the .in-addr.arpa sub-domain for the network block assigned to it.
Maybe I
could ask them nicely to add another PTR record from that IP address
back to
xxx.bard.org.il but it's at their discretion to decide whether they
like the
colour of my eyes or the font on my fax and do it or not. No laws or IETF
rules involved here.
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.
It will get you everywhere. No need for any beaurocracy.
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.
And I edited zone files of a major university already back in 1991, so
what?
Things change. Maybe you want to refresh your memory. Just please give a
concrete pointer to substantiate your claims because so far it seems your
are outnumbered 2-1.
Because you don't understand that to be authoritative it involves
technical as
well as bureaucratice processes. You only know the technical aspect of it.
The technical aspect of the job is the easiest.
If everybody can be authoritative by doing what J Waugh had done there
will be chaos on the internet.
The whole point:
perkypants.org is not authoritative for plammered.perkypants.org.
I know how he does this.
But fortunately, perkypants.org cannot make a
commercial proposition out of these activities. If perkypants.org
makes money by using someone else public ip address without authority
this is stealing.
Again, just because you can, you do. Just as because you can
hack someones Server you do.
Plameras
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
