• Step 5

    Connect FE to DNS service  

    Now we have a machine with a public IP address and a DNS name for our service. Now is the moment to connect all together, depending on the provider, this step might be tricky. Most servers on the Internet have a fixed (static) IP address that never changes. The DNS record for these nodes will only change infrequently. 

    However, many home users are assigned an IP address that changes more frequently. These dynamic IP addresses are assigned by an ISP. This makes it a challenge to translate a Name to one of these IP addresses.

    If your server IP address is static, there is not too much to do. You can manually update the IP address at nsupdate.fedcloud.eu. On the other hand, if you are not sure, you should use a software utility to perform Dynamic DNS Updates. But don't worry, let’s do this in a few steps.

    First, install ddclient, the original Linux utility for dynamic DNS updates, you can run:

    $ sudo apt install ddclient

    You can skip the graphical configuration and directly edit the file /etc/ddclient.conf with the following configuration:

    ssl=yes  # To use secure SSL communications
    use=web, web=checkip.dyndns.com/, web-skip='IP Address'
    login=mythematicservice.test.fedcloud.eu  # Your hostname
    password='9VvAN4yJW6'  # Your host secret
    mythematicservice.test.fedcloud.eu  # Your hostname

    Do you remember the url and secret obtained at step 1? In the url it looks something like this https://mythematicservice.test.fedcloud.eu:9VvAN4yJW6@nsupdate.fedcloud.eu/nic/update.

    The secret would be ‘9VvAN4yJW6’, check it is working by running:

    $ sudo ddclient -debug -verbose -noquiet

    Now you should be able to access your FE and Kubernetes endpoints using your DNS address instead of an IP number. You can find out more information about DynamicDNS and how to configure it in Ubuntu here. For now,  try to access the kubernetes dashboard using your DNS, for example https://mythematicservice.test.fedcloud.eu/dashboard/#/login

    If all steps were executed correctly, the previous browser warning will disappear from now on when you access via https using the DNS name (and not the IP).