1. Identify the Pool ID of the Satellite Infrastructure subscription:

   # subscription-manager list --all --available --matches 'Red Hat Satellite Infrastructure Subscription'

   The command displays output similar to the following:

   Subscription Name:   Red Hat Satellite Infrastructure Subscription
   Provides:            Red Hat Satellite
                         Red Hat Software Collections (for RHEL Server)
                         Red Hat CodeReady Linux Builder for x86_64
                         Red Hat Ansible Engine
                         Red Hat Enterprise Linux Load Balancer (for RHEL Server)
                         Red Hat
                         Red Hat Software Collections (for RHEL Server)
                         Red Hat Enterprise Linux Server
                         Red Hat Satellite Capsule
                         Red Hat Enterprise Linux for x86_64
                         Red Hat Enterprise Linux High Availability for x86_64
                         Red Hat Satellite
                         Red Hat Satellite 5 Managed DB
                         Red Hat Satellite 6
                         Red Hat Discovery
   SKU:                 MCT3719
   Contract:            11878983
   Pool ID:             8a85f99968b92c3701694ee998cf03b8
   Provides Management: No
   Available:           1
   Suggested:           1
   Service Level:       Premium
   Service Type:        L1-L3
   Subscription Type:   Standard
   Ends:                03/04/2020
   System Type:         Physical

2. Make a note of the subscription Pool ID. Your subscription Pool ID is different from the example provided.

3. Attach the Satellite Infrastructure subscription to the base system that your Satellite Server is running on:

   # subscription-manager attach --pool=pool_id

   The command displays output similar to the following:

   Successfully attached a subscription for: Red Hat Satellite Infrastructure Subscription

4. Optional: Verify that the Satellite Infrastructure subscription is attached:

   # subscription-manager list --consumed

1. Disable all repositories:

   # subscription-manager repos --disable "*"

2. Enable the following repositories:

   # subscription-manager repos --enable=rhel-7-server-rpms \
   --enable=rhel-7-server-satellite-6.6-rpms \
   --enable=rhel-7-server-satellite-maintenance-6-rpms \
   --enable=rhel-server-rhscl-7-rpms \
   --enable=rhel-7-server-ansible-2.8-rpms

   Note

   If you are installing Satellite Server as a virtual machine hosted on Red Hat Virtualization (RHV), you must also enable the Red Hat Common repository, and install RHV guest agents and drivers. For more information, see Installing the Guest Agents and Drivers on Red Hat Enterprise Linux in the Virtual Machine Management Guide for more information.

3. Clear any yum metadata:

   # yum clean all

4. Optional: Verify that the required repositories are enabled:

   # yum repolist enabled

1. Update all packages:

   # yum update

2. Install the Satellite Server packages:

   # yum install satellite

1. Install the chrony package:

   # yum install chrony

2. Start and enable the chronyd service:

   # systemctl start chronyd
   # systemctl enable chronyd

1. Open https://access.redhat.com/ in your browser and log in to the Red Hat account that you used to register the system to Red Hat Subscription Management.
2. Navigate to Subscriptions in the upper-left corner of the Customer Portal.
3. Navigate to Subscription Allocations.
4. Click Create New subscription allocation.
5. In the Name field, enter a name.
6. From the Type list, select the type and version that corresponds to your Satellite Server.
7. Click Create.

1. Open https://access.redhat.com/ in your browser and log in to the Red Hat account that you used to register the system to Red Hat Subscription Management.
2. Navigate to Subscriptions in the upper-left corner of the Customer Portal.
3. Navigate to Subscription Allocations.
4. Click the allocation that you want to update.
5. Click the Subscriptions tab.
6. Click Add Subscriptions.
7. A list of your Red Hat product subscriptions appears. Enter the Entitlement Quantity for each product.
8. Click Submit to complete the assignment.

For Web UI Users

1. Ensure the context is set to the organization you want to use.
2. Navigate to Content > Subscriptions.
3. Click Manage Manifest to display the manifest page for the organization.
4. Click Choose file, select the Subscription Manifest, then click Upload.
5. Click Choose file and select the manifest archive in a .zip format that you have exported from the Customer Portal.

1. To store all the source certificate files, create a directory that is accessible only to the root user.

   # mkdir /root/satellite_cert

