| Yes, this is coming from DECNET_REGISTER
But the interesting thing is that it is another DECNET_REGISTER command
that results in the error. I try to produce it with a DNS$CONTROL command
without luck.
When there is a real error from DECdns, DECNET_REGISTER doesn't seem to
report it.
Now what I'm trying to diagnose is a problem where several of my nodes
are unable to resolve things thru DECdns. Here is a typical error from
DNS$CONTROL where I try to diagnose that on a different node (one that
the NIO DNS servers doesn't particularly like):
L$ mc dns$control sho obj .DNA_BackTranslation.%X49.%X0027.%XAA000400419E
SHOW
OBJECT DEC:.dna_backtranslation.%X49.%X0027.%XAA0
00400419E
AT 30-MAY-1997:21:05:04
DNA$NODESYNONYM =
DNA$Towers (set) = :
Tower 1 Floor 1 = 01 13 (null)
Tower 1 Floor 2 = 03 00 13
Tower 1 Floor 3 = 05 de c0
Tower 1 Floor 4 = 06 49 00 27 aa 00 04 00 41 9e 21
DNS$ACS =
DNS$Class =
DNS$ClassVersion = 1.0
DNS$CTS =
DNS$UTS = 1997-05-30-14:03:22.608139300/08-00-2b-24
-4b-b5
Error on entity: DEC:.dna_backtranslation.%X49.%X0027.%XAA000400419E
%DNS-E-CANNOTAUTHENTIC, Requesting principal could not be authenticated to the c
learinghouse
Error on entity: DEC:.dna_backtranslation.%X49.%X0027.%XAA000400419E
%DNS-E-CANNOTAUTHENTIC, Requesting principal could not be authenticated to the c
learinghouse
Error on entity: DEC:.dna_backtranslation.%X49.%X0027.%XAA000400419E
%DNS-E-CANNOTAUTHENTIC, Requesting principal could not be authenticated to the c
learinghouse
Error on entity: DEC:.dna_backtranslation.%X49.%X0027.%XAA000400419E
%DNS-E-CANNOTAUTHENTIC, Requesting principal could not be authenticated to the c
learinghouse
L$ mc dns$control sho obj .DNA_BackTranslation.%X49.%X0027.%XAA000400419E
SHOW
OBJECT DEC:.dna_backtranslation.%X49.%X0027.%XAA0
00400419E
AT 30-MAY-1997:21:05:49
DNA$NODESYNONYM =
DNA$Towers =
DNS$ACS (set) = :
Flags = none
Rights = read, write, delete, test, control
(IV) Principal = ESCDNS::DNRS_REG
(V) Principal = DEC:.DNS$IV.ESCDNS.DNRS_REG
DNS$ACS (set) = :
Flags = propagate, group
Rights = read, write, delete, test, control
Group = DEC:.name_czars
DNS$ACS (set) = :
Flags = propagate
Rights = read, test
(IV) Principal = *::*
(V) Principal = DEC:.DNS$IV.*.*
DNS$ACS (set) = :
Flags = propagate
Rights = read, write, delete, test, control
(IV) Principal = melmac::system
(V) Principal = DEC:.DNS$IV.melmac.system
DNS$ACS (set) = :
Flags = propagate
Rights = read, write, delete, test, control
(IV) Principal = shumwa::system
(V) Principal = DEC:.DNS$IV.shumwa.system
DNS$ACS (set) = :
Flags = propagate, group
Rights = read, write, delete, test, control
Group = DEC:.us.dns_admin
DNS$ACS (set) = :
Flags = propagate, group
Rights = read, write, delete, test, control
Group = DEC:.nio.dns_admin
DNS$ACS (set) = :
Flags = propagate, group
Rights = read, write, delete, test, control
Group = DEC:.DNRS_Registrar
DNS$ACS (set) = :
Flags = propagate, group
Rights = read, write, delete, test
Group = DEC:.nio.OBJ_ADMIN
DNS$ACS (set) = :
Flags = propagate
Rights = read, write, test, control
(IV) Principal = leder1::DNA$SessCtrl
(V) Principal = DEC:.DNS$IV.leder1.DNA$SessCtrl
DNS$ACS (set) = :
Flags = none
Rights = read, write, delete, test, control
(V) Principal = DEC:.NIO.LEDER1.DNA$SessCtrl
DNS$ACS (set) = :
Flags = none
Rights = read, write, delete, test, control
(V) Principal = DEC:.NIO.DNS$IV.leder1
DNS$ACS (set) = :
Flags = propagate
Rights = read, test
(V) Principal = DEC:.*...
DNS$Class =
DNS$ClassVersion = 1.0
DNS$CTS =
DNS$UTS =
Error on entity: DEC:.dna_backtranslation.%X49.%X0027.%XAA000400419E
%DNS-E-CANNOTAUTHENTIC, Requesting principal could not be authenticated to the c
learinghouse
Error on entity: DEC:.dna_backtranslation.%X49.%X0027.%XAA000400419E
%DNS-E-CANNOTAUTHENTIC, Requesting principal could not be authenticated to the c
learinghouse
Error on entity: DEC:.dna_backtranslation.%X49.%X0027.%XAA000400419E
%DNS-E-CANNOTAUTHENTIC, Requesting principal could not be authenticated to the c
learinghouse
Error on entity: DEC:.dna_backtranslation.%X49.%X0027.%XAA000400419E
%DNS-E-CANNOTAUTHENTIC, Requesting principal could not be authenticated to the c
learinghouse
Error on entity: DEC:.dna_backtranslation.%X49.%X0027.%XAA000400419E
%DNS-E-CANNOTAUTHENTIC, Requesting principal could not be authenticated to the c
learinghouse
L$ mc dns$control sho obj .DNA_BackTranslation.%X49.%X0027.%XAA000400419E
SHOW
OBJECT DEC:.dna_backtranslation.%X49.%X0027.%XAA0
00400419E
AT 30-MAY-1997:21:06:35
Error on entity: DEC:.dna_backtranslation.%X49.%X0027.%XAA000400419E
%DNS-E-CANNOTAUTHENTIC, Requesting principal could not be authenticated to the c
learinghouse
>>>>>>>> yes, the error varies from one minute to the next....
L$ mc decnet_register sho dir decdns node 39.577
Directory Service: DECdns
Node name: DEC:.nio.LEDER1
Accessed by link: .DNA_BackTranslation.%X49.%X0027.%XAA000400419E
Error - Node name lookup failure
.DNA_BackTranslation.%X49.%X0027.%XAA000400419E
%DNS-E-UNKNOWNENTRY, Requested name does not exist
DNA$NodeSynonym
%DNS-E-UNKNOWNENTRY, Requested name does not exist
DNA$Towers
Number of nodes reported on: 1
L$ mc dns$control sho obj .nio.leder1
SHOW
OBJECT DEC:.nio.leder1
AT 30-MAY-1997:21:14:17
Error on entity: DEC:.nio.leder1
%DNS-E-CANNOTAUTHENTIC, Requesting principal could not be authenticated to the c
learinghouse
L$ mc decnet_register sho dir decdns node .nio.leder1
Directory Service: DECdns
Error - Node name lookup failure
.NIO.LEDER1
Number of nodes reported on: 0
|
| You may want to go into this further in the DNS conference, or you may want to
raise this as a QAR, but here are some quick thoughts.
First, please consider the possibility that DECdns is telling you the exact
truth here. If you assume it's the truth and you get to a dead end, then it's
time to consider that someone may be lying or broken. I see no reason to believe
that these error messages are false or inconsistant.
Second, keep in mind that the .dna_backtranslation.api.area.id entries are all
links, not objects (try SHOW LINK before the SHOW OBJECT). When you use SHOW
OBJECT on a link, you are following the link and trying to show the object
pointed to by the link.
Third, you may be getting inconsistant results because of the number of DNS
servers involved, especially since you're getting CANNOTAUTHENTIC messages. Keep
in mind that there are two copies of DEC:.NIO, and two copies of
DEC:.DNA_BACKTRANSLATION.%X49.%X0027. I'm not sure, but I think that the SHOW
OBJECT command may be producing separate requests, one for each attribute. If
that's the case, then each request could be going to a different server. Perhaps
the attributes which show up as blank are the ones that went to the server that
you couldn't be authenticated to?
I would try to find out why the node you used couldn't be authenticated to one
of the servers (probably a backtranslation problem), and I'd also take a look at
LEDER1 from a node that the NIO servers like better. It looks OK to me from
DEC:.LKG.BULEAN.
Thanks,
John Saunders
DECdns Engineering
|
| John and Mulp,
In DNS$CONTROL there is a command that used to be documented but along the
way the help file got munged and it is still gone. Even after I submitted a
QAR on it to have it fixed!
You can tell DNS$CONTROL to use either Low, Medium, or High confidence. Low
only looks at the cache, Medium looks at the cache and may also try a server,
High insists on getting information from a server. You must issue the command
once for each DNS$CONTROL session. The default is medium. Here's how you do
it:
$ MCR DNS$CONTROL
DNS> show dnscp confidence
Confidence used is medium
DNS> set dnscp confidence=high
DNS> sho dnscp confidence
Confidence used is high
DNS>
I checked DECNET_REGISTER to see if there was a confidence setting available.
There isn't. Might it make sense to add it, if possible, to the preferences
choice if the user selects DECdns as the naming service to use?
John, maybe you could put the text back into help? I once gave Dave a copy of
a helpfile with the information. I guess he never got around to putting it
back in. I'm sure that I could dig it up again if you'd like.
Regards,
David
|