{"id":13613,"date":"2025-12-30T11:11:12","date_gmt":"2025-12-30T05:41:12","guid":{"rendered":"https:\/\/www.youstable.com\/blog\/?p=13613"},"modified":"2025-12-30T11:11:14","modified_gmt":"2025-12-30T05:41:14","slug":"fix-dns-on-linux-server","status":"publish","type":"post","link":"https:\/\/www.youstable.com\/blog\/fix-dns-on-linux-server","title":{"rendered":"How to Fix DNS on Linux Server in 2026? &#8211; Easy Guide"},"content":{"rendered":"\n<p><strong>To fix DNS on a Linux server<\/strong>, verify network connectivity, check which resolver stack you use (systemd-resolved, NetworkManager, or plain resolv.conf), set correct nameservers, flush DNS caches, and test with dig. <\/p>\n\n\n\n<p>If you run a DNS service <strong>(BIND\/Unbound\/dnsmasq)<\/strong>, validate configuration, open port 53, and confirm zones and recursion. DNS failing on a server breaks updates, package installs, and outbound API calls.<\/p>\n\n\n\n<p>In this guide, I\u2019ll show you how to fix DNS on Linux server environments step-by-step, using simple commands, proven diagnostics, and distribution-specific instructions. Whether you\u2019re a beginner or maintaining production nodes, you\u2019ll find quick wins and robust, permanent fixes.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"quick-dns-diagnosis-checklist\"><strong>Quick DNS Diagnosis Checklist<\/strong><\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Check basic network connectivity:<\/strong> can you ping an IP (not a domain)?<\/li>\n\n\n\n<li><strong>Identify your resolver stack:<\/strong> systemd-resolved, NetworkManager, or static \/etc\/resolv.conf.<\/li>\n\n\n\n<li>Inspect current <a href=\"https:\/\/www.youstable.com\/blog\/change-nameservers-in-godaddy\/\"><strong>nameservers and search domains<\/strong><\/a>.<\/li>\n\n\n\n<li>Test DNS resolution with dig and nslookup.<\/li>\n\n\n\n<li>Flush DNS caches (client and local DNS services).<\/li>\n\n\n\n<li>Check firewall\/SELinux for port 53 if the server runs DNS.<\/li>\n\n\n\n<li><strong>Review logs:<\/strong> systemd-journals and <a href=\"https:\/\/www.youstable.com\/blog\/fix-503-service-temporarily-unavailable\/\"><strong>service logs for errors<\/strong><\/a> (SERVFAIL, timeouts).<\/li>\n<\/ul>\n\n\n\n<pre class=\"wp-block-code\"><code># 1) Connectivity\nping -c2 1.1.1.1 || ping -c2 8.8.8.8\n\n# 2) What resolver do I use?\nreadlink -f \/etc\/resolv.conf\nresolvectl status 2&gt;\/dev\/null || systemd-resolve --status 2&gt;\/dev\/null\n\n# 3) What is my DNS seeing?\ncat \/etc\/resolv.conf\ndig youstable.com +short\nnslookup youstable.com\n\n# 4) Trace a domain (find where it fails)\ndig example.com +trace\n\n# 5) Logs (adjust service name as needed)\njournalctl -u systemd-resolved --no-pager --since \"10 min ago\"\njournalctl -u named --since \"1 hour ago\"\njournalctl -u unbound --since \"1 hour ago\"<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"understand-how-dns-works-on-linux\"><strong>Understand How DNS Works on Linux<\/strong><\/h2>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"glibc-resolver-and-nsswitch\"><strong>glibc resolver and nsswitch<\/strong><\/h3>\n\n\n\n<p>Most Linux apps rely on the glibc resolver, which consults sources listed in \/etc\/nsswitch.conf. The line \u201chosts: files dns myhostname\u201d controls resolution order. If DNS appears ignored, check nsswitch to ensure \u201cdns\u201d is present and not blocked by misordered sources.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"etc-resolv-conf\"><strong>\/etc\/resolv.conf<\/strong><\/h3>\n\n\n\n<p>resolv.conf defines nameserver IPs, search domains, and options (like timeout and attempts). Depending on your distro, it may be managed by systemd-resolved, NetworkManager, netplan, or cloud-init. Editing it directly may be overwritten on reboot\u2014use the right tool for persistent changes.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"systemd-resolved\"><strong>systemd-resolved<\/strong><\/h3>\n\n\n\n<p>On many modern distros (Ubuntu, Debian, Fedora), systemd-resolved is the stub resolver. It commonly uses 127.0.0.53 as a local DNS and manages resolv.conf via a symlink. Use resolvectl to view and set DNS per interface and to flush caches.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"networkmanager-netplan-and-ifcfg\"><strong>NetworkManager, netplan, and ifcfg<\/strong><\/h3>\n\n\n\n<p>NetworkManager (nmcli) and netplan (Ubuntu cloud images) configure interfaces and DNS persistently. RHEL-based systems may use ifcfg files. Cloud-init may set DNS at boot from metadata. Set DNS in the appropriate layer for changes to persist across reboots.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"client-side-fixes-dns-not-working-on-a-linux-server\"><strong>Client-Side Fixes: DNS Not Working on a Linux Server<\/strong><\/h2>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"step-1-verify-network-connectivity-and-routing\"><strong>Step 1: Verify network connectivity and routing<\/strong><\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>ip a\nip route\nping -c3 1.1.1.1\ncurl -I http:\/\/1.1.1.1<\/code><\/pre>\n\n\n\n<p>If ping to an IP works but resolving domains fails, the issue is DNS-specific. If IP connectivity is also broken, fix networking first (gateway, routes, security groups).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"step-2-inspect-and-set-resolv-conf-temporary\"><strong>Step 2: Inspect and set resolv.conf (temporary)<\/strong><\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>cat \/etc\/resolv.conf\n# Quick temporary fix: point to public resolvers\nsudo sed -i.bak 's\/^\/#\/' \/etc\/resolv.conf\nprintf \"nameserver 1.1.1.1\\nnameserver 8.8.8.8\\noptions timeout:2 attempts:2\\n\" | sudo tee \/etc\/resolv.conf<\/code><\/pre>\n\n\n\n<p>This may be overwritten by your network stack. Make it persistent using the correct tool below.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"step-3-use-systemd-resolved-properly-ubuntu-debian-fedora\"><strong>Step 3: Use systemd-resolved properly (Ubuntu\/Debian\/Fedora)<\/strong><\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code># Show current DNS per interface\nresolvectl status\n\n# Set DNS for a specific interface, e.g., eth0\nsudo resolvectl dns eth0 1.1.1.1 8.8.8.8\nsudo resolvectl domain eth0 example.local\n\n# Ensure resolv.conf points to systemd-resolved's stub\nsudo ln -sf \/run\/systemd\/resolve\/stub-resolv.conf \/etc\/resolv.conf\n\n# Flush cache\nsudo resolvectl flush-caches<\/code><\/pre>\n\n\n\n<p>If resolv.conf is not a symlink to systemd\u2019s file, mismatches can cause failures. Recreate the symlink as shown.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"step-4-networkmanager-persistent-dns-rhel-centos-alma-rocky-ubuntu-desktop\"><strong>Step 4: NetworkManager persistent DNS (RHEL\/CentOS\/Alma\/Rocky\/Ubuntu Desktop)<\/strong><\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code># List connections and pick the active one\nnmcli con show\n# Set DNS and disable automatic DNS from DHCP if needed\nsudo nmcli con mod &lt;CONNECTION_NAME&gt; ipv4.ignore-auto-dns yes\nsudo nmcli con mod &lt;CONNECTION_NAME&gt; ipv4.dns \"1.1.1.1 8.8.8.8\"\nsudo nmcli con up &lt;CONNECTION_NAME&gt;  # or reload\n# For IPv6 if applicable\nsudo nmcli con mod &lt;CONNECTION_NAME&gt; ipv6.ignore-auto-dns yes\nsudo nmcli con mod &lt;CONNECTION_NAME&gt; ipv6.dns \"2606:4700:4700::1111 2001:4860:4860::8888\"<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"step-5-netplan-common-on-ubuntu-cloud-images\"><strong>Step 5: Netplan (common on Ubuntu cloud images)<\/strong><\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo nano \/etc\/netplan\/50-cloud-init.yaml\n# Example:\n# network:\n#   version: 2\n#   ethernets:\n#     eth0:\n#       dhcp4: yes\n#       nameservers:\n#         addresses: &#91;1.1.1.1, 8.8.8.8]\nsudo netplan apply<\/code><\/pre>\n\n\n\n<p>If cloud-init overwrites DNS on reboot, set DNS in \/etc\/cloud\/cloud.cfg or the datasource (metadata) as per your provider\u2019s docs.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"step-6-fix-nsswitch-order-and-hosts-file\"><strong>Step 6: Fix nsswitch order and hosts file<\/strong><\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>grep '^hosts:' \/etc\/nsswitch.conf\n# Recommended baseline:\n# hosts: files dns myhostname\n\nsudo sed -i 's\/^hosts:.*\/hosts: files dns myhostname\/' \/etc\/nsswitch.conf\nsudo head -n 50 \/etc\/hosts<\/code><\/pre>\n\n\n\n<p>Ensure \/etc\/hosts doesn\u2019t contain conflicting entries that hijack <a href=\"https:\/\/www.youstable.com\/blog\/do-i-need-a-domain-for-a-forex-vps\/\">domains you need<\/a> to resolve via DNS.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"step-7-flush-local-dns-caches\"><strong>Step 7: Flush local DNS caches<\/strong><\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code># systemd-resolved\nsudo resolvectl flush-caches\n\n# nscd\nsudo nscd -i hosts\n\n# dnsmasq (cache flush by SIGHUP)\nsudo killall -HUP dnsmasq\n\n# unbound\nsudo unbound-control flush_zone .  # or specific zones<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"step-8-vpn-split-dns-and-ipv6-pitfalls\"><strong>Step 8: VPN, split-DNS, and IPv6 pitfalls<\/strong><\/h3>\n\n\n\n<p>VPN clients often install their own resolv.conf or push DNS via NetworkManager. Test without VPN. If IPv6 is enabled but your resolver can\u2019t reach v6 upstreams, either add working IPv6 DNS or disable IPv6 DNS for now via NetworkManager or resolv.conf options.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"if-your-server-runs-dns-bind-unbound-dnsmasq\"><strong>If Your Server Runs DNS (BIND\/Unbound\/dnsmasq)<\/strong><\/h2>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"open-and-test-port-53-udp-tcp\"><strong>Open and test port 53 (UDP\/TCP)<\/strong><\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code># Firewalld\nsudo firewall-cmd --add-service=dns --permanent\nsudo firewall-cmd --reload\n\n# UFW\nsudo ufw allow 53\nsudo ufw allow 53\/udp\n\n# nftables quick check\nsudo nft list ruleset | sed -n '1,200p'\n\n# Test externally (from another host)\ndig @SERVER_IP example.com A\ndig @SERVER_IP google.com A +tcp<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"bind-named-configuration-and-zone-sanity\"><strong>BIND (named) configuration and zone sanity<\/strong><\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code># Validate configs and zones\nsudo named-checkconf\nsudo named-checkzone example.com \/var\/named\/example.com.zone\n\n# Common mistakes:\n# - Missing SOA\/NS records\n# - Serial number not incremented\n# - Wrong allow-query \/ recursion settings<\/code><\/pre>\n\n\n\n<p>For a resolver serving your private network, enable recursion and restrict access:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>options {\n    recursion yes;\n    allow-recursion { 10.0.0.0\/8; 192.168.0.0\/16; };\n    allow-query     { any; };\n    dnssec-validation auto;\n};<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"unbound-as-a-validating-resolver\"><strong>Unbound as a validating resolver<\/strong><\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code># Check logs for SERVFAIL (often DNSSEC-related)\njournalctl -u unbound -e\n\n# Basic allowlist for your LAN:\nserver:\n  interface: 0.0.0.0\n  access-control: 10.0.0.0\/8 allow\n  access-control: 192.168.0.0\/16 allow\n  verbosity: 1<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"dnsmasq-notes\"><strong>dnsmasq notes<\/strong><\/h3>\n\n\n\n<p>dnsmasq can forward or cache DNS. If it\u2019s bound to 127.0.0.1 but resolv.conf points elsewhere, clients may bypass it. Align resolv.conf or systemd-resolved to use dnsmasq, and HUP after changes.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"dnssec-and-servfail\"><strong>DNSSEC and SERVFAIL<\/strong><\/h3>\n\n\n\n<p>If you see SERVFAIL sporadically, it may be DNSSEC validation failing due to time skew or upstream issues. Ensure NTP is healthy and your resolver can reach root and TLD servers. As a temporary workaround, use a public resolver (1.1.1.1, 8.8.8.8) while you fix validation.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"verification-confirm-dns-is-healthy\"><strong>Verification: Confirm DNS Is Healthy<\/strong><\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Resolve multiple domains:<\/strong> A, AAAA, MX, and NS records.<\/li>\n\n\n\n<li>Test UDP and TCP on port 53 if you run a DNS service.<\/li>\n\n\n\n<li>Trace a problematic domain end-to-end with dig +trace.<\/li>\n\n\n\n<li>Packet capture to see timeouts or refusals.<\/li>\n<\/ul>\n\n\n\n<pre class=\"wp-block-code\"><code>dig youstable.com A +short\ndig google.com MX +short\ndig @1.1.1.1 cloudflare.com NS +short\ndig example.com AAAA +short\ndig +trace example.com\n\n# Tcpdump (observe DNS traffic)\nsudo tcpdump -ni any port 53 -vv<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"make-dns-settings-persistent\"><strong>Make DNS Settings Persistent<\/strong><\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Use nmcli or netplan instead of editing resolv.conf directly.<\/li>\n\n\n\n<li>Align systemd-resolved and resolv.conf symlink.<\/li>\n\n\n\n<li>Disable overwrite sources (DHCP ignore-auto-dns, cloud-init updates) if needed.<\/li>\n\n\n\n<li>Document DNS choices (public vs. private resolvers) per environment.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"prevention-reduce-dns-outages\"><strong>Prevention: Reduce DNS Outages<\/strong><\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Always configure at least two resolvers from different networks (e.g., 1.1.1.1 and 8.8.8.8).<\/li>\n\n\n\n<li>Monitor DNS latency and failure rates with scripts or a monitoring suite.<\/li>\n\n\n\n<li>Use DNS caching locally (systemd-resolved, Unbound) for faster responses.<\/li>\n\n\n\n<li>Keep time synced (NTP\/chrony) to avoid DNSSEC validation failures.<\/li>\n\n\n\n<li>Control changes <a href=\"https:\/\/www.youstable.com\/blog\/how-to-configure-ssh-backup-via-jetbackup-in-directadmin\/\">via configuration<\/a> management (Ansible, Terraform).<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"when-to-escalate-and-how-youstable-helps\"><strong>When to Escalate and How YouStable Helps<\/strong><\/h2>\n\n\n\n<p>If you still see timeouts, SERVFAIL, or intermittent resolution under load, the issue may involve upstream filters, ISP peering, or recursive resolver behavior. In production, consider managed DNS and managed servers. YouStable\u2019s hosting stack ships with hardened defaults, 24\/7 support, and best-practice resolver configurations to keep your apps reachable.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"common-errors-and-fast-fixes\"><strong>Common Errors and Fast Fixes<\/strong><\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>\u201cTemporary failure in name resolution\u201d \u2014<\/strong> set working nameservers and flush caches.<\/li>\n\n\n\n<li><strong>\u201cconnection timed out; no servers could be reached\u201d \u2014<\/strong> check firewall, upstream reachability, or VPN.<\/li>\n\n\n\n<li><strong>\u201cSERVFAIL\u201d \u2014<\/strong> inspect DNSSEC, time sync, or zone delegation problems.<\/li>\n\n\n\n<li><strong>resolv.conf keeps changing \u2014<\/strong> configure DNS in NetworkManager, netplan, or cloud-init.<\/li>\n\n\n\n<li><strong>Works with IP but not hostname \u2014<\/strong> fix nsswitch order and DNS settings.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"faqs\"><strong>FAQ&#8217;s<\/strong><\/h2>\n\n\n<div id=\"rank-math-faq\" class=\"rank-math-block\">\n<div class=\"rank-math-list \">\n<div id=\"faq-question-1765884727174\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \" class=\"rank-math-question \" id=\"1-why-is-dns-not-working-on-my-linux-server\">1. <strong>Why is DNS not working on my Linux server?<\/strong><\/h3>\n<div class=\"rank-math-answer \">\n\n<p>Common causes include wrong nameservers, overwritten resolv.conf, misordered nsswitch.conf, local DNS cache issues, VPN interference, or firewall blocks on port 53. Start by checking resolv.conf, resolvectl status, and testing with dig against a known-good resolver.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1765884734934\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \" class=\"rank-math-question \" id=\"2-how-do-i-permanently-set-dns-in-linux\">2. <strong>How do I permanently set DNS in Linux?<\/strong><\/h3>\n<div class=\"rank-math-answer \">\n\n<p>Use your network stack\u2019s tool: nmcli (NetworkManager), netplan (Ubuntu cloud), or resolvectl (systemd-resolved). Avoid editing resolv.conf directly; it\u2019s often managed and will be overwritten. For RHEL-family systems, nmcli with ignore-auto-dns ensures persistence across reboots.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1765884744550\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \" class=\"rank-math-question \" id=\"3-how-do-i-flush-dns-cache-on-linux\">3. <strong>How do I flush DNS cache on Linux?<\/strong><\/h3>\n<div class=\"rank-math-answer \">\n\n<p>For systemd-resolved use \u201cresolvectl flush-caches\u201d. For nscd use \u201cnscd -i hosts\u201d. For dnsmasq send SIGHUP, and for Unbound use \u201cunbound-control flush_zone\u201d. Many servers don\u2019t cache at the glibc level\u2014caches live in these services.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1765884752297\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \" class=\"rank-math-question \" id=\"4-how-can-i-test-if-port-53-is-open\">4. <strong>How can I test if port 53 is open?<\/strong><\/h3>\n<div class=\"rank-math-answer \">\n\n<p>From a remote host, run \u201cdig @SERVER_IP example.com A\u201d and \u201cdig @SERVER_IP example.com +tcp\u201d. On the server, confirm firewall rules (ufw, firewalld, nftables) and listen sockets with \u201css -lunpt | grep :53\u201d.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1765884760004\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \" class=\"rank-math-question \" id=\"5-how-do-i-fix-temporary-failure-in-name-resolution-quickly\">5. <strong>How do I fix \u201cTemporary failure in name resolution\u201d quickly?<\/strong><\/h3>\n<div class=\"rank-math-answer \">\n\n<p>Set working resolvers (1.1.1.1 and 8.8.8.8), align the resolv.conf symlink with systemd-resolved if used, flush caches, and verify with dig. Make the change persistent via nmcli or netplan so it survives reboots.<\/p>\n<p>With the steps above, you can fix DNS on Linux server environments reliably and make your changes stick. If you want a hardened setup with proactive monitoring and expert support, YouStable\u2019s managed hosting can take DNS headaches off your plate.<\/p>\n\n<\/div>\n<\/div>\n<\/div>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>To fix DNS on a Linux server, verify network connectivity, check which resolver stack you use (systemd-resolved, NetworkManager, or plain [&hellip;]<\/p>\n","protected":false},"author":21,"featured_media":16695,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"categories":[350],"tags":[],"class_list":["post-13613","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-knowledgebase"],"acf":[],"featured_image_src":"https:\/\/www.youstable.com\/blog\/wp-content\/uploads\/2025\/12\/How-to-Fix-DNS-on-Linux-Server.jpg","author_info":{"display_name":"Sanjeet Chauhan","author_link":"https:\/\/www.youstable.com\/blog\/author\/sanjeet"},"_links":{"self":[{"href":"https:\/\/www.youstable.com\/blog\/wp-json\/wp\/v2\/posts\/13613","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.youstable.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.youstable.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.youstable.com\/blog\/wp-json\/wp\/v2\/users\/21"}],"replies":[{"embeddable":true,"href":"https:\/\/www.youstable.com\/blog\/wp-json\/wp\/v2\/comments?post=13613"}],"version-history":[{"count":5,"href":"https:\/\/www.youstable.com\/blog\/wp-json\/wp\/v2\/posts\/13613\/revisions"}],"predecessor-version":[{"id":16697,"href":"https:\/\/www.youstable.com\/blog\/wp-json\/wp\/v2\/posts\/13613\/revisions\/16697"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.youstable.com\/blog\/wp-json\/wp\/v2\/media\/16695"}],"wp:attachment":[{"href":"https:\/\/www.youstable.com\/blog\/wp-json\/wp\/v2\/media?parent=13613"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.youstable.com\/blog\/wp-json\/wp\/v2\/categories?post=13613"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.youstable.com\/blog\/wp-json\/wp\/v2\/tags?post=13613"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}