2. Create a private key with which to sign the Certificate Signing Request (CSR).

   Note that the private key must be unencrypted. If you use a password-protected private key, remove the private key password.

   If you already have a private key for this Satellite Server, skip this step.

   # openssl genrsa -out /root/satellite_cert/satellite_cert_key.pem 4096

3. Create the /root/satellite_cert/openssl.cnf configuration file for the Certificate Signing Request (CSR) and include the following content:

   [ req ]
   req_extensions = v3_req
   distinguished_name = req_distinguished_name
   x509_extensions = usr_cert
   prompt = no
   
   [ req_distinguished_name ] 1
   C  = Country Name (2 letter code)
   ST = State or Province Name (full name)
   L  = Locality Name (eg, city)
   O  = Organization Name (eg, company)
   OU = The division of your organization handling the certificate
   CN = satellite.example.com 2
   
   [ v3_req ]
   basicConstraints = CA:FALSE
   keyUsage = digitalSignature, nonRepudiation, keyEncipherment, dataEncipherment
   extendedKeyUsage = serverAuth, clientAuth, codeSigning, emailProtection
   subjectAltName = @alt_names
   
   [ usr_cert ]
   basicConstraints=CA:FALSE
   nsCertType = client, server, email
   keyUsage = nonRepudiation, digitalSignature, keyEncipherment
   extendedKeyUsage = serverAuth, clientAuth, codeSigning, emailProtection
   nsComment = "OpenSSL Generated Certificate"
   subjectKeyIdentifier=hash
   authorityKeyIdentifier=keyid,issuer
   
   [ alt_names ]
   DNS.1 = satellite.example.com 3

   1

   In the [ req_distinguished_name ] section, enter information about your organization.

   2

   Set the certificate’s Common Name CN to match the fully qualified domain name (FQDN) of your Satellite Server. To confirm a FQDN, on that Satellite Server, enter the hostname -f command. This is required to ensure that the katello-certs-check command validates the certificate correctly.

   3

   Set the Subject Alternative Name (SAN) DNS.1 to match the fully qualified domain name (FQDN) of your server.

4. Generate the Certificate Signing Request (CSR):

   # openssl req -new \
   -key /root/satellite_cert/satellite_cert_key.pem \ 1
   -config /root/satellite_cert/openssl.cnf \ 2
   -out /root/satellite_cert/satellite_cert_csr.pem 3

   1

   Path to the private key.

   2

   Path to the configuration file.

   3

   Path to the CSR to generate.

5. Send the certificate signing request to the Certificate Authority. The same Certificate Authority must sign certificates for Satellite Server and Capsule Server.

   When you submit the request, specify the lifespan of the certificate. The method for sending the certificate request varies, so consult the Certificate Authority for the preferred method. In response to the request, you can expect to receive a Certificate Authority bundle and a signed certificate, in separate files.

1. Validate the custom SSL certificate input files. Note that for the katello-certs-check command to work correctly, Common Name (CN) in the certificate must match the FQDN of Satellite Server.

   # katello-certs-check \
   -c /root/satellite_cert/satellite_cert.pem \      1
   -k /root/satellite_cert/satellite_cert_key.pem \  2
   -b /root/satellite_cert/ca_cert_bundle.pem        3

   1

   Path to the Satellite Server certificate file that is signed by a Certificate Authority.

   2

   Path to the private key that was used to sign the Capsule Server certificate.

   3

   Path to the Certificate Authority bundle.

   If the command is successful, it returns two satellite-installer commands, one of which you must use to deploy a certificate to Satellite Server.

   Example output of katello-certs-check

   Validation succeeded.
   
   To install the Red Hat Satellite Server with the custom certificates, run:
   
     satellite-installer --scenario satellite \
       --certs-server-cert "/root/satellite_cert/satellite_cert.pem" \
       --certs-server-key "/root/satellite_cert/satellite_cert_key.pem" \
       --certs-server-ca-cert "/root/satellite_cert/ca_cert_bundle.pem"
   
   To update the certificates on a currently running Red Hat Satellite installation, run:
   
     satellite-installer --scenario satellite \
       --certs-server-cert "/root/satellite_cert/satellite_cert.pem" \
       --certs-server-key "/root/satellite_cert/satellite_cert_key.pem" \
       --certs-server-ca-cert "/root/satellite_cert/ca_cert_bundle.pem" \
       --certs-update-server --certs-update-server-ca

