| Title: | DECmcc user notes file. Does not replace IPMT. |
| Notice: | Use IPMT for problems. Newsletter location in note 6187 |
| Moderator: | TAEC::BEROUD |
| Created: | Mon Aug 21 1989 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 6497 |
| Total number of notes: | 27359 |
Hi,
I new to DNS, but my customer will use DNS with DECmcc to manage their
network.
Refer to note 4693.1, does it mean DECmcc BMS V1.3 can ONLY talk to
DNS V1.1/V1.2/V1.3 server?
Second question: DNS Clerk comes with DECnet-VAX Ext where DNS version
is 5.2-000 (the image version DNS$ADVER.EXE), does it mean my DECmcc
workstation (running with DNS clerk/DNV-ext) can access to the DNS
server (V1.1/V1.2/V1.3) running in a VAXcluster connected to the same
Ethernet LAN?
Thanks in advance for help!
Andrew Chiu - NIS Sydney
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 5250.1 | TOOK::R_SPENCE | Nets don't fail me now... | Thu Jun 24 1993 16:18 | 8 | |
The DNS clerk that is supplied with VMS for DECnet Phase IV will
talk to an V1.x DNS Server.
The note you refer to (4693.1) is discussing autoconfig. Autoconfig
expects to be run on a system which is a decnet phase iv system
which therefore uses dns V1.x.
s/rob
| |||||
| 5250.2 | DNS V1.1 supported for DECmcc V1.0-V1.3 | CUJO::HILL | Dan Hill-Net.Mgt.-Customer Resident | Fri Jul 02 1993 02:11 | 49 |
Andrew,
Don't be confused by the DNS image versions when doing analyze/image.
There are only two versions of DECdns in use today. They are V1.1 and
V2.0.
DECdns V2.0 requires DECnet Phase V extensions. You can have a DECdns
V2.0 server node using V1.1 format of the repository, so, if you know
what you are doing, you could potentially have a V2.0 server and a V1.1
server in the same namespace. Unless you are a glutton for punishment,
I would recommend against it.
DECdns is not trivial. You must spend at least as much time learning
DNS as you would learning Polycenter Network Manager (DECmcc). There
are several notes in this conference that deal with DNS issues. I
advise you to check them out.
I also advise you to make a call to the support center and request a
DNS expert. Ask questions. Read manuals. Give up your personal life.
To quickly answer your questions:
The DNS client software comes with VMS. Simply include the
"@SYS$STARTUP:DNS$CLIENT_STARTUP.COM" command in your system startup
procedure on VMS after first executing the DNS$CHANGE_DEFAULT_FILE.COM
procedure to point to a DNS server node on the network.
You may have more than one DNS server in your namespace. The namespace
is composed of clearinghouses which reside on the server nodes (look in
SYS$SYSROOT:[DNS$SERVER] on the DNS server nodes. The *_CH.DNS files
are the clearinghouses. There is one clearinghouse per server.
Directories are in clearinghouses. Objects, groups, links, and other
directories are in directories.
You may reach any DNS server via the DECnet transport on a LAN or
extended LAN.
Be sure you use the MCC_DNS_SETUP.COM procedures to create directories
and backtranslation links, etc.
READ, READ, READ. PRAY, PRAY, PRAY.
Several weeks of cursing, rebuilding namespaces, re-installing DNS, and
populating namespaces with PNM entities will make you a guru. You will
be worshipped and some may even buy you lunch or name their children
after you.
-Dan
| |||||
| 5250.3 | DECdns and DECmcc 1.2 vs. 1.3 | TUXEDO::SMART | Fri Aug 20 1993 12:12 | 15 | |
I have a question regarding MCC 1.3's use of DECdns. A customer who
uses DECmcc and DECdns has been unable to access certain namepsaces
without control access. I have done a protocol trace and it appears
that MCC is attempting to do a modify on the DNS$ACS attribute (in
DECdns). Can someone who is knowledgeable about DECmcc verify whether
or not this is the case?
The customer did not experience this error using MCC 1.2, but is now
finding problems with DECdns and DECmcc 1.3
thanx
ryan
| |||||