[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: endpoint discovery from reverse DNS [Re: other comments on draft-nielsen-v6ops-3GPP-zeroconf-goals-00. txt
On Fri, 5 Nov 2004, Alain Durand wrote:
On Nov 5, 2004, at 12:33 PM, Pekka Savola wrote:
On Fri, 5 Nov 2004, Alain Durand wrote:
As to the attributes of the reverse lookup schemes, one might say a few
good / bad sides, like:
- bad side is that requires a lot of records
not an issue as they can be generated with script.
Still, doing so either requires that script be invented and (re-)written by
every DNS admin, or be distributed with DNS servers.
The script is probably very trivial, yes, but this is an ease-of-use
factor.
This is a bogus argument. Such a script already exist for generating
the PTR in the reverse zone. I wrote a very small ad-hoc perl script
(10 lines of code!) to do that, I can donate it to the community if
need be.
I was not arguing that such scripts would not exist, and many admins
would probably be qualified to write it pretty easily if they just
bothered to do that. The point is that the other admins don't know it
exists when they think of the problem they want to solve, and
discredit the solution as requiring manual insertion for the lack of
better tools.
- increases the number of required lookups
Not necessarily. Think CNAME and additional section.
CNAMEs in reverse tree? Granted. Hopefully no DNS servers would break
with such unanticipated usage.
No. I should have been more clear... When you are resolving a name
in the forward tree and there is a CNAME, you generally do not have
to do a second query to resolve the CNAME. As the server knows you
are more than likely to need that data anyway, it puts it in the
additional section.
Sure -- what I'm having difficulty understanding is why you're talking
about forward tree when the proposal was about reverse tree?
--
Pekka Savola "You each name yourselves king, yet the
Netcore Oy kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings