Discover the dns server name in linux with these simple steps to identify dns servers and resolvers quickly 2026

Discover the dns server name in linux with these simple steps. This quick guide gives you a clear path to identifying your DNS server name, plus extra tips to keep your network moving smoothly. Here’s a concise, buddy-to-buddy style walkthrough that covers the essentials and a few pro tricks you’ll actually use.

Quick fact: Your DNS server name tells your computer where to send domain lookups, and it can impact speed and reliability of web access.

• What you’ll learn:

  • How to find the DNS server name on Linux using common commands
  • How to check DNS configuration for both systemd-resolved and traditional resolv.conf setups
  • How to verify DNS end-to-end with practical tests
  • Common pitfalls and quick fixes
  • Lightweight debugging steps you can run from a terminal

• Why it matters:

  • If you’re troubleshooting slow internet, DNS failures, or VPN quirks, knowing where DNS comes from helps you pinpoint problems fast.
  • For dev environments, consistent DNS resolves reduce flaky tests and unstable connections.

• Quick step-by-step overview:

  1. Identify the active resolver service
  2. Inspect DNS configuration files
  3. Resolve the DNS server name and test it
  4. Check for DNS leaks or misconfigurations
  5. Apply best practices for reliability

Useful resources text only: Apple Website – apple.com, Artificial Intelligence Wikipedia – en.wikipedia.org/wiki/Artificial_intelligence, Linux DNS Best Practices – en.wikipedia.org/wiki/Domain_Name_System, Systemd Documentation – www.freedesktop.org/wiki/Software/systemd, Networking Tools Guide – linux.die.net

Understanding DNS on Linux

DNS is the system that translates human-friendly domain names into IP addresses. On Linux, you might be using systemd-resolved, NetworkManager, or traditional resolv.conf-based configuration. Each setup has its own file locations and commands to reveal the DNS server name.

• Common DNS setups you might see:

  • systemd-resolved with resolvectl or systemd-resolve
  • NetworkManager with nmcli or nm-connection-editor
  • Static resolv.conf or /etc/resolv.conf managed by your distro
  • DNS over TLS or VPN-provided DNS, which can complicate things

• Why different methods exist:

  • Some distros ship systemd-resolved by default, others rely on legacy resolv.conf. Knowing which one you have is the first step.

Quick way to discover the DNS server name step by step

Step 1: Check which resolver service is running

• Use the service status command to see if systemd-resolved is active:
  • sudo systemctl status systemd-resolved
• Check NetworkManager’s resolver linkage:
  • nmcli device show | grep ‘IP4.DNS’ -C 2
• If nothing obvious shows up, you might be looking at a static /etc/resolv.conf file.

Step 2: Inspect /etc/resolv.conf

• Open the file:
  • cat /etc/resolv.conf
• Look for lines starting with nameserver. Those lines contain the DNS server IP addresses, not the names. If you see a comment like “Generated by NetworkManager” or “Generated by resolvconf,” that tells you where it’s coming from.
• Quick interpretation:
  • nameserver 1.1.1.1
  • nameserver 8.8.8.8
  • If you see only IPs, that’s fine for DNS resolution, but you might want to map those to hostnames later for troubleshooting.

Step 3: Use resolvectl for systemd-resolved

• If you’re on a system with systemd-resolved, resolver details can be checked with:
  • resolvectl status
• This shows DNS servers per link e.g., eth0, wlan0 and the search domains.
• You can also force or inspect DNS options per interface:
  • resolvectl query your-domain.test
  • resolvectl dns eth0 1.1.1.1

Step 4: Use systemd-resolve and dig for validation

• Validate DNS with dig or drill:
  • dig +short @1.1.1.1 example.com
  • drill example.com @1.1.1.1
• If you get a clean IP in the answer, the DNS server is reachable and responding.
• For system-wide DNS, check the DNS suffix search list:
  • resolvectl status | grep -i “Domains”

Step 5: Check for VPN or DNS leakage

• If you’re using a VPN, sometimes DNS requests go outside the tunnel. Test for DNS leaks with:
  • curl -s https://dnsleaktest.com | head -n 20
• While not perfect, it’s a quick sanity check to ensure DNS queries are staying secure.

Step 6: Verify end-to-end DNS resolution with a simple test

• Resolve a domain with the active DNS server directly:
  • dig @ example.com
  • Replace with your known DNS IP from resolvectl or resolv.conf
• Compare results with a recursive resolver:
  • dig example.com
• If both give similar answers, your DNS path is healthy; if not, you’ve found a potential misconfiguration.

