Configure IP or DNS Settings on a Device with Umbrella Roaming Client Installed

Available Languages

Download Options

  • PDF     (46.4 KB)
    View with Adobe Reader on a variety of devices
  • ePub     (123.7 KB)
    View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
  • Mobi (Kindle)     (224.7 KB)
    View on Kindle device or Kindle app on multiple devices
Updated:October 7, 2025
Document ID:224870

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

    Introduction

    This document describes how to change static IP or DNS settings on a device with the Umbrella roaming client installed.

    Overview

    The Umbrella Roaming Client modifies the DNS settings on the computers' Network Interface (NIC). This means you must take extra care wherever you attempt to change settings on the interface, such as assigning a static IP address. 

    note-icon

    Note: This article only applies to the standalone Roaming Client and not the AnyConnect Roaming Security Module.

    Basics

    The Roaming Client replaces the DNS server assigned to the network interface with the loopback address (127.0.0.1). It is normal to see this value (127.0.0.1) assigned as DNS server when the client is running.

    When making a change to the Network Interface you MUST also replace the 127.0.0.1 DNS server value with the correct DNS server value for your network.  Do not use the default value of 127.0.0.1.

    caution-icon

    Caution: When switching from a DHCP IP address to a static IP configuration, you MUST also supply a static DNS server. If this is not done it can cause the DNS resolution to fail.

    Examples

    This screenshot shows an example of the DNS setting which must be updated when setting the static IP address:

    360041282071360041282071

    Remove the 127.0.0.1 setting.

    This screenshot shows an example of a correctly set DNS server:

    360041282111360041282111

    It is now safe to click OK and save the new Network interface settings.

    note-icon

    Note: After saving the NIC settings the Roaming Client again replaces the DNS server with 127.0.0.1. This is normal and expected behaviour.

    More Information

    The computer is configured to send all DNS traffic through the Roaming Client on 127.0.0.1:53.  However, the Roaming Client remembers the list of DNS servers that you assign to the network interface and uses them for handling DNS traffic:

    • If a DNS query is for an Internal Domain it is sent to the saved DNS servers from the network interface
    •  All other DNS queries are sent directly to Umbrella DNS resolvers in the cloud

    When switching to a static IP configuration the DHCP DNS server address is lost which triggers a known limitation in the Roaming Client. The Roaming Client does not configure DNS protection on a network interface with no DNS server, leading to a scenario where the network interface has no DNS configured.

    Revision History

    Revision Publish Date Comments
    1.0
    07-Oct-2025
    Initial Release
    TAC Authored

    Contributed by Cisco Engineers

    Was this Document Helpful?

    FeedbackFeedback

    Contact Cisco

    This Document Applies to These Products