Installing Satellite Server in a disconnected network environment

Procedure

1. For a new installation, install fapolicyd:

   # dnf install fapolicyd

   Copy to Clipboard

2. For an existing installation, install fapolicyd using satellite-maintain packages install:

   # satellite-maintain packages install fapolicyd

   Copy to Clipboard

3. Start the fapolicyd service:

   # systemctl enable --now fapolicyd

   Copy to Clipboard

Procedure

1. Enter the following command with any additional options that you want to use:

   # satellite-installer --scenario satellite \
   --foreman-initial-organization "My_Organization" \
   --foreman-initial-location "My_Location" \
   --foreman-initial-admin-username admin_user_name \
   --foreman-initial-admin-password admin_password

   Copy to Clipboard

   The script displays its progress and writes logs to /var/log/foreman-installer/satellite.log.

2. Unmount the ISO images:

   # umount /media/sat6
   # umount /media/rhel8

   Copy to Clipboard

Procedure

1. In the Satellite web UI, navigate to Content > Subscriptions.
2. Click Manage Manifest.
3. Switch to the CDN Configuration tab.
4. Select the Export Sync tab.
5. Click Update.

CLI procedure

1. Log in to your Satellite Server by using SSH.

2. Set CDN configuration to sync by using exports:

   # hammer organization configure-cdn --name="My_Organization" --type=export_sync

   Copy to Clipboard

Procedure

1. Navigate to Content > Subscriptions.
2. Click Manage Manifest.
3. Navigate to the CDN Configuration tab.
4. Select the Network Sync tab.
5. In the URL field, enter the address of the upstream Satellite Server.
6. In the Username, enter your username for upstream login.
7. In the Password, enter your password or personal access token for upstream login.
8. In the Organization label field, enter the label of the upstream organization.
9. Optional: In the Lifecycle Environment Label field, enter the label of the upstream lifecycle environment. Default is Library.
10. Optional: In the Content view label field, enter the label of the upstream content view. Default is Default_Organization_View.
11. From the SSL CA Content Credential menu, select a CA certificate used by the upstream Satellite Server.
12. Click Update.
13. In the Satellite web UI, navigate to Content > Products.
14. Select the product that contains the repositories that you want to synchronize.

15. From the Select Action menu, select Sync Now to synchronize all repositories within the product.

    You can also create a synchronization plan to ensure updates on a regular basis. For more information, see Creating a Synchronization Plan in Managing content.

CLI procedure

1. Connect to your downstream Satellite Server using SSH.

2. View information about the upstream CA certificate:

   # hammer content-credential show \
   --name="My_Upstream_CA_Cert" \
   --organization="My_Downstream_Organization"

   Copy to Clipboard

   Note the ID of the CA certificate for the next step.

3. Set CDN configuration to an upstream Satellite Server:

   # hammer organization configure-cdn --name="My_Downstream_Organization" \
   --type=network_sync \
   --url https://upstream-satellite.example.com \
   --username upstream_username --password upstream_password \
   --ssl-ca-credential-id "My_Upstream_CA_Cert_ID" \ --upstream-organization-label="_My_Upstream_Organization" \
   [--upstream-lifecycle-environment-label="My_Lifecycle_Environment"] \
   [--upstream-content-view-label="My_Content_View"]

   Copy to Clipboard

   The default lifecycle environment label is Library. The default content view label is Default_Organization_View.

Procedure

1. Disable DHCP, DNS, and TFTP integration on your Satellite Server:

   # satellite-installer --foreman-proxy-dhcp false \
   --foreman-proxy-dns false \
   --foreman-proxy-tftp false

   Copy to Clipboard

2. Disable the Capsule integration for every subnet:

   1. In the Satellite web UI, navigate to Infrastructure > Subnets.
   2. Select a subnet.
   3. On the Capsules tab, clear the DHCP Capsule, TFTP Capsule, and Reverse DNS Capsule fields.
3. In the Satellite web UI, navigate to Infrastructure > Domains and select a domain.
4. Clear the DNS Capsule field.

5. Optional: If you use a DHCP service supplied by a third party, configure your DHCP server to pass the following options:

   Option 66: IP address of Satellite or Capsule
   Option 67: /pxelinux.0

   Copy to Clipboard

   For more information about DHCP options, see RFC 2132.

Procedure

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

   # mkdir /root/satellite_cert

   Copy to Clipboard

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

   Copy to Clipboard

3. Create the /root/satellite_cert/openssl.cnf configuration file for the CSR and include the following content:

   [ req ]
   req_extensions = v3_req
   distinguished_name = req_distinguished_name
   prompt = no
   
   [ req_distinguished_name ]
   commonName = satellite.example.com
   
   [ v3_req ]
   basicConstraints = CA:FALSE
   keyUsage = digitalSignature, keyEncipherment
   extendedKeyUsage = serverAuth, clientAuth
   subjectAltName = @alt_names
   
   [ alt_names ]
   DNS.1 = satellite.example.com

   Copy to Clipboard

   For more information about the [ v3_req ] parameters and their purpose, see RFC 5280: Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile.