Step 7: Confirm DNS settings persist across reboots

• Check symlink or configuration source:
  • ls -l /etc/resolv.conf
• If resolv.conf is dynamically generated, changes should be made in the contributing service NetworkManager, systemd-resolved, or your VPN client, not directly in resolv.conf.

Step 8: Common issues and fixes

• Issue: DNS server not responding
  • Fix: Change DNS servers in resolvectl or NetworkManager, or set a reliable fallback DNS.
• Issue: DNS resolution delays
  • Fix: Use closer or faster resolvers; consider a local DNS cache.
• Issue: VPN DNS routing
  • Fix: Ensure DNS requests stay inside the VPN tunnel or adjust VPN settings to force DNS through the tunnel.

How to configure a reliable DNS setup practical tips

• Use at least two DNS servers:
  • Primary and secondary e.g., 1.1.1.1 and 9.9.9.9
• Prefer privacy-respecting resolvers if you value tracking minimization:
  • Cloudflare, Quad9, or similar
• Consider enabling DNS over TLS DoT or DNS over HTTPS DoH if your distro supports it and you need it
• For servers, pin resolvers in /etc/resolv.conf or persistent NetworkManager profiles to avoid drift
• Periodically test DNS health as part of routine maintenance:
  • Keep an eye on latency, resolution failures, and timeouts

Troubleshooting checklist quick reference

• Check active resolver: systemctl status systemd-resolved or nmcli device show
• Inspect DNS sources: cat /etc/resolv.conf and resolvectl status
• Validate with dig or drill: dig @ domain
• Verify VPN DNS behavior: test for leaks
• Confirm persistence: examine /etc/resolv.conf and network profiles
• Monitor performance: measure DNS query times with time dig +short @server domain

DNS performance tips

• Use a fast, reliable primary DNS server and a nearby secondary for redundancy
• Enable caching where possible local DNS cache reduces repeated lookups
• Minimize DNS lookups for frequently used domains by leveraging proper caching and pre-fetch strategies
• If you manage multiple devices, consider centralized DNS policies or a small authoritative DNS setup in your network

Real-world scenarios

• Home office setup:
  • You’re seeing occasional slow page loads. Check if your router is the DNS source, switch to a public resolver like 1.1.1.1, and verify via dig.
• Remote work with VPN:
  • DNS failures inside the VPN can cause access issues to internal resources. Ensure VPN pushes DNS servers and routes DNS through the tunnel.
• Linux server in a data center:
  • Use systemd-resolved or resolvconf to keep resolvers consistent; test both reachability and reliability from multiple clients.

Comparison table: common commands and what they show

Purpose	Command	What it reveals
Active DNS servers systemd-resolved	resolvectl status	Per-link DNS server info
Active DNS servers general	cat /etc/resolv.conf	Lists resolver IPs, source may vary
Direct DNS query to a server	dig @8.8.8.8 example.com	Checks if a specific server responds
Quick DNS health any server	nslookup example.com 1.1.1.1	Simple lookup test
Network manager DNS info	nmcli device show	Shows DNS on each interface
Resolve a domain to IPs	dig example.com	Provides A/AAAA records and authority

Best practices for long-term reliability

• Keep your DNS servers up to date and monitor their performance
• Document your preferred DNS configuration for each environment home, work, cloud
• Use predictable, well-supported DNS services to reduce surprises after updates
• Regularly test DNS behavior after network changes or VPN updates
• If you serve internal domains, plan for split-horizon DNS to avoid leakage and ensure correct resolution for internal resources

Security considerations

• Prefer DNS servers that support DNSSEC validation to prevent spoofing
• Use encrypted DNS DoT or DoH if privacy and security are priorities
• Be mindful of DNS spoofing on untrusted networks; consider VPN or encrypted tunnels for sensitive lookups
• Regularly audit DNS logs for unusual query patterns that might indicate misconfigurations or misuse

In practice: a short checklist you can copy-paste

• Determine resolver service: systemctl status systemd-resolved OR nmcli device show
• Inspect resolv.conf: cat /etc/resolv.conf
• Check per-interface DNS: resolvectl status
• Validate with direct queries: dig @ example.com
• Ensure VPN DNS alignment: test for leaks and tunnel routing

Advanced topics optional

• DNS caching on Linux servers with dnsmasq or unbound
• Split-horizon DNS for internal vs external resolution
• DNS over TLS DoT and DNS over HTTPS DoH client configurations
• Automated DNS health monitoring with simple scripts

