Conference azur::mcc

    	First of all, there is a dns$analyze.exe program you might want
    to try (see note 490.3 in the NOTED::DNS notesfile for more info).

    	Also, are you sure you correctly reinstalled dns?  I made this
    mistake several times before I finally got it right.  Follow this
    procedure exactly (substituing <diskname> and <nodename>'s, etc. where
    appropriately marked) to reinstall dns.  Warning: this procedure will
    blow away your existing local namespace, so only do this if you don't
    care what's currently in there:

A.  Prior to [re]installing dns:

    1.	$ @sys$manager:dns$stop
    2.	$ @sys$manager:dns$client_stop
    3.	$ delete sys$system:dns$global.gbl;
    4.	$ delete sys$system:global_cache.gbl;
    5.	$ rename sys$system:dns$default_file.dat *_old.dat
    6.  $ delete <diskname>:[sys0.dns$server]ch_<nodename>.dns;
    7.  $ delete <diskname>:[sys0.dns$server]ch_<nodename>.gbl;

B.	Install dns making sure you have the latest dns V1.1 kit (apparently
    	there was a patched kit released sometime after the original V1.1):

    1.  $ @sys$update:vmsinstal dns <kit_location>

C.	DNS post-installation instructions:

    1.  $ @sys$manager:dns$startup
    2.  Add above to systartup_v5.com (if not already there).

    	...and that should fix your problem (fingers crossed).  It worked
    for us anyway.  Previously we had problems similar to yours which
    turnd out to be caused be multiple name servers running on the same
    system (one in sys$specific and one in sys$common).

				    -davo

note: check also notes #463.*, and #490.* in the NOTED::DNS notesfile.

    RE: .0
    
    When you specify the Namespace (tq_ns:) in the fullname in a node4
    registration command, for example,
        REGISTER NODE4 tq_ns:.dna_node.BISTRO SYNONYM=BISTRO
    
    the MCC V1.1 tries to create two backtranslation links (synonym and
    address backtranslation) in your system's DEFAULT DNS Namespace!!
                                                
    It looks like that the DNS Clerk on your system cannot communicate with
    the nameserver of the default namespace. Check your system's DNS default
    namespace, and see if you can access the namespace using DNS$Control
    program.
    

    William
    
    
    PS: The topic #652 includes many discussions on DNS default namespace.

    The namespace you use for DECmcc MUST be the Default namespace on the
    system (for now).
    
    s/rob

    re .1, .2, .3
    
    Thank you for your help. I had already checked and done the things
    you sugested. Namelly accessing DNS using the dns$control program,
    checking that the default name space was the correct one, making sure
    there were no multiple DNS's, deleting the files and re-installing DNS,
    etc...
    
    But because you sugested it, I went and deleted and re-installed DNS
    once again, as per Davo's sugestion in re .1, and it worked !!!!!!!!
    Third time lucky I guess. 
    
    Now lets hope it doesn't go bad once again, as it has done before. 
    If it does I will post it here.
    
    	Gil

re: .4,
    
>    But because you sugested it, I went and deleted and re-installed DNS
>    once again, as per Davo's sugestion in re .1, and it worked !!!!!!!!
>    Third time lucky I guess. 

    	That's what happened for me too.  I could have sworn I already
    did those things the first few times, but apparently dns is very
    particular about how it reinstalled and it must be done just right
    or else...

    				    -davo

p.s.	The real credit goes to William Kwak who originally supplied
    	me with hardcopy of the steps I outlined in #.1.