4. Optional: If you want to add Distinguished Name (DN) details to the CSR, add the following information to the [ req_distinguished_name ] section:

   [req_distinguished_name]
   CN = satellite.example.com
   countryName =My_Country_Name 

   1

   
   stateOrProvinceName = My_State_Or_Province_Name 

   2

   
   localityName = My_Locality_Name 

   3

   
   organizationName = My_Organization_Or_Company_Name
   organizationalUnitName = My_Organizational_Unit_Name 

   4

   Copy to Clipboard

   1

   Two letter code

   2

   Full name

   3

   Full name (example: New York)

   4

   Division responsible for the certificate (example: IT department)

5. Generate 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

   Copy to Clipboard

   1

   Path to the private key

   2

   Path to the configuration file

   3

   Path to the CSR to generate

6. Send the certificate signing request to the certificate authority (CA). The same CA 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 CA for the preferred method. In response to the request, you can expect to receive a CA bundle and a signed certificate, in separate files.

Verification

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

Procedure

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

2. Disable all repositories and enable only the following repositories:

   # subscription-manager repos --disable '*'
   # subscription-manager repos \
   --enable=satellite-6.15-for-rhel-8-x86_64-rpms \
   --enable=satellite-maintenance-6.15-for-rhel-8-x86_64-rpms \
   --enable=rhel-8-for-x86_64-baseos-rpms \
   --enable=rhel-8-for-x86_64-appstream-rpms

   Copy to Clipboard

3. Enable the following module:

   # dnf module enable satellite:el8

   Copy to Clipboard
   Note

   Enablement of the module satellite:el8 warns about a conflict with postgresql:10 and ruby:2.5 as these modules are set to the default module versions on Red Hat Enterprise Linux 8. The module satellite:el8 has a dependency for the modules postgresql:12 and ruby:2.7 that will be enabled with the satellite:el8 module. These warnings do not cause installation process failure, hence can be ignored safely. For more information about modules and lifecycle streams on Red Hat Enterprise Linux 8, see Red Hat Enterprise Linux Application Streams Lifecycle.

Procedure

1. To install PostgreSQL, enter the following command:

   # dnf install postgresql-server postgresql-evr postgresql-contrib

   Copy to Clipboard

2. To initialize PostgreSQL, enter the following command:

   # postgresql-setup initdb

   Copy to Clipboard

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

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

   Copy to Clipboard

   Note that the default configuration of external PostgreSQL needs to be adjusted to work with Satellite. The base recommended external database configuration adjustments are as follows:

   • checkpoint_completion_target: 0.9
   • max_connections: 500
   • shared_buffers: 512MB
   • work_mem: 4MB

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

   listen_addresses = '*'

   Copy to Clipboard

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

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

   Copy to Clipboard

6. Add the following line to the file:

     host  all   all   Satellite_ip/32   md5

   Copy to Clipboard

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

   # systemctl enable --now postgresql

   Copy to Clipboard

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

   # firewall-cmd --add-service=postgresql

   Copy to Clipboard

9. Make the changes persistent:

   # firewall-cmd --runtime-to-permanent

   Copy to Clipboard

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

    $ su - postgres -c psql

    Copy to Clipboard

11. Create three databases and dedicated roles: one for Satellite, one for Candlepin, and one for Pulp:

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

    Copy to Clipboard

12. Connect to the Pulp database:

    postgres=# \c pulpcore
    You are now connected to database "pulpcore" as user "postgres".

    Copy to Clipboard

13. Create the hstore extension:

    pulpcore=# CREATE EXTENSION IF NOT EXISTS "hstore";
    CREATE EXTENSION

    Copy to Clipboard

14. Exit the postgres user:

    # \q

    Copy to Clipboard

15. 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"
    # PGPASSWORD='Pulpcore_Password' psql -h postgres.example.com -p 5432 -U pulp -d pulpcore -c "SELECT 1 as ping"

    Copy to Clipboard

Procedure