Quick-start cheat sheet

• Find DNS servers: resolvectl status or cat /etc/resolv.conf
• Validate a specific DNS server: dig @ domain
• Check per-interface DNS: nmcli device show or resolvectl status
• Confirm that DNS works through VPN: test DNS leakage and tunnel DNS

Frequently Asked Questions

How do I know which DNS server Linux is using?

You can check /etc/resolv.conf, run resolvectl status if you’re on systemd-resolved, or inspect NetworkManager’s DNS settings with nmcli. Discover if youre new to a discord server a simple guide to onboarding, etiquette, roles, and rules 2026

What if /etc/resolv.conf is a symlink?

If it’s a symlink, it usually points to a dynamically managed file by NetworkManager or systemd-resolved. Check the manager to understand where DNS sources are configured.

How can I test DNS speed on Linux?

Use dig to measure response times from different DNS servers. For example: time dig @1.1.1.1 example.com

Can I use DoT/DoH on Linux?

Yes, many tools support DoT/DoH. DoH clients like a web browser or specialized DoH utilities can be configured to use encrypted DNS. DoT can be enabled in some resolvers or via dedicated clients.

How do I switch DNS servers quickly?

Edit the appropriate configuration source resolv.conf, NetworkManager profiles, or systemd-resolved configuration and restart the service if needed.

What is the difference between resolv.conf and resolvectl?

Resolv.conf is a traditional resolver list. resolvectl is a tool for querying and configuring systemd-resolved, which manages DNS for systemd environments. Discover The Dns Server Address On Your Pc A Step By Step Guide 2026

Why doesn’t my VPN show the VPN DNS servers?

Some VPNs route DNS through the tunnel but not all. Check your VPN client settings and ensure that DNS over the VPN is enabled if available.

How do I make DNS changes permanent on Linux?

Make changes in the persistent configuration location for your setup: NetworkManager profiles, systemd-resolved config, or your VPN’s DNS settings.

How can I diagnose DNS problems quickly?

Cross-check resolv.conf, per-interface DNS, and perform end-to-end queries with dig. If issues persist, test without VPN and compare results.

What should I do if DNS keeps failing after reboot?

Ensure the service that manages DNS NetworkManager, systemd-resolved is enabled and configured to apply at boot. Check for static resolv.conf or startup scripts that override DNS on boot.

Yes, you can discover the DNS server name in Linux with these simple steps. In this guide, you’ll learn easy, practical ways to see which DNS servers your system is using, how to read resolver configuration, and how to verify DNS resolution across various setups—whether you’re on systemd-resolved, NetworkManager, or classic /etc/resolv.conf. We’ll cover quick checks, per-interface details, and some troubleshooting tips so you can get reliable DNS results fast. Think of this as a friendly, no-fl fluff toolbox you can pull out whenever you need to confirm what your Linux box is using for DNS. Discover the Default Isolation Level in SQL Server: Read Committed, Snapshot, and More 2026

Useful URLs and Resources:

• resolv.conf explained – resolv.conf page on Linux docs
• systemd-resolved documentation – systemd-resolve and resolvectl man pages
• NetworkManager DNS info – NetworkManager docs
• RFC 1034 and RFC 1035 – DNS concepts and name resolution
• Wikipedia DNS – Domain Name System overview

Quick overview of what you’ll find here

• Why DNS info varies by setup systemd-resolved, NetworkManager, or classic resolv.conf
• Step-by-step commands to read current DNS servers
• How to verify DNS resolution and identify the active server
• How to handle containers, VMs, and DHCP-driven environments
• Practical tips to change or override DNS safely

Quick steps to discover the DNS server name in Linux

• Step 1: Check the resolver configuration file
• Step 2: Inspect the system’s resolver service systemd-resolved or resolvectl
• Step 3: Inspect DNS settings for network managers
• Step 4: Verify with a DNS query and confirm which server was used
• Step 5: Consider edge cases containers, virtualization, DHCP

The resolver file: /etc/resolv.conf

What to look for

• The file commonly contains lines starting with nameserver followed by an IP address.
• If you see multiple lines, you’re likely listing more than one DNS server, in order of preference.
• In newer setups using systemd, this file may be a symlink to a systemd stub resolver, such as /run/systemd/resolve/stub-resolv.conf.

How to inspect it

• Command: cat /etc/resolv.conf
• Command: grep -E ‘^nameserver’ /etc/resolv.conf

What this tells you:

