Create DNS entries and deploy PEG VM as part of installing PEG.

Create DNS entries where each domain mentioned in Table 1, points to the PEG VM (PEG must have a static IP or a static domain name).

For security, some organizations might require a custom DNS. The following steps describe how to update the settings to use a custom DNS and ensure smooth data forwarding to the platform.

Procedure

  1. Edit the CoreDNS ConfigMap.
    1. Run the command: kubectl edit configmap coredns -n kube-system.
    2. Modify the Corefile to replace the default DNS forward setting with the client's custom DNS.
  2. Change the configuration.
    1. Locate the line: forward. /etc/resolv.conf.
    2. Change the line to: forward. example_DNS.
      Replace example_DNS with your custom DNS.

    Example of the modified configuration:

    
    apiVersion: v1
    data:
      Corefile: |
        .:53 {
        errors
        health
        ready
        kubernetes cluster.local in-addr.arpa ip6.arpa {
          pods insecure
          upstream
          fallthrough in-addr.arpa ip6.arpa
        }
        hosts /etc/coredns/NodeHosts {
          reload 1s
          fallthrough
        }
        prometheus :9153
        forward . <CUSTOM_DNS_HERE>
        cache 30
        loop
        reload
        loadbalance
      }
  3. Apply the changes.
    1. Save and exit the editor to apply the changes.
    2. CoreDNS will automatically reload the new configuration.