{"id":367853,"date":"2021-11-16T16:00:57","date_gmt":"2021-11-16T13:00:57","guid":{"rendered":"https:\/\/en.buradabiliyorum.com\/how-to-run-your-own-dns-server-on-your-local-network-cloudsavvy-it\/"},"modified":"2021-11-16T16:00:57","modified_gmt":"2021-11-16T13:00:57","slug":"how-to-run-your-own-dns-server-on-your-local-network-cloudsavvy-it","status":"publish","type":"post","link":"https:\/\/buradabiliyorum.com\/en\/how-to-run-your-own-dns-server-on-your-local-network-cloudsavvy-it\/","title":{"rendered":"#How to Run Your Own DNS Server on Your Local Network \u2013 CloudSavvy IT"},"content":{"rendered":"<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_89 counter-hierarchy ez-toc-counter ez-toc-custom ez-toc-container-direction\">\n<p class=\"ez-toc-title\" style=\"cursor:inherit\">Table of Contents<\/p>\n<label for=\"ez-toc-cssicon-toggle-item-6aee0d2822eb4\" class=\"ez-toc-cssicon-toggle-label\"><span class=\"\"><span class=\"eztoc-hide\" style=\"display:none;\">Toggle<\/span><span class=\"ez-toc-icon-toggle-span\"><svg style=\"fill: #dd3333;color:#dd3333\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" class=\"list-377408\" width=\"20px\" height=\"20px\" viewBox=\"0 0 24 24\" fill=\"none\"><path d=\"M6 6H4v2h2V6zm14 0H8v2h12V6zM4 11h2v2H4v-2zm16 0H8v2h12v-2zM4 16h2v2H4v-2zm16 0H8v2h12v-2z\" fill=\"currentColor\"><\/path><\/svg><svg style=\"fill: #dd3333;color:#dd3333\" class=\"arrow-unsorted-368013\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"10px\" height=\"10px\" viewBox=\"0 0 24 24\" version=\"1.2\" baseProfile=\"tiny\"><path d=\"M18.2 9.3l-6.2-6.3-6.2 6.3c-.2.2-.3.4-.3.7s.1.5.3.7c.2.2.4.3.7.3h11c.3 0 .5-.1.7-.3.2-.2.3-.5.3-.7s-.1-.5-.3-.7zM5.8 14.7l6.2 6.3 6.2-6.3c.2-.2.3-.5.3-.7s-.1-.5-.3-.7c-.2-.2-.4-.3-.7-.3h-11c-.3 0-.5.1-.7.3-.2.2-.3.5-.3.7s.1.5.3.7z\"\/><\/svg><\/span><\/span><\/label><input type=\"checkbox\"  id=\"ez-toc-cssicon-toggle-item-6aee0d2822eb4\" checked aria-label=\"Toggle\" \/><nav><ul class='ez-toc-list ez-toc-list-level-1 ' ><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/buradabiliyorum.com\/en\/how-to-run-your-own-dns-server-on-your-local-network-cloudsavvy-it\/#What_Is_DNS\" >What Is DNS?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/buradabiliyorum.com\/en\/how-to-run-your-own-dns-server-on-your-local-network-cloudsavvy-it\/#Why_Run_Your_Own_DNS\" >Why Run Your Own DNS?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/buradabiliyorum.com\/en\/how-to-run-your-own-dns-server-on-your-local-network-cloudsavvy-it\/#DNS_With_Dnsmasq\" >DNS With Dnsmasq<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/buradabiliyorum.com\/en\/how-to-run-your-own-dns-server-on-your-local-network-cloudsavvy-it\/#Getting_Started\" >Getting Started<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/buradabiliyorum.com\/en\/how-to-run-your-own-dns-server-on-your-local-network-cloudsavvy-it\/#Mapping_Hostnames_to_IPs\" >Mapping Hostnames to IPs<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/buradabiliyorum.com\/en\/how-to-run-your-own-dns-server-on-your-local-network-cloudsavvy-it\/#Testing_Your_Server\" >Testing Your Server<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-7\" href=\"https:\/\/buradabiliyorum.com\/en\/how-to-run-your-own-dns-server-on-your-local-network-cloudsavvy-it\/#Configuring_Your_Network\" >Configuring Your Network<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-8\" href=\"https:\/\/buradabiliyorum.com\/en\/how-to-run-your-own-dns-server-on-your-local-network-cloudsavvy-it\/#Conclusion\" >Conclusion<\/a><\/li><\/ul><\/nav><\/div>\n<p><strong>&#8220;#How to Run Your Own DNS Server on Your Local Network \u2013 CloudSavvy IT&#8221;<\/strong><\/p>\n<div id=\"article-content-area\">\n<figure style=\"width: 1200px\" class=\"wp-caption aligncenter\"><img loading=\"lazy\" decoding=\"async\" class=\"type:primaryImage size-full wp-image-14817\" srcset=\"https:\/\/www.cloudsavvyit.com\/p\/uploads\/2021\/11\/c73ebab4.jpg?width=398&amp;trim=1,1&amp;bg-color=000&amp;pad=1,1 400w, https:\/\/www.cloudsavvyit.com\/p\/uploads\/2021\/11\/c73ebab4.jpg?width=1198&amp;trim=1,1&amp;bg-color=000&amp;pad=1,1 1200w\" sizes=\"auto, 400w, 1200w\" src=\"https:\/\/www.cloudsavvyit.com\/p\/uploads\/2021\/11\/c73ebab4.jpg?width=1198&amp;trim=1,1&amp;bg-color=000&amp;pad=1,1\" alt=\"Stylized illustration of &quot;DNS&quot; text on a blue circuitry background\" width=\"1200\" height=\"675\" onload=\"pagespeed.lazyLoadImages.loadIfVisibleAndMaybeBeacon(this);\" onerror=\"this.onerror=null;pagespeed.lazyLoadImages.loadIfVisibleAndMaybeBeacon(this);\"\/><figcaption class=\"wp-caption-text\"><span class=\"type:primaryImage imagecredit\"><a rel=\"nofollow noopener\" target=\"_blank\" href=\"https:\/\/www.shutterstock.com\/image-illustration\/3d-rendering-word-bright-yellow-color-634316441\">jivacore\/Shutterstock.com<\/a><\/span><\/figcaption><\/figure>\n<p>Running your own DNS server is a great way to accelerate your network\u2019s responsiveness, reduce your reliance on public infrastructure, and benefit from extra functionality like hostname routing. Here\u2019s how to set up a DNS server on a Linux machine using Dnsmasq.<\/p>\n<h2 id=\"what-is-dns\"><span class=\"ez-toc-section\" id=\"What_Is_DNS\"><\/span>What Is DNS?<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>DNS is the system that translates a domain name like <code>example.com<\/code> to the numerical IP address of its server. This could look like <code>127.0.0.1<\/code>. Whenever you make a network request using a domain name, your system will perform a DNS lookup to determine the server address it should contact.<\/p>\n<p>This adds an overhead to every request you make. Although your device will cache DNS responses, visits to new domains will incur a DNS round-<a href=\"https:\/\/buradabiliyorum.com\/en\/category\/trip-and-travel\/\" data-internallinksmanager029f6b8e52c=\"10\" title=\"Trip &amp; Travel\" target=\"_blank\" rel=\"noopener\">trip<\/a> before the actual request begins. This occurs at the level of the OS networking stack, invisible to you as the user.<\/p>\n<p>ISPs usually run DNS servers. You\u2019re probably relying on your ISP\u2019s server if you\u2019re using default settings on your router and devices. Other public DNS servers are available from providers such as <a rel=\"nofollow noopener\" target=\"_blank\" href=\"https:\/\/www.cloudflare.com\/en-gb\/dns\">Cloudflare<\/a> and <a rel=\"nofollow noopener\" target=\"_blank\" href=\"https:\/\/developers.google.com\/speed\/public-dns\">Google<\/a>.<\/p>\n<h2 id=\"why-run-your-own-dns\"><span class=\"ez-toc-section\" id=\"Why_Run_Your_Own_DNS\"><\/span>Why Run Your Own DNS?<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Running your own DNS server gives you more control over your network. One common motivation is being able to configure network-level domain m<a href=\"https:\/\/buradabiliyorum.com\/en\/category\/download-scripts-themes-apps\/\" data-internallinksmanager029f6b8e52c=\"9\" title=\"Download Scripts &amp; Themes &amp; Apps\" target=\"_blank\" rel=\"noopener\">app<\/a>ings, such as <code>web-server<\/code> to <code>192.168.0.101<\/code>. Configuring your router to use your DNS would result in any of your connected devices being able to access <code>192.168.0.101<\/code> via <code>http:\/\/web-server<\/code>.<\/p>\n<p>Having your own DNS server lets you centralize settings into one location instead of applying them individually in <code>\/etc\/hosts<\/code> on each device. They\u2019ll apply to everything you connect to your network, including embedded hardware which provides no other way to customize its routing stack.<\/p>\n<p>An in-house DNS server can also improve performance and provide an extra layer of resilience. Wide-scale DNS outages <a rel=\"nofollow noopener\" target=\"_blank\" href=\"https:\/\/techcrunch.com\/2021\/07\/22\/a-dns-outage-just-took-down-a-good-chunk-of-the-internet\">are not unheard of<\/a>; using a custom server with a long-lived cache for critical services you interact with could help you ride out downtime at your selected upstream provider.<\/p>\n<h2 id=\"dns-with-dnsmasq\"><span class=\"ez-toc-section\" id=\"DNS_With_Dnsmasq\"><\/span>DNS With Dnsmasq<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p><a rel=\"nofollow noopener\" target=\"_blank\" href=\"https:\/\/redirect.viglink.com\/?key=204a528a336ede4177fff0d84a044482&amp;u=https%3A%2F%2Fthekelleys.org.uk%2Fdnsmasq%2Fdoc.html\">Dnsmasq<\/a> is a lightweight DNS server that\u2019s included with most Linux distributions. It\u2019s also refreshingly simple to configure.<\/p>\n<p>Before starting out, it\u2019s worth thinking about what functionality you need your DNS server to provide. In this guide, we\u2019ll look at setting up Dnsmasq with local caching, some custom domain routes, and Google\u2019s <code>8.8.8.8<\/code> as our upstream DNS provider.<\/p>\n<p>The routing flow will look like this:<\/p>\n<ul>\n<li>Network router receives a request from one of your connected devices. The router will be configured to use the Dnsmasq host as its DNS server.<\/li>\n<li>Dnsmasq will check whether it has a defined route for the domain name, such as <code>web-server<\/code> to <code>192.168.0.101<\/code>. If the request was for <code>http:\/\/web-server\/example-page<\/code>, it will send <code>192.168.0.101<\/code> back to the router.<\/li>\n<li>When Dnsmasq has no matching route, it will forward the DNS request to Google\u2019s <code>8.8.8.8<\/code>, enabling resolution on the public internet. This ensures you can still reach the wider web when using your own DNS.<\/li>\n<\/ul>\n<p>You won\u2019t need to make any config changes on your client devices. Everything behind your router will end up making DNS queries via Dnsmasq. However, it is worth noting that all popular desktop and mobile operating systems support setting a DNS server, so you could configure individual devices to use Dnsmasq without enabling it at the router level.<\/p>\n<h2 id=\"getting-started\"><span class=\"ez-toc-section\" id=\"Getting_Started\"><\/span>Getting Started<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>We\u2019ll assume you\u2019ve already got a functioning Linux machine ready to host Dnsmasq. Dnsmasq is not particularly resource-intensive \u2013 if you\u2019ve got few client devices, it will easily run on a Raspberry Pi.<\/p>\n<p>Your host should have a <a rel=\"nofollow noopener\" target=\"_blank\" href=\"https:\/\/www.howtogeek.com\/howto\/ubuntu\/change-ubuntu-server-from-dhcp-to-a-static-ip-address\">static IP<\/a> assigned. From hereon, the IP <code>192.168.0.1<\/code> refers to the Dnsmasq server.<\/p>\n<p>Make sure Dnsmasq is installed:<\/p>\n<pre># Assuming a Debian system&#13;\napt update&#13;\napt install dnsmasq<\/pre>\n<p>Dnsmasq\u2019s config file is usually located at <code>\/etc\/dnsmasq.conf<\/code>. This is pre-populated with initial settings. Some changes need to be made for Dnsmasq to work effectively in a local network scenario. Run <code>sudo nano \/etc\/dnsmasq.conf<\/code> to open the file, then use the Ctrl+W keyboard shortcut to find and uncomment the following lines:<\/p>\n<pre>#domain-needed&#13;\n#bogus-priv<\/pre>\n<p>Remove the <code>#<\/code> character from the start of each line. Here\u2019s what these settings are enabling:<\/p>\n<ul>\n<li><strong><code>domain-needed<\/code><\/strong> \u2013 This stops Dnsmasq from forwarding local names without a domain part to the upstream DNS server. In our installation, it means <code>example.com<\/code> will be eligible for resolution via Google but <code>example<\/code> or <code>web-server<\/code> will not. It reserves dot-less names for your local network.<\/li>\n<li><strong><code>bogus-priv<\/code><\/strong> \u2013 Prevents forwarding DNS reverse-lookup queries to the upstream DNS server. It means internal IPs like <code>192.168.0.101<\/code> will never be exposed to Google. Not enabling this could unintentionally leak the architecture of your internal network to your upstream provider.<\/li>\n<\/ul>\n<p>To set your upstream DNS server, add a new line to your config file:<\/p>\n<pre>server=8.8.8.8&#13;\nserver=4.4.4.4<\/pre>\n<p>This instructs Dnsmasq to forward unresolved queries to <code>8.8.8.8<\/code>. If that server\u2019s unavailable, <code>4.4.4.4<\/code> will be used instead. These addresses are the primary and secondary resolvers for Google\u2019s DNS service.<\/p>\n<p>Next adjust the cache size. This defaults to a relatively low value of 150 cached requests. Increasing this will let Dnsmasq serve more lookups from the cache, reducing network latency. Find the <code>cache-size<\/code> line, uncomment it, and change its value:<\/p>\n<pre>cache-size=1000<\/pre>\n<p>Save and close the file now.<\/p>\n<h2 id=\"mapping-hostnames-to-ips\"><span class=\"ez-toc-section\" id=\"Mapping_Hostnames_to_IPs\"><\/span>Mapping Hostnames to IPs<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>There are a few different ways to map hostnames to their IP addresses. The simplest is to add entries to your server\u2019s existing <code>\/etc\/hosts<\/code> file. Dnsmasq automatically loads the rules from this file as part of its default configuration.<\/p>\n<p>Open <code>\/etc\/hosts<\/code> and add your routes to the bottom of the file. The IP address comes first, followed by the name to assign:<\/p>\n<pre>192.168.0.101 web-server&#13;\n192.168.0.105 gateway.lan<\/pre>\n<p>These lines mean any request to <code>http:\/\/web-server<\/code> will be directed to <code>192.168.0.101<\/code> while <code>http:\/\/gateway.lan<\/code> will end up at <code>192.168.0.5<\/code>. Save and close the file when you\u2019ve finished mapping your devices.<\/p>\n<h2 id=\"testing-your-server\"><span class=\"ez-toc-section\" id=\"Testing_Your_Server\"><\/span>Testing Your Server<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Restart Dnsmasq to apply all your changes:<\/p>\n<pre>sudo service dnsmasq restart<\/pre>\n<p>Check the server\u2019s running correctly:<\/p>\n<pre>sudo service dnsmasq status<\/pre>\n<p>You should see <code>active (running)<\/code> displayed in green. If you don\u2019t, check the log lines at the bottom of the status information to work out what\u2019s wrong.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-14819\" src=\"https:\/\/www.cloudsavvyit.com\/p\/uploads\/2021\/11\/579a47c7.png?trim=1,1&amp;bg-color=000&amp;pad=1,1\" alt=\"\" width=\"1271\" height=\"206\" onload=\"pagespeed.lazyLoadImages.loadIfVisibleAndMaybeBeacon(this);\" onerror=\"this.onerror=null;pagespeed.lazyLoadImages.loadIfVisibleAndMaybeBeacon(this);\"\/><\/p>\n<p>Now you\u2019re ready to test your server. You can make manual DNS lookup attempts with the <code>dig<\/code> tool. You might need to install the <code>dnsutils<\/code> package first.<\/p>\n<pre>dig google.com @localhost&#13;\ndig gateway.lan @localhost<\/pre>\n<p>Both of these commands should show an IP address in the <code>ANSWER SECTION<\/code>. In the case of <code>gateway.lan<\/code>, the result should be <code>192.168.0.5<\/code> according to the routing rule set up in <code>\/etc\/hosts<\/code>. The <code>@localhost<\/code> part of the commands instructs <code>dig<\/code> to query your local DNS server.<\/p>\n<h2 id=\"configuring-your-network\"><span class=\"ez-toc-section\" id=\"Configuring_Your_Network\"><\/span>Configuring Your Network<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>The final step is to configure your network router to make DNS lookups via your Dnsmasq server. The <a rel=\"nofollow noopener\" target=\"_blank\" href=\"https:\/\/www.howtogeek.com\/167533\/the-ultimate-guide-to-changing-your-dns-server\">steps for this<\/a> will vary depending on the routing equipment you\u2019re using.<\/p>\n<p>Once you find the correct settings page, set your server\u2019s IP (<code>192.168.0.1<\/code> in this guide) as the router\u2019s primary DNS server. It\u2019s a good idea to configure a public DNS provider, such as Google\u2019s <code>8.8.8.8<\/code>, as the secondary server. This ensures you\u2019ll still have internet access if your DNS server crashes and goes offline.<\/p>\n<p>Now all the devices connected to your router will make DNS queries via your Dnsmasq instance. They\u2019ll be able to reach your devices by their assigned names, such as <code>web-server<\/code> and <code>gateway.lan<\/code>, and benefit from network-level DNS caching.<\/p>\n<h2 id=\"conclusion\"><span class=\"ez-toc-section\" id=\"Conclusion\"><\/span>Conclusion<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>DNS is an intricate topic but Dnsmasq makes it easy to get a basic server operational. There are many <a rel=\"nofollow noopener\" target=\"_blank\" href=\"https:\/\/redirect.viglink.com\/?key=204a528a336ede4177fff0d84a044482&amp;u=https%3A%2F%2Fthekelleys.org.uk%2Fdnsmasq%2Fdocs%2Fdnsmasq-man.html\">more settings<\/a> which you can explore once you\u2019ve got the core functionality working. These let you filter queries, manage relays and proxies, run scripts when events occur, and set up other kinds of DNS record such as MX results for mail servers.<\/p>\n<p>Dnsmasq doesn\u2019t usually need much manual intervention once it\u2019s live. You can monitor logs using <code>service dnsmasq status<\/code> or <code>systemctl status dnsmasq<\/code>. Now you\u2019re ready to benefit from your self-hosted DNS server, maximizing performance and letting you use internal domain names to reach local network devices.\n<\/div>\n<blockquote><p><strong><span style=\"color: #ff6600;\">If you liked the article, do not forget to share it with your friends. Follow us on\u00a0<span style=\"color: #ff0000;\"><a style=\"color: #ff0000;\" href=\"https:\/\/news.google.com\/publications\/CAAqBwgKMLG0nwswvr63Aw\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">Google News<\/a><\/span>\u00a0too, click on the star and choose us from your favorites.<\/span><\/strong><\/p><\/blockquote>\n<blockquote>\n<p style=\"text-align: center;\">For forums sites go to <span style=\"color: #ff9900;\"><a style=\"color: #ff9900;\" href=\"https:\/\/forum.buradabiliyorum.com\/\" target=\"_blank\" rel=\"noopener\">Forum.BuradaBiliyorum.Com<\/a><\/span><\/strong><\/p>\n<\/blockquote>\n<blockquote>\n<p style=\"text-align: center;\"><strong>If you want to read more like this article, you can visit our <span style=\"color: #ff9900;\"><a style=\"color: #ff9900;\" href=\"https:\/\/en.buradabiliyorum.com\/technology\/\" target=\"_blank\" rel=\"noopener\">Technology category.<\/a><\/span><\/strong><\/p>\n<\/blockquote>\n<p><span style=\"color: black;\"><a style=\"color: #ff9900;\" href=\"https:\/\/www.cloudsavvyit.com\/14816\/how-to-run-your-own-dns-server-on-your-local-network\/\" target=\"_blank\" rel=\"noopener\">Source<\/a><\/span><\/p>\n","protected":false},"excerpt":{"rendered":"<p>&#8220;#How to Run Your Own DNS Server on Your Local Network \u2013 CloudSavvy IT&#8221; jivacore\/Shutterstock.com Running your own DNS server is a great way to accelerate your network\u2019s responsiveness, reduce your reliance on public infrastructure, and benefit from extra functionality like hostname routing. Here\u2019s how to set up a DNS server on a Linux machine&#8230;<\/p>\n","protected":false},"author":1,"featured_media":367854,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"fifu_image_url":"https:\/\/www.cloudsavvyit.com\/p\/uploads\/2021\/11\/c73ebab4.jpg","fifu_image_alt":"","footnotes":""},"categories":[18],"tags":[],"class_list":["post-367853","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-technology"],"_links":{"self":[{"href":"https:\/\/buradabiliyorum.com\/en\/wp-json\/wp\/v2\/posts\/367853","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/buradabiliyorum.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/buradabiliyorum.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/buradabiliyorum.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/buradabiliyorum.com\/en\/wp-json\/wp\/v2\/comments?post=367853"}],"version-history":[{"count":0,"href":"https:\/\/buradabiliyorum.com\/en\/wp-json\/wp\/v2\/posts\/367853\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/buradabiliyorum.com\/en\/wp-json\/wp\/v2\/media\/367854"}],"wp:attachment":[{"href":"https:\/\/buradabiliyorum.com\/en\/wp-json\/wp\/v2\/media?parent=367853"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/buradabiliyorum.com\/en\/wp-json\/wp\/v2\/categories?post=367853"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/buradabiliyorum.com\/en\/wp-json\/wp\/v2\/tags?post=367853"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}