• The IPs listed after each nameserver line are the DNS servers your system will query in order.
• If you see a line like: nameserver 127.0.0.53, you’re using the systemd-resolved stub resolver on the local loopback, and the real servers are managed elsewhere.

Common pitfall

• If /etc/resolv.conf is a symlink to /run/systemd/resolve/stub-resolv.conf or a similar path, the actual DNS servers are configured through systemd-resolved or NetworkManager rather than a static file. In that case, the resolver’s status commands below will give you the real server list.

Systemd-resolved: status, status, status

Why it matters

• systemd-resolved is a modern, centralized DNS resolver used by many Linux distros Ubuntu, Debian-based systems, Fedora variants, etc.. It aggregates DNS settings from various sources DHCP, VPNs, network managers and caches results.

How to check

• Command: systemd-resolve –status
• Alternative: resolvectl status on newer systemd versions

What you’ll see

• A summary of Link network interface blocks showing DNS servers per interface.
• Look for lines like:
  • DNS Servers: 1.1.1.1 9.9.9.9
  • DNS Domain: example.local
• If you’re using the classic loopback DNS 127.0.0.53, that means systemd-resolved is actively handling DNS, and the real servers are listed under the relevant link.

Quick commands and examples

• Basic status check:
  • systemd-resolve –status
• If you prefer the shorter alias:
  • resolvectl status
• What to extract:
  • For each network interface, note the DNS Servers field.

Why this helps

• It gives you a centralized view across all adapters, VPNs, and Docker/VMs that piggyback on systemd-resolved.
• It also shows the local stub resolver’s presence, which is common in modern Linux setups.

NetworkManager: DNS and connections

Who uses NetworkManager

• Desktop-oriented distros Fedora Workstation, Ubuntu Desktop, etc. and many laptop configurations rely on NetworkManager to manage network connections and DNS.

How to inspect DNS with NetworkManager

• Command: nmcli device show
  • This shows a lot of details, including DNS servers for each device IP4.DNS and IP6.DNS fields.
• More targeted:
  • nmcli device show | grep -E “IP4.DNS|IP6.DNS”
  • Example: nmcli device show wlp2s0 | grep IP4.DNS
• Quick summary:
  • You’ll see DNS server addresses listed in the IP4.DNS entries; that’s what the device is using for DNS queries.

How to change DNS via NetworkManager safe and persistent

• Find your connection name:
  • nmcli con show
• Set new DNS servers:
  • nmcli con mod ipv4.dns “1.1.1.1 8.8.8.8”
  • nmcli con mod ipv4.dns-search “”
• Apply changes:
  • nmcli con up –reload
• What to expect:
  • After reloading, the DNS servers listed in resolvectl or systemd-resolved should reflect the new values, depending on your exact stack.

Why NetworkManager matters

• It’s the most common way laptops and desktop users configure DNS, thanks to user-friendly GUI tools and straightforward CLI commands.

Reading DNS per-interface details and direct lookups

Per-interface DNS details

• Command: nmcli device show | grep -E “IP4.DNS|IP6.DNS”
• This helps you map the DNS servers to a specific NIC eth0, wlan0, enp3s0, etc., which is particularly useful on multi-NIC systems or when you’re debugging VPN-related DNS leaks.

Quick test: validate DNS resolution

• Command: dig +short example.com
• Observations:
  • The DNS server used is typically shown in the header of the resolution step, but you can also run:
  • dig +trace example.com
  • The first answer comes from the resolver currently in place; to see which server was used, check the SERVER line in the dig output the final answer will include something like SERVER: 127.0.0.53#53 for a local stub or the actual DNS server IP if directly queried.

Verify by querying a specific server

• Command: dig @1.1.1.1 example.com
• If this returns results, your system can reach that DNS server; if not, you might need to check connectivity or firewall rules.

Quick table: when to use which command

Situation	Command	What it shows
See system-wide DNS servers systemd-resolved	systemd-resolve –status or resolvectl status	Lists per-link DNS servers
See DNS for all NetworkManager devices	nmcli device show	Shows IP4.DNS/IP6.DNS per device
See /etc/resolv.conf contents	cat /etc/resolv.conf	Static or stub-resolver content
Check per-interface DNS directly	nmcli device show	IP4.DNS and IP6.DNS for a specific interface
Validate actual resolution and server used	dig example.com	Resolution results and server used

Edge cases: containers, VMs, and DHCP

