Hi Ben,
- The DNS UPDATE RFC redefines the question section as the zone section.
This means that the DNS server already doesn't extract the target zone
from the record name, but from the zone section. A relative record
should therefore be added to the zone mentioned in the zone section.
- The label indicator only can appear in the end, so
"selector._domainkey[relative-label-here]". The zone name has to be
known from context, but that is the case for DNS UPDATE (zone section)
and also for binary zone file (file name and file header).
This should be made explicit. Maybe the whole draft could be something
like "Relative Names for DNS UPDATE", and precisely define a mechanism
for this particular purpose, including the new label type.
- It is not about if a program can or cannot make a FQDN of something
relative. It is about the control of the user using that program to be
able to choose if a record is added with relative/absolute domain names.
Overall, IMHO, this is a UI issue in the panel you are using to manage
your zones, and not something that needs to be implemented in the DNS
itself. You can already have relative names in presentation format by
not including the trailing '.', and you can store zones in any format
you want. On the wire, this just does the job of a pointer in 1 less octet.
Alexander
_______________________________________________
DNSOP mailing list -- dnsop@ietf.org
To unsubscribe send an email to dnsop-le...@ietf.org
