This section details the networking and port requirements for Uyuni.
- Fully Qualified Domain Name (FQDN)
The Uyuni server must resolve its FQDN correctly. If the FQDN cannot be resolved, it can cause serious problems in a number of different components.
For more information about configuring the hostname and DNS, see https://documentation.suse.com/sles/15-SP3/html/SLES-all/cha-network.html#sec-network-yast-change-host.
- Hostname and IP Address
To ensure that the Uyuni domain name can be resolved by its clients, both server and client machines must be connected to a working DNS server. You also need to ensure that reverse lookups are correctly configured.
For more information about setting up a DNS server, see https://documentation.suse.com/sles/15-SP3/html/SLES-all/cha-dns.html.
- Using a Proxy When Installing from SUSE Linux Enterprise Media
If you are on an internal network and do not have access to SUSE Customer Center, you can set up and use a proxy during installation.
For more information about configuring a proxy for access to SUSE Customer Center during a SUSE Linux Enterprise installation, see https://documentation.suse.com/sles/15-SP3/html/SLES-all/cha-boot-parameters.html#sec-boot-parameters-advanced-proxy.
The hostname of Uyuni must not contain uppercase letters as this may cause jabberd to fail. Choose the hostname of your Uyuni server carefully. Although changing the server name is possible and supported, it is important to plan for this change before going ahead with it. When you change the hostname of the server, all clients attached to the server must be made aware of the change.
In a production environment, the Uyuni Server and clients should always use a firewall. For a comprehensive list of the required ports, see installation:ports.adoc.
For more information on disconnected setup and port configuration, see administration:disconnected-setup.adoc#client-cfg-reg-with-bootstrap-disconnected.