|
First let's make sure we are using the same terminology.
DNS primary and secondary identifiers say which identifiers are
to be used in the registration process; and YES the primary must
be a fullname.
The primary and secondary identifiers, as used by the parser specify
in what order the identifiers are to be checked for when parsing
the entity's identifier; this order is determined by the NAME=(<list>)
field in your .MS file. For the register and deregister to work
you have to make sure that your dns identifier is in the list of
all primary and secondary identifiers.
The reason these are different is because dns fullnames are VERY
robust and can be entered in so many forms that if listed as the
primary identifier for most entity classes it would always be found
as the match (ex: a simple name is a subset of a fullname, a phase
4 name looks just like a fullname, so do ethernet addresses).
Make sure to look at the input formats in chapter 9 of the SRM if
you don't know what their potential input formats are, and think
about which identifiers are your dns identifieres and what order
fo rthe entity class you use in defining you primary and secondary
identiers.
Maybe some one has less ambiguous terms for these but I hope you
understand the difference.
|