2. From the output of the katello-certs-check command, depending on your requirements, enter the satellite-installer command that deploys a certificate to a new Satellite or updates a certificate on a currently running Satellite.

   Important

   Do not delete the certificate archive file after you deploy the certificate. It is required, for example, when upgrading Satellite Server.

3. On a computer with network access to Satellite Server, navigate to the following URL: https://satellite.example.com.
4. In your browser, view the certificate details to verify the deployed certificate.

1. Delete the current katello-ca-consumer package on the host:

   # yum remove 'katello-ca-consumer*'

2. Install the katello-ca-consumer package on the host:

   # yum localinstall \
   http://satellite.example.com/pub/katello-ca-consumer-latest.noarch.rpm

1. Use Section 1.2, “Storage Requirements and Guidelines” to plan the storage requirements for your external databases
2. Prepare PostgreSQL with databases for Foreman and Candlepin and dedicated users owning them
3. Prepare MongoDB with user pulp owning the pulp_database
4. Follow the initial steps to install Satellite and ensure that the databases are accessible from Satellite
5. Edit the parameters of satellite-installer to point to the new databases, and run satellite-installer

1. Use the instructions in Attaching the Satellite Infrastructure Subscription to attach a Satellite subscription to your server.

2. To install MongoDB and PostgreSQL servers on Red Hat Enterprise Linux Server 7, you must disable all repositories and enable only the following repositories:

   # subscription-manager repos --disable '*'
   # subscription-manager repos --enable=rhel-server-rhscl-7-rpms \
   --enable=rhel-7-server-rpms

1. To install MongoDB, enter the following command:

   # yum install rh-mongodb34 rh-mongodb34-syspaths

2. Start and enable the rh-mongodb34 service:

   # systemctl start rh-mongodb34-mongod
   # systemctl enable rh-mongodb34-mongod

3. Create a Pulp user on MongoDB for database pulp_database:

   # mongo pulp_database \
   --eval "db.createUser({user:'pulp',pwd:'pulp_password',roles:[{role:'dbOwner', db:'pulp_database'},{ role: 'readWrite', db: 'pulp_database'}]})"

4. In the /etc/opt/rh/rh-mongodb34/mongod.conf file, specify the bind IP:

   bindIp: your_mongodb_server_bind_IP,::1

5. Edit the /etc/opt/rh/rh-mongodb34/mongod.conf file to enable authentication in the security section:

   security:
     authorization: enabled

6. Restart the rh-mongodb34-mongod service:

   # systemctl restart rh-mongodb34-mongod

7. Open port 27017 for MongoDB:

   # firewall-cmd --add-port=27017/tcp
   # firewall-cmd --runtime-to-permanent

8. From Satellite Server, test that you can access the database. If the connection succeeds, the command returns 1.

   # scl enable rh-mongodb34 " mongo --host mongo.example.com \
   -u pulp -p pulp_password --port 27017 --eval 'ping:1' pulp_database"

1. To install PostgreSQL, enter the following command:

   # yum install postgresql-server

2. To initialize, start, and enable PostgreSQL service, enter the following commands:

   # postgresql-setup initdb
   # systemctl start postgresql
   # systemctl enable postgresql

3. Edit the /var/lib/pgsql/data/postgresql.conf file:

   # vi /var/lib/pgsql/data/postgresql.conf

4. Remove the # and edit to listen to inbound connections:

   listen_addresses = '*'

5. Edit the /var/lib/pgsql/data/pg_hba.conf file:

   # vi /var/lib/pgsql/data/pg_hba.conf

6. Add the following line to the file:

     host  all   all   satellite_server_ip/24   md5

7. Restart PostgreSQL service to update with the changes:

   # systemctl restart postgresql

8. Open the postgresql port on the external PostgreSQL server:

   # firewall-cmd --add-service=postgresql
   # firewall-cmd --runtime-to-permanent

9. Switch to the postgres user and start the PostgreSQL client:

   $ su - postgres -c psql

10. Create two databases and dedicated roles, one for Satellite and one for Candlepin:

    CREATE USER "foreman" WITH PASSWORD 'Foreman_Password';
    CREATE USER "candlepin" WITH PASSWORD 'Candlepin_Password';
    CREATE DATABASE foreman OWNER foreman;
    CREATE DATABASE candlepin OWNER candlepin;

