Skip to content

DNS Name Resolution Configuration

Configuring a DNS Name Resolution

The first step to configuring the Cloud Access Connector is to ensure that there is a solid connection between the Cloud Access Connector and the Active Directory Domain Controller. You need to ensure that you can route from this machine to the Domain Controller and that there is nothing to prevent port 443 (https) and port 636 (LDAPS) connecting between the two systems.

In the following example the IP of the Domain Controller is 10.162.0.42.

.yaml format file

In step 4 below this is a .yaml format file and the whitespaces are critical. Tabs cannot be used in a .yaml file. Please format it exactly as it is displayed in the above example.

  1. Install Resolvconf
    sudo apt update
    sudo apt install resolvconf
    
  2. Edit the resolvconf file
    Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
    DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
    127.0.0.53 is the systemd-resolved stub resolver.
    run "systemd-resolve --status" to see details about the actual nameservers.
    search teradici.local
    nameserver 10.162.0.42
    
  3. Restart the resolvconf service
    sudo service resolvconf restart
    
  4. Edit Netplan Config
    sudo nano /etc/netplan/50-cloud-init.yaml
    This file is generated from information provided by the datasource. Changes
    to it will not persist across an instance reboot. To disable cloud-init's
    network configuration capabilities, write a file
    /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
    network: {config: disabled}
    network:
    ethernets:
    ens4:
    dhcp4: true
    match:
    macaddress: 42:01:0a:a2:00:29
    set-name: ens4
    nameservers:
    search: [teradici.local]
    addresses: [10.162.0.42]
    version: 2
    
  5. Restart Netplan
    sudo netplan apply
    
  6. Test DNS
    ping <name-of-domain-controller>
    
  7. If the response is successful, you should receive a message similar to the example below:
    PING example.com (172.217.14.206): 56 data bytes
    64 bytes from 172.217.14.206: icmp_seq=0 ttl=118 time=16.622 ms
    64 bytes from 172.217.14.206: icmp_seq=1 ttl=118 time=50.675 ms
    64 bytes from 172.217.14.206: icmp_seq=2 ttl=118 time=27.682 ms
    64 bytes from 172.217.14.206: icmp_seq=3 ttl=118 time=19.886 ms
    ^C
    --- example.com ping statistics ---
    4 packets transmitted, 4 packets received, 0.0% packet loss