| 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 |
I have a few questions about setting up DNS to run with a DECmcc
development environment, and cooperating with DFS and DQS. I've looked
through this conference for a similar situation and haven't found one.
Our group will be working on access modules for bridges and wiring
concentrators. We want to be able to perform operations like register,
deregister, rename, and reset without disturbing the Easynet. So it
looks like we want to have a local DNS server to muck with.
Will this screw up anything with DFS or DQS? Our developers'
workstations use DNS to get to remote disks and queues in the building.
If we want to have our own DNS namespace for MCC development, how do we
get DNS to figure out where the DFS disks and queues are? Is there a
way to copy them into our namespace from the building's DNS server?
How do we keep them in sync with the building's nameserver?
Is there some memo I don't know about, something called "Installing DNS
if you're doing MCC development on the EasyNet" ? Is there anyone out
there who does MCC development while operating with DFS and DQS? Any
advice?
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 752.1 | Make explicit namespace references in startup files | TOOK::CAREY | Tue Feb 26 1991 12:47 | 22 | |
We do it all the time.
On my system (may or may not be representative, but it surely works)
I have set my default namespace to the private nameserver that is on my
system. This is where I muck around with MCC and check out our ability
to register and manage DECnet phase 4 stuff.
My DFS sources are all pointed to explicitly in the startup file, that
is as:
DEC:.ENG.NAC.NETS.USER... instead of:
.ENG.NAC.NETS.USER... to invoke it from the default namespace.
As far as I know, DQS just sets up the same. Point your default
namespace at your private "mucking around" namespace, and make explicit
references to the DEC: or other namespaces that you use for day to day
operation.
-Jim Carey
| |||||