13,420
edits
Changes
no edit summary
# Make certain that you can login to your cloning source. The minimum commands required are: '''host''', '''dig''', '''netstat''', '''links'''.
# Do not install software on your cloning source: you are expected to install other software on your "cloned" VMs instead. For example, if you are required to install bind in a clone, install it in the clone as opposed to the "cloning source".
# Configure your network with a static configuration. See Refer to the table below for IP address and hostname.# Make sure certain that you have '''iptables ''' services enabled and running instead of ''Firewalld''. The default rules should suffice.# If you have created a regular user when you installed the machine - , delete that regular user. You'll (you are to use only have the root leftaccount).# Set up an SSH server on this machine"cloning source". Make sure that the root account is only allowed permitted to log in using key authentication. Other If user users are required to be created later, they should still be able permitted to log in with a their username/and password.# Generate a new key pair on your host Host Machine (don't delete the existing one), called : '''id_rsa_asg1'''# Make sure you can log in from your regular user on the host your Host Machine to root on the "cloning source" virtual machine using specifically that key.# Do not place the that newly-generated private key on the "cloning source" VM.
== ns1 ==
Clone the souce source to create a machine that will be your master DNS server on this network. See the table below for address and hostname.
Your DNS server must have all the records for the zone ops335a1.org listed in that table, including records for machines that don't exist yet. It's important to understand that DNS records live independently from the machines they are pointing to.