When either type of client (static or DHCP client) initiates an A record update with its authoritative DNS server, it will first start by performing an SOA query for the FQDN of the client in question: The client then receives a response from the authoritative DNS server containing information about the server that is to process the dynamic update.
From there, the client continues communicating with the primary DNS server that accepted the A record update.
The roaming client is lightweight software installed on Windows machines which takes in the client’s DNS queries and conditionally forwards them to Umbrella anycast resolvers.
The roaming client forwards DNS queries listed in Internal Domains to the local DNS servers on the network.
Some customers have reported issues with Microsoft Dynamic Updates after installing virtual appliances (VAs) in their environment or installing the Umbrella Roaming Client on some machines.