Re: TCPIP Services on VMS (and Tru64)

denny wrote:
> My response was to run the "tcpip show name" command, and then package
> that output plus the help for "set name" and send it to him. All, of
> course, from my VMS system.


If the alpha is currently running the main DNS server, you should be
able to find the .db files in the bind directory somewhere in the file
system. They are in standard BIND format. Hopefully the micro***
software should be able to read those.

I think the same applies to DHCP. There should be text files in some
DHCP directory. But not sure how standard a format they are in.


You will need to find out how to disable DHCP service on the Tru64 node.
DHCP works on broadcasted requests, so if you leave the DHCP server
running, it will continue to offer some replies to requests and
"compete" against the microsoft server.

Once you've loaded the microsoft virus incubator with the BIND database,
you may wish to edit the UNIX bind database to respond with an
incorrect IP address for all entries. This way, you will likely
notice/catch any computer with a hardwired DNS server entry still
pointing to the Unix box and then tell their owners to point the DNS to
the Microsoft virus incubator machine.

Switching DNS server isn't something to be taken lightly.

Consider any domain names which may be defined on the internet to point
to that IP address. This will need to be updated to point to the
Microsoft virus incubator IP address. In the BIND directory, you will
find .db files for each domain for which this DNS server is
authoritative.
.

Quantcast