11. Exit the postgres user:

    # \q

12. From Satellite Server, test that you can access the database. If the connection succeeds, the commands return 1.

    # PGPASSWORD='Foreman_Password' psql -h postgres.example.com  -p 5432 -U foreman -d foreman -c "SELECT 1 as ping"
    # PGPASSWORD='Candlepin_Password' psql -h postgres.example.com -p 5432 -U candlepin -d candlepin -c "SELECT 1 as ping"

13. To install and configure the remote database for Satellite, enter the following command:

    satellite-installer --scenario satellite \
      --foreman-db-host postgres.example.com \
      --foreman-db-password Foreman_Password \
      --foreman-db-database foreman \
      --katello-candlepin-db-host postgres.example.com \
      --katello-candlepin-db-name candlepin \
      --katello-candlepin-db-password Candlepin_Password \
      --katello-candlepin-manage-db false \
      --katello-pulp-db-username pulp \
      --katello-pulp-db-password pulp_password \
      --katello-pulp-db-seeds mongo.example.com:27017 \
      --katello-pulp-db-name pulp_database

1. On a Red Hat Enterprise Linux Server server, install the ISC DHCP Service and Berkeley Internet Name Domain (BIND) packages:

   # yum install dhcp bind

2. Generate a security token:

   # dnssec-keygen -a HMAC-MD5 -b 512 -n HOST omapi_key

   As a result, a key pair that consists of two files is created in the current directory.

3. Copy the secret hash from the key:

   # cat Komapi_key.+*.private |grep ^Key|cut -d ' ' -f2

4. Edit the dhcpd configuration file for all of the subnets and add the key. The following is an example:

   # cat /etc/dhcp/dhcpd.conf
   default-lease-time 604800;
   max-lease-time 2592000;
   log-facility local7;
   
   subnet 192.168.38.0 netmask 255.255.255.0 {
   	range 192.168.38.10 192.168.38.100;
   	option routers 192.168.38.1;
   	option subnet-mask 255.255.255.0;
   	option domain-search "virtual.lan";
   	option domain-name "virtual.lan";
   	option domain-name-servers 8.8.8.8;
   }
   
   omapi-port 7911;
   key omapi_key {
   	algorithm HMAC-MD5;
   	secret "jNSE5YI3H1A8Oj/tkV4...A2ZOHb6zv315CkNAY7DMYYCj48Umw==";
   };
   omapi-key omapi_key;

   Note that the option routers value is the Satellite or Capsule IP address that you want to use with an external DHCP service.

5. Delete the two key files from the directory that they were created in.

6. On Satellite Server, define each subnet. Do not set DHCP Capsule for the defined Subnet yet.

   To prevent conflicts, set up the lease and reservation ranges separately. For example, if the lease range is 192.168.38.10 to 192.168.38.100, in the Satellite web UI define the reservation range as 192.168.38.101 to 192.168.38.250.

7. Configure the firewall for external access to the DHCP server:

   # firewall-cmd --add-service dhcp \
   && firewall-cmd --runtime-to-permanent

8. On Satellite Server, determine the UID and GID of the foreman user:

   # id -u foreman
   993
   # id -g foreman
   990

9. On the DHCP server, create the foreman user and group with the same IDs as determined in a previous step:

   # groupadd -g 990 foreman
   # useradd -u 993 -g 990 -s /sbin/nologin foreman

10. To ensure that the configuration files are accessible, restore the read and execute flags:

    # chmod o+rx /etc/dhcp/
    # chmod o+r /etc/dhcp/dhcpd.conf
    # chattr +i /etc/dhcp/ /etc/dhcp/dhcpd.conf

11. Start the DHCP service:

    # systemctl start dhcpd

12. Export the DHCP configuration and lease files using NFS:

    # yum install nfs-utils
    # systemctl enable rpcbind nfs-server
    # systemctl start rpcbind nfs-server nfs-lock nfs-idmapd

13. Create directories for the DHCP configuration and lease files that you want to export using NFS:

    # mkdir -p /exports/var/lib/dhcpd /exports/etc/dhcp