• Containers and Docker: When you run containers, DNS settings can be mounted from the host or overridden inside the container. Look at the container’s /etc/resolv.conf to see what DNS servers the container is using. If you’re using a modern container runtime, it usually forwards the host DNS settings unless you override them.
• Virtual machines: A VM may have its own NIC settings and DHCP-provided DNS, independent of the host. Inside the VM, repeat the same steps to identify its own DNS servers.
• DHCP-driven DNS: When a DHCP server provides DNS settings, your host might dynamically update /etc/resolv.conf or systemd-resolved. If you see frequent changes, it’s likely DHCP is pushing new DNS servers.

How to change DNS servers safely on Linux

• Systemd-resolved approach recommended on systems that use systemd
  • Edit the resolved.conf file:
    • sudo nano /etc/systemd/resolved.conf
    • Add or modify the DNS= line, for example: DNS=1.1.1.1 8.8.8.8
  • Restart the resolver:
    • sudo systemctl restart systemd-resolved
  • If you want /etc/resolv.conf to reflect the systemd-managed resolvers, you can set up the symlink:
    • sudo ln -sf /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf
• NetworkManager approach
  • Identify your connection name and edit:
    • nmcli con mod ipv4.dns “1.1.1.1 8.8.8.8”
    • nmcli con mod ipv4.dns-search “”
  • Bring the connection down and up to apply:
    • nmcli connection down
    • nmcli connection up
• Static /etc/resolv.conf approach less recommended on systems with active resolvers
  • Create or edit /etc/resolv.conf and add lines like:
    • nameserver 1.1.1.1
    • nameserver 8.8.8.8
  • Note: If a resolver service overwrites resolv.conf, changes may be overwritten on reboot or network change.

Practical tips and best practices

• Avoid mixing configurations: If you use systemd-resolved, let it manage DNS and avoid editing /etc/resolv.conf directly unless you’re sure it won’t be overwritten.
• Prefer DNS servers you trust and monitor latency and privacy implications. Public DNS providers vary in performance and features like DNS over TLS.
• Test after changes: Always run a quick dig or nslookup to confirm that the intended DNS server is responding as expected.
• Be mindful of VPNs and corporate networks: VPNs often push their own DNS servers, which can override local settings. Check the DNS section of your VPN client or use resolvectl to see what’s active during a VPN session.

Real-world stats and context

• In recent years, many mainstream Linux distributions rely on systemd-resolved or NetworkManager to manage DNS. The result is that /etc/resolv.conf often points to a local stub 127.0.0.53 when systemd-resolved is active, with the actual servers configured elsewhere.
• NetworkManager remains the go-to DNS manager for desktop systems, providing an intuitive interface for changing DNS servers without editing files by hand.
• For servers, you’ll often see static DNS configuration or DHCP-driven DNS settings, especially in cloud environments and containers.

Quick reference: command cheat sheet

• View resolver configuration:
  • cat /etc/resolv.conf
  • grep -E ‘^nameserver’ /etc/resolv.conf
• Systemd-resolved status:
  • systemd-resolve –status
  • resolvectl status
• NetworkManager DNS:
  • nmcli device show
  • nmcli device show | grep IP4.DNS
• Test DNS resolution:
  • dig example.com
  • dig @127.0.0.53 example.com
  • dig @1.1.1.1 example.com
• Check link-specific DNS if using systemd-resolved:
  • resolvectl status
  • systemd-resolve –status

Frequently Asked Questions

How do I find my DNS server in Linux quickly?

The fastest way is to read /etc/resolv.conf for static configurations or to use systemd-resolve –status and nmcli device show to see per-interface DNS servers. If you’re on a systemd-based setup, you’ll likely see a local stub 127.0.0.53 in resolv.conf, with the real servers listed in systemd-resolved’s output.

What is /etc/resolv.conf used for?

resolv.conf is a resolver configuration file that specifies the DNS servers your system will query. It’s a central place for simple setups, but on modern systems, its contents can be managed by systemd-resolved or NetworkManager.

Why do I see 127.0.0.53 in /etc/resolv.conf?

That means your system uses systemd-resolved as the DNS resolver. The real DNS servers are configured elsewhere through systemd-resolved, NetworkManager, or DHCP. The local 127.0.0.53 is the stub resolver that forwards queries to the actual servers. Discover how to find your dns server ip address on linux today 2026

How can I change my DNS server in NetworkManager?

Use nmcli con mod ipv4.dns “1.1.1.1 8.8.8.8” and then nmcli con up to apply. You can also set the DNS search domain to an empty string if you don’t want search suffixes.

How do I verify which DNS server a system uses when I run a query?