1. To configure the external databases for Satellite, enter the following command:

   # satellite-installer \
   --foreman-db-database foreman \
   --foreman-db-host postgres.example.com \
   --foreman-db-manage false \
   --foreman-db-password Foreman_Password \
   --foreman-proxy-content-pulpcore-manage-postgresql false \
   --foreman-proxy-content-pulpcore-postgresql-db-name pulpcore \
   --foreman-proxy-content-pulpcore-postgresql-host postgres.example.com \
   --foreman-proxy-content-pulpcore-postgresql-password Pulpcore_Password \
   --foreman-proxy-content-pulpcore-postgresql-user pulp \
   --katello-candlepin-db-host postgres.example.com \
   --katello-candlepin-db-name candlepin \
   --katello-candlepin-db-password Candlepin_Password \
   --katello-candlepin-manage-db false

   Copy to Clipboard

   To enable the Secure Sockets Layer (SSL) protocol for these external databases, add the following options:

   --foreman-db-root-cert <path_to_CA>
   --foreman-db-sslmode verify-full
   --foreman-proxy-content-pulpcore-postgresql-ssl true
   --foreman-proxy-content-pulpcore-postgresql-ssl-root-ca <path_to_CA>
   --katello-candlepin-db-ssl true
   --katello-candlepin-db-ssl-ca <path_to_CA>
   --katello-candlepin-db-ssl-verify true

   Copy to Clipboard

Procedure

1. On your Red Hat Enterprise Linux host, install the ISC DHCP Service and Berkeley Internet Name Domain (BIND) utilities packages:

   # dnf install dhcp-server bind-utils

   Copy to Clipboard

2. Generate a security token:

   # tsig-keygen -a hmac-md5 omapi_key

   Copy to Clipboard

3. Edit the dhcpd configuration file for all subnets and add the key generated by tsig-keygen. 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 "My_Secret";
   };
   omapi-key omapi_key;

   Copy to Clipboard

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

4. 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.

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

   # firewall-cmd --add-service dhcp

   Copy to Clipboard

6. Make the changes persistent:

   # firewall-cmd --runtime-to-permanent

   Copy to Clipboard

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

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

   Copy to Clipboard

8. 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

   Copy to Clipboard

9. 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

   Copy to Clipboard

10. Enable and start the DHCP service:

    # systemctl enable --now dhcpd

    Copy to Clipboard

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

    # dnf install nfs-utils
    # systemctl enable --now nfs-server

    Copy to Clipboard

12. 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

    Copy to Clipboard

13. 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

    Copy to Clipboard

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

    # mount -a

    Copy to Clipboard

15. 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)

    Copy to Clipboard

    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.

16. Reload the NFS server:

    # exportfs -rva

    Copy to Clipboard

17. Configure the firewall for DHCP omapi port 7911:

    # firewall-cmd --add-port=7911/tcp

    Copy to Clipboard

18. Optional: Configure the firewall for external access to NFS. Clients are configured using NFSv3.

    # firewall-cmd \
    --add-service mountd \
    --add-service nfs \
    --add-service rpc-bind \
    --zone public

    Copy to Clipboard

19. Make the changes persistent:

    # firewall-cmd --runtime-to-permanent

    Copy to Clipboard

Procedure

1. Install the nfs-utils package:

   # satellite-maintain packages install nfs-utils

   Copy to Clipboard

2. Create the DHCP directories for NFS:

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

   Copy to Clipboard

3. Change the file owner:

   # chown -R foreman-proxy /mnt/nfs

   Copy to Clipboard

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

   Copy to Clipboard

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

   Copy to Clipboard

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

   # mount -a

   Copy to Clipboard

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
   $ cat /mnt/nfs/etc/dhcp/dhcpd.conf
   $ cat /mnt/nfs/var/lib/dhcpd/dhcpd.leases
   $ exit

   Copy to Clipboard

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

   # satellite-installer \
   --enable-foreman-proxy-plugin-dhcp-remote-isc \
   --foreman-proxy-dhcp-provider=remote_isc \
   --foreman-proxy-dhcp-server=My_DHCP_Server_FQDN \
   --foreman-proxy-dhcp=true \
   --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=My_Secret \
   --foreman-proxy-plugin-dhcp-remote-isc-omapi-port=7911

   Copy to Clipboard
9. Associate the DHCP service with the appropriate subnets and domain.

Creating a Kerberos principal on the IdM server

1. Obtain a Kerberos ticket for the account obtained from the IdM administrator:

   # kinit idm_user

   Copy to Clipboard

2. Create a new Kerberos principal for Satellite Server to use to authenticate on the IdM server:

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

   Copy to Clipboard

Installing and configuring the idM client

1. On the base operating system of either the Satellite or Capsule that is managing the DNS service for your deployment, install the ipa-client package:

   # satellite-maintain packages install ipa-client

   Copy to Clipboard

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

   # ipa-client-install

   Copy to Clipboard

3. Obtain a Kerberos ticket:

   # kinit admin

   Copy to Clipboard

4. Remove any preexisting keytab:

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

   Copy to Clipboard

5. Obtain the keytab for this system:

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

   Copy to Clipboard
   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. For the dns.keytab file, set the group and owner to foreman-proxy:

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

   Copy to Clipboard

7. Optional: To verify that the keytab file is valid, enter the following command:

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

   Copy to Clipboard

Configuring DNS zones in the IdM web UI