14. To create mount points for the created directories, add the following line to the /etc/fstab file:

    /var/lib/dhcpd /exports/var/lib/dhcpd none bind,auto 0 0
    /etc/dhcp /exports/etc/dhcp none bind,auto 0 0

15. Mount the file systems in /etc/fstab:

    # mount -a

16. Ensure the following lines are present in /etc/exports:

    /exports 192.168.38.1(rw,async,no_root_squash,fsid=0,no_subtree_check)
    
    /exports/etc/dhcp 192.168.38.1(ro,async,no_root_squash,no_subtree_check,nohide)
    
    /exports/var/lib/dhcpd 192.168.38.1(ro,async,no_root_squash,no_subtree_check,nohide)

    Note that the IP address that you enter is the Satellite or Capsule IP address that you want to use with an external DHCP service.

17. Reload the NFS server:

    # exportfs -rva

18. Configure the firewall for the DHCP omapi port 7911:

    # firewall-cmd --add-port="7911/tcp" \
    && firewall-cmd --runtime-to-permanent

19. Optional: Configure the firewall for external access to NFS.

    Clients are configured using NFSv3.

    • Use the firewalld NFS service to configure the firewall:

      # firewall-cmd --zone public --add-service mountd \
      && firewall-cmd --zone public --add-service rpc-bind \
      && firewall-cmd --zone public --add-service nfs \
      && firewall-cmd --runtime-to-permanent

1. Install the nfs-utils utility:

   # yum install nfs-utils

2. Create the DHCP directories for NFS:

   # mkdir -p /mnt/nfs/etc/dhcp /mnt/nfs/var/lib/dhcpd

3. Change the file owner:

   # chown -R foreman-proxy /mnt/nfs

4. Verify communication with the NFS server and the Remote Procedure Call (RPC) communication paths:

   # showmount -e DHCP_Server_FQDN
   # rpcinfo -p DHCP_Server_FQDN

5. Add the following lines to the /etc/fstab file:

   DHCP_Server_FQDN:/exports/etc/dhcp /mnt/nfs/etc/dhcp nfs
   ro,vers=3,auto,nosharecache,context="system_u:object_r:dhcp_etc_t:s0" 0 0
   
   DHCP_Server_FQDN:/exports/var/lib/dhcpd /mnt/nfs/var/lib/dhcpd nfs
   ro,vers=3,auto,nosharecache,context="system_u:object_r:dhcpd_state_t:s0" 0 0

6. Mount the file systems on /etc/fstab:

   # mount -a

7. To verify that the foreman-proxy user can access the files that are shared over the network, display the DHCP configuration and lease files:

   # su foreman-proxy -s /bin/bash
   bash-4.2$ cat /mnt/nfs/etc/dhcp/dhcpd.conf
   bash-4.2$ cat /mnt/nfs/var/lib/dhcpd/dhcpd.leases
   bash-4.2$ exit

8. Enter the satellite-installer command to make the following persistent changes to the /etc/foreman-proxy/settings.d/dhcp.yml file:

   # satellite-installer --foreman-proxy-dhcp=true \
   --foreman-proxy-dhcp-provider=remote_isc \
   --foreman-proxy-plugin-dhcp-remote-isc-dhcp-config /mnt/nfs/etc/dhcp/dhcpd.conf \
   --foreman-proxy-plugin-dhcp-remote-isc-dhcp-leases /mnt/nfs/var/lib/dhcpd/dhcpd.leases \
   --foreman-proxy-plugin-dhcp-remote-isc-key-name=omapi_key \
   --foreman-proxy-plugin-dhcp-remote-isc-key-secret=jNSE5YI3H1A8Oj/tkV4...A2ZOHb6zv315CkNAY7DMYYCj48Umw== \
   --foreman-proxy-plugin-dhcp-remote-isc-omapi-port=7911 \
   --enable-foreman-proxy-plugin-dhcp-remote-isc \
   --foreman-proxy-dhcp-server=DHCP_Server_FQDN

9. Restart the foreman-proxy service:

   # systemctl restart foreman-proxy

10. Log in to the Satellite Server web UI.
11. Navigate to Infrastructure > Capsules. Locate the Capsule Server that you want to configure with external DHCP, and from the list in the Actions column, select Refresh.
12. Associate the DHCP service with the appropriate subnets and domain.