Run dig example.com and look at the SERVER line or the header’s authoritative section. If you’re using a stub resolver, DIG will show SERVER: 127.0.0.53#53. If you query a specific server dig @1.1.1.1 example.com, you’ll see results only from that server.

Can DNS settings differ between interfaces?

Yes. With NetworkManager or per-interface configuration, different interfaces e.g., Ethernet vs. Wi-Fi can use different DNS servers. Check each interface with nmcli device show and inspect IP4.DNS values.

How do I know if DNS is being pushed by DHCP?

Check your interface’s DHCP client configuration or the router’s DHCP settings. If DNS values change automatically when you reconnect to Wi-Fi or reconnect to VPNs, DHCP or VPN DNS pushes are likely at play. systemd-resolved shows per-link DNS servers, which helps diagnose this.

What’s the difference between systemd-resolved and resolv.conf?

Systemd-resolved is a modern, centralized resolver that can aggregate DNS settings from multiple sources. resolv.conf is a traditional resolver configuration file. On systems using systemd-resolved, resolv.conf often points to a local stub resolver 127.0.0.53. The real servers are configured via systemd-resolved. Discover How to Make a Minecraft Multiplayer Server for Free: Quick Guide to Free Hosting, Setup, and Tips 2026

How can I test DNS performance quickly?

Run multiple dig queries to common domains e.g., google.com, cloudflare.com against different DNS servers you’re considering. Compare latency and consistency. Tools like “namebench” or “dnsperf” can help in more formal testing, though they’re more advanced.

How do I ensure DNS settings persist across reboots?

Use your distribution’s network manager to set DNS servers NetworkManager for desktops, netplan or NetworkManager on newer servers. For systemd-resolved, keep the DNS= entries in /etc/systemd/resolved.conf and restart the service. Avoid editing /etc/resolv.conf directly if a resolver service is managing it.

What should I do if DNS isn’t resolving after a change?

• Confirm the change actually took effect check resolv.conf, systemd-resolved status, and NetworkManager settings.
• Check for conflicting services e.g., DHCP or VPN clients overwriting DNS.
• Test with a known good DNS server like 8.8.8.8 or 1.1.1.1 to isolate network issues.
• Ensure you can reach the DNS server no firewall blocks, proper routing.

Is there a best practice for Linux DNS in mixed environments home, work, cloud?

Start with a stable local resolver systemd-resolved and a primary set of trusted DNS servers e.g., a secure public DNS provider. Add redundancy with a second server. Keep DHCP-derived DNS from overriding critical settings unless you rely on dynamic changes for VPNs or other networks. Periodically verify DNS health with quick tests and monitor latency.

How do I view DNS settings inside a Docker container?

Inside the container, inspect /etc/resolv.conf. By default, containers inherit host DNS settings unless you override them with –dns flags or custom Docker network configurations. For isolation, you can set specific DNS servers per container if needed.

Can I use DNS over TLS on Linux?

Yes, with additional tools and proxies like dnscrypt-proxy, Stubby, or Cloudflare’s 1.1.1.1 DNS over TLS support via resolvers. This is more advanced and may require careful configuration to work across all apps and containers. Discover How to Find Your DNS Server IP Address in 3 Simple Steps and Beyond 2026

What if I’m using a VPN and the DNS looks wrong?

VPNs often push their own DNS servers. Check your VPN settings and test DNS resolution both with and without the VPN connected. You may want to force a specific DNS server for certain apps or routes using firewall rules or per-app DNS configurations depending on your OS and VPN client capabilities.

---

If you want a quick, repeatable workflow to always know which DNS server your Linux machine uses, start with /etc/resolv.conf for baseline visibility, then move to systemd-resolved or NetworkManager for authoritative, per-interface, and dynamic configurations. With these steps, you’ll never wonder which DNS server is serving your queries again. And when in doubt, a simple dig query and a quick check of resolvectl or nmcli will usually tell you everything you need.

Sources:

Nordvpn eero router setup 2026: The Ultimate Guide to VPN on Eero Routers

Vpnnext VPN 加密上网全面指南：隐私保护、速度优化、解锁地理限制与实际使用技巧

Nordvpn amazon fire tablet setup 2026: Quick Install Guide for Fire Tablet, Android App, NordLynx, and Streaming Discover How to Find Your Primary DNS Server Address with Ease: Quick Guide to Locate and Change DNS Settings 2026

Geo edge vpn full guide for privacy, streaming, geo-restrictions, and setup tips

Vpn路由：让你的整个家庭网络都享受VPN的终极保护