1. Create and configure the zone that you want to manage:

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

   4. Click the Settings tab and in the BIND update policy box, add the following to the semi-colon separated list:

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

      Copy to Clipboard
   5. Set Dynamic update to True.
   6. Enable Allow PTR sync.
   7. Click Save to save the changes.

2. Create and configure the reverse zone:

   1. Navigate to Network Services > DNS > DNS Zones.
   2. Click 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. Click the Settings tab and in the BIND update policy box, add the following to the semi-colon separated list:

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

      Copy to Clipboard
   6. Set Dynamic update to True.
   7. Click Save to save the changes.

Configuring the Satellite or Capsule Server that manages the DNS service for the domain

1. Configure your Satellite Server or Capsule Server to connect to your DNS service:

   # satellite-installer \
   --foreman-proxy-dns-managed=false \
   --foreman-proxy-dns-provider=nsupdate_gss \
   --foreman-proxy-dns-server="idm1.example.com" \
   --foreman-proxy-dns-tsig-keytab=/etc/foreman-proxy/dns.keytab \
   --foreman-proxy-dns-tsig-principal="capsule/satellite.example.com@EXAMPLE.COM" \
   --foreman-proxy-dns=true

   Copy to Clipboard

2. For each affected Capsule, update the configuration of that Capsule in the Satellite web UI:

   1. In the Satellite web UI, navigate to Infrastructure > Capsules, locate the Satellite Server, and from the list in the Actions column, select Refresh.

   2. Configure the domain:

      1. In the Satellite web UI, navigate to Infrastructure > Domains and select the domain name.
      2. In the Domain tab, ensure DNS Capsule is set to the Capsule where the subnet is connected.

   3. Configure the subnet:

      1. In the Satellite web UI, navigate to Infrastructure > Subnets and select the subnet name.
      2. In the Subnet tab, set IPAM to None.
      3. In the Domains tab, select the domain that you want to manage using the IdM server.
      4. In the Capsules tab, ensure Reverse DNS Capsule is set to the Capsule where the subnet is connected.
      5. Click Submit to save the changes.

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:

   ########################################################################
   
   include "/etc/rndc.key";
   controls  {
   inet _IdM_Server_IP_Address_ port 953 allow { _Satellite_IP_Address_; } keys { "rndc-key"; };
   };
   ########################################################################

   Copy to Clipboard

2. Reload the named service to make the changes take effect:

   # systemctl reload named

   Copy to Clipboard

3. In the IdM web UI, navigate to Network Services > DNS > DNS Zones and click the name of the zone. In the Settings tab, apply the following changes:

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

      grant "rndc-key" zonesub ANY;

      Copy to Clipboard
   2. Set Dynamic update to True.
   3. Click Update to save the changes.

4. Copy the /etc/rndc.key file from the IdM server to the base operating system of your Satellite Server. Enter the following command:

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

   Copy to Clipboard

5. To set the correct ownership, permissions, and SELinux context for the rndc.key file, enter the following command:

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

   Copy to Clipboard

6. Assign the foreman-proxy user to the named group manually. Normally, satellite-installer ensures that the foreman-proxy user belongs to the named UNIX group, however, in this scenario Satellite does not manage users and groups, therefore you need to assign the foreman-proxy user to the named group manually.

   # usermod -a -G named foreman-proxy

   Copy to Clipboard

7. On Satellite Server, enter the following satellite-installer command to configure Satellite to use the external DNS server:

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

   Copy to Clipboard

Testing external updates to the DNS zone in the IdM server

1. Ensure that the key in the /etc/rndc.key file on Satellite Server is the same key file that is used on the IdM server:

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

   Copy to Clipboard

2. 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

   Copy to Clipboard

3. 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

   Copy to Clipboard
4. To view the entry in the IdM web UI, navigate to Network Services > DNS > DNS Zones. Click the name of the zone and search for the host by name.

5. 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

   Copy to Clipboard

6. Confirm that the DNS entry was removed:

   # nslookup test.example.com 192.168.25.1

   Copy to Clipboard

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

Updating the configuration in the Satellite web UI

1. In the Satellite web UI, navigate to Infrastructure > Capsules.
2. For each Capsule that you want to update, from the Actions list, select Refresh.

3. Configure the domain:

   1. In the Satellite web UI, navigate to Infrastructure > Domains and click the domain name that you want to configure.
   2. In the Domain tab, set DNS Capsule to the Capsule where the subnet is connected.

4. Configure the subnet:

   1. In the Satellite web UI, navigate to Infrastructure > Subnets and select the subnet name.
   2. In the Subnet tab, set IPAM to DHCP or Internal DB.
   3. In the Domains tab, select the domain that you want to manage using Satellite or Capsule.
   4. In the Capsules tab, set Reverse DNS Capsule to the Capsule where the subnet is connected.
   5. Click Submit to save the changes.