Configure OpenDNS on Windows 11, MacOS, and Linux

Available Languages

Download Options

  • PDF     (82.4 KB)
    View with Adobe Reader on a variety of devices
  • ePub     (81.1 KB)
    View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
  • Mobi (Kindle)     (67.0 KB)
    View on Kindle device or Kindle app on multiple devices
Updated:March 31, 2026
Document ID:225802

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 configure OpenDNS DNS server addresses on Windows 11, macOS, and Linux.

 

Prerequisites

Requirements

 
  • Administrative access on the endpoint (Windows, macOS, or Linux)
  • Network connectivity to the internet
  • The OpenDNS resolver IP addresses:
    • 208.67.222.222
    • 208.67.220.220
  

Optional (FamilyShield):

  • 208.67.222.123
  • 208.67.220.123
 

Configure OpenDNS on Windows 11

  1. Navigate to Settings > Network & internet.
  2. Select the active connection:
    • Wi-Fi, then select the connected network, or Ethernet.
  3. Under DNS server assignment, click Edit.
  4. Select Manual.
  5. Enable IPv4.
  6. Enter these DNS servers:
    • Preferred DNS: 208.67.222.222
    • Alternate DNS: 208.67.220.220
  7. Click Save.
 

Configure OpenDNS on MacOS

 
  1. Navigate to System Settings > Network.
  2. Select the active network interface (for example, Wi‑Fi or Ethernet).
  3. Click Details.
  4. Select DNS.
  5. Under DNS Servers, add:
    • 208.67.222.222
    • 208.67.220.220
  6. Click OK, then click Apply.
 

Configure OpenDNS on Linux

 

Option 1. Configure DNS with NetworkManager (GUI)

  1. Open the network settings for the active connection.
  2. Edit the IPv4 DNS settings for the connection.
  3. Set DNS servers to:
    • 208.67.222.222
    • 208.67.220.220
  4. Save the connection changes and reconnect.

Option 2. Configure DNS with NetworkManager (nmcli)

  1. Identify the connection name:
    • Run the nmcli connection show command.
  2. Set DNS servers on the connection:
    • Run the nmcli connection modify command to set IPv4 DNS to 208.67.222.222 208.67.220.220.
  3. Reconnect the connection:
    • Disconnect and reconnect the NetworkManager connection.
note-icon

Note: The exact connection name and interface varies by distribution.

Option 3. Configure DNS with systemd-resolved (resolvectl)

If the distribution uses systemd-resolved, set DNS per-interface and verify settings with resolvectl.

Configure the DNS servers for the active interface to:

  •    208.67.222.222
  •    208.67.220.220
note-icon

Note: Configuration methods vary by distribution and whether DNS is managed by NetworkManager, systemd-networkd, or another service.

Verify DNS Resolution

After configuration, verify DNS queries resolve and that the configured resolvers are in use.

  • On Windows, verify DNS server assignment in the active adapter settings.
  • On macOS, verify DNS servers appear under the active interface DNS settings.
  • On Linux, verify the DNS servers for the active interface with the system resolver status.

If name resolution does not change immediately, clear the local DNS cache (method varies by operating system).

Troubleshooting

  • If DNS servers revert after reboot, verify whether DNS is enforced by:
    • VPN software
    • Mobile device management (MDM) profiles
    • Security software
    • DHCP options from the router (common if DNS is being set on the router instead of the endpoint)
  • If a browser uses DNS-over-HTTPS (DoH), it can bypass OS-level DNS settings. Verify browser DNS/DoH configuration if results do not match expectations.

Revision History

Revision Publish Date Comments
1.0
24-Apr-2026
Initial Release
TAC Authored

Contributed by Cisco Engineers

  • Robin Margallo
    Technical Consultant

Was this Document Helpful?

FeedbackFeedback

Contact Cisco

This Document Applies to These Products