1. Configure the firewall (UDP on port 69).

   # firewall-cmd --add-port="69/udp" \
   && firewall-cmd --runtime-to-permanent

Before you Begin.

1. Confirm the IdM server is deployed and the host-based firewall has been configured correctly. For more information, see Port Requirements in the Linux Domain Identity, Authentication, and Policy Guide.
2. Obtain an account on the IdM server with permissions to create zones on the IdM server.
3. Confirm if the Satellite or an external Capsule is managing DNS for a domain.
4. Confirm that the Satellite or external Capsule are currently working as expected.
5. In the case of a newly installed system, complete the installation procedures in this guide first. In particular, DNS and DHCP configuration should have been completed.
6. Make a backup of the answer file in case you have to revert the changes. See Specifying Installation Options for more information.

Create a Kerberos Principal on the IdM Server.

1. Ensure you have a Kerberos ticket.

   # kinit idm_user

   Where idm_user is the account created for you by the IdM administrator.

2. Create a new Kerberos principal for the Satellite or Capsule to use to authenticate to the IdM server.

   # ipa service-add capsule/satellite.example.com

1. Install the ipa-client package on Satellite Server or Capsule Server:

   • On Satellite Server, enter the following command:

     # satellite-maintain packages install ipa-client

   • On Capsule Server, enter the following command:

     # yum install ipa-client

2. Configure the IdM client by running the installation script and following the on-screen prompts.

   # ipa-client-install

3. Ensure you have a Kerberos ticket.

   # kinit admin

4. Remove any preexisting keytab.

   # rm /etc/foreman-proxy/dns.keytab

5. Get the keytab created for this system.

   # ipa-getkeytab -p capsule/satellite.example.com@EXAMPLE.COM \
   -s idm1.example.com -k /etc/foreman-proxy/dns.keytab

   Note

   When adding a keytab to a standby system with the same host name as the original system in service, add the r option to prevent generating new credentials and rendering the credentials on the original system invalid.

6. Set the group and owner for the keytab file to foreman-proxy as follows.

   # chown foreman-proxy:foreman-proxy /etc/foreman-proxy/dns.keytab

7. If required, check the keytab is valid.

   # kinit -kt /etc/foreman-proxy/dns.keytab \
   capsule/satellite.example.com@EXAMPLE.COM

Configure DNS Zones in the IdM web UI.

1. Create and configure the zone to be managed:

   1. Navigate to Network Services > DNS > DNS Zones.
   2. Select Add and enter the zone name. In this example, example.com.
   3. Click Add and Edit.

   4. On the Settings tab, in the BIND update policy box, add an entry as follows to the semi-colon separated list.

      grant capsule\047satellite.example.com@EXAMPLE.COM wildcard * ANY;

   5. Ensure Dynamic update is set to True.
   6. Enable Allow PTR sync.
   7. Select Save to save the changes.

2. Create and Configure the reverse zone.

   1. Navigate to Network Services > DNS > DNS Zones.
   2. Select Add.
   3. Select Reverse zone IP network and add the network address in CIDR format to enable reverse lookups.
   4. Click Add and Edit.

   5. On the Settings tab, in the BIND update policy box, add an entry as follows to the semi-colon separated list:

      grant capsule\047satellite.example.com@EXAMPLE.COM wildcard * ANY;

   6. Ensure Dynamic update is set to True.
   7. Select Save to save the changes.

1. Navigate to Infrastructure > Capsules.
2. For each Capsule to be updated, from the Actions drop-down menu, select Refresh.

3. Configure the domain:

   1. Go to Infrastructure > Domains and select the domain name.
   2. On the Domain tab, ensure DNS Capsule is set to the Capsule where the subnet is connected.

4. Configure the subnet:

   1. Go to Infrastructure > Subnets and select the subnet name.
   2. On the Subnet tab, set IPAM to None.
   3. On the Domains tab, ensure the domain to be managed by the IdM server is selected.
   4. On the Capsules tab, ensure Reverse DNS Capsule is set to the Capsule where the subnet is connected.
   5. Click Submit to save the changes.

Before you Begin

