Understand Why IP Address Is Not Available in the Umbrella Dashboard Reports

Available Languages

Download Options

  • PDF     (3.6 KB)
    View with Adobe Reader on a variety of devices
  • ePub     (82.9 KB)
    View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
  • Mobi (Kindle)     (68.5 KB)
    View on Kindle device or Kindle app on multiple devices
Updated:October 22, 2025
Document ID:225265

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 why the internal IP address of a DNS query is not available in the Umbrella Dashboard Reports when using DNS in the Tunnel.

    Background Information

    The internal IP address of a DNS query is not populated in the Umbrella Dashboard Reports when users are using DNS in the Tunnel.

    Explanation

    Because of the way that the DNS queries are forwarded to Umbrella, internal IP addresses are not logged in the reports just by deploying DNS in the Tunnel. Users wishing to apply "internal network" identities still required the use of the Virtual Appliance or the Roaming Client / AnyConnect Client.

    Revision History

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

    Contributed by Cisco Engineers

    Was this Document Helpful?

    FeedbackFeedback

    Contact Cisco

    This Document Applies to These Products