1. Confirm the IdM Server is deployed and the host-based firewall has been configured correctly. For more information, see Port Requirements in the Linux Domain Identity, Authentication, and Policy Guide.
2. Obtain root user privileges on the IdM server.
3. Confirm if the Satellite or an external Capsule is managing DNS for a domain.
4. Confirm that the Satellite or external Capsule are currently working as expected.
5. In the case of a newly installed system, complete the installation procedures in this guide first. In particular, DNS and DHCP configuration should have been completed.
6. Make a backup of the answer file in case you have to revert the changes. See Specifying Installation Options for more information.

Enabling External Updates to the DNS Zone in the IdM Server

1. On the IdM Server, add the following to the top of the /etc/named.conf file.

   // This was added to allow Satellite Server at 192.168.25.1 to make DNS updates.
   ########################################################################
   include "/etc/rndc.key";
   controls  {
   inet 192.168.25.2 port 953 allow { 192.168.25.1; } keys { "rndc-key"; };
   };
   ########################################################################

2. Reload named to make the changes take effect.

   # systemctl reload named

3. In the IdM web UI, go to Network Services > DNS > DNS Zones. Select the name of the zone. On the Settings tab:

   1. Add the following in the BIND update policy box.

      grant "rndc-key" zonesub ANY;

   2. Ensure Dynamic update is set to True.
   3. Click Update to save the changes.

4. Copy the /etc/rndc.key file from the IdM server to Satellite’s base system as follows.

   # scp /etc/rndc.key root@satellite.example.com:/etc/rndc.key

5. Ensure that the ownership, permissions, and SELinux context are correct.

   # restorecon -v /etc/rndc.key
   # chown -v root:named /etc/rndc.key
   # chmod -v 640 /etc/rndc.key

6. On Satellite Server, run the installation script as follows to use the external DNS server.

   # satellite-installer --scenario satellite \
   --foreman-proxy-dns=true \
   --foreman-proxy-dns-managed=false \
   --foreman-proxy-dns-provider=nsupdate \
   --foreman-proxy-dns-server="192.168.25.2" \
   --foreman-proxy-keyfile=/etc/rndc.key \
   --foreman-proxy-dns-ttl=86400

Testing External Updates to the DNS Zone in the IdM Server

1. Install bind-utils for testing with nsupdate.

   # yum install bind-utils

2. Ensure the key in the /etc/rndc.key file on Satellite Server is the same one as used on the IdM server.

   key "rndc-key" {
           algorithm hmac-md5;
           secret "secret-key==";
   };

3. On Satellite Server, create a test DNS entry for a host. For example, host test.example.com with an A record of 192.168.25.20 on the IdM server at 192.168.25.1.

   # echo -e "server 192.168.25.1\n \
   update add test.example.com 3600 IN A 192.168.25.20\n \
   send\n" | nsupdate -k /etc/rndc.key

4. On Satellite Server, test the DNS entry.

   # nslookup test.example.com 192.168.25.1
   Server:		192.168.25.1
   Address:	192.168.25.1#53
   
   Name:	test.example.com
   Address: 192.168.25.20

5. To view the entry in the IdM web UI, go to Network Services > DNS > DNS Zones. Select the name of the zone and search for the host by name.

6. If resolved successfully, remove the test DNS entry.

   # echo -e "server 192.168.25.1\n \
   update delete test.example.com 3600 IN A 192.168.25.20\n \
   send\n" | nsupdate -k /etc/rndc.key

7. Confirm that the DNS entry was removed.

   # nslookup test.example.com 192.168.25.1

   The above nslookup command fails and returns the SERVFAIL error message if the record was successfully deleted.

1. Navigate to Infrastructure > Capsules.
2. For each Capsule to be updated, from the Actions drop-down menu, select Refresh.

3. Configure the domain:

   1. Go to Infrastructure > Domains and select the domain name.
   2. On the Domain tab, ensure DNS Capsule is set to the Capsule where the subnet is connected.

4. Configure the subnet:

   1. Go to Infrastructure > Subnets and select the subnet name.
   2. On the Subnet tab, set IPAM to DHCP or Internal DB.
   3. On the Domains tab, ensure the domain to be managed by the Satellite or Capsule is selected.
   4. On the Capsules tab, ensure Reverse DNS Capsule is set to the Capsule where the subnet is connected.
   5. Click Submit to save the changes.

1. Launch an EC2 instance of a Red Hat Enterprise Linux AMI
2. Connect to the newly created instance.