{"id":1423,"date":"2025-11-06T16:41:42","date_gmt":"2025-11-06T13:41:42","guid":{"rendered":"https:\/\/www.dchost.com\/blog\/the-friendly-guide-to-private-nameservers-and-glue-records-step%e2%80%91by%e2%80%91step-setup\/"},"modified":"2025-11-06T16:41:42","modified_gmt":"2025-11-06T13:41:42","slug":"the-friendly-guide-to-private-nameservers-and-glue-records-step%e2%80%91by%e2%80%91step-setup","status":"publish","type":"post","link":"https:\/\/www.dchost.com\/blog\/en\/the-friendly-guide-to-private-nameservers-and-glue-records-step%e2%80%91by%e2%80%91step-setup\/","title":{"rendered":"The Friendly Guide to Private Nameservers and Glue Records: Step\u2011by\u2011Step Setup"},"content":{"rendered":"<div class=\"dchost-blog-content-wrapper\"><div id=\"toc_container\" class=\"toc_transparent no_bullets\"><p class=\"toc_title\">\u0130&ccedil;indekiler<\/p><ul class=\"toc_list\"><li><a href=\"#So_About_That_Time_My_DNS_Went_Quiet\"><span class=\"toc_number toc_depth_1\">1<\/span> So, About That Time My DNS Went Quiet\u2026<\/a><\/li><li><a href=\"#Private_Nameservers_and_Glue_Records_The_Story_Behind_the_Jargon\"><span class=\"toc_number toc_depth_1\">2<\/span> Private Nameservers and Glue Records: The Story Behind the Jargon<\/a><\/li><li><a href=\"#What_You_Need_Before_You_Start\"><span class=\"toc_number toc_depth_1\">3<\/span> What You Need Before You Start<\/a><\/li><li><a href=\"#Step-by-Step_How_to_Set_Up_Private_Nameservers_and_Glue_Records\"><span class=\"toc_number toc_depth_1\">4<\/span> Step-by-Step: How to Set Up Private Nameservers and Glue Records<\/a><ul><li><a href=\"#Step_1_Choose_your_names\"><span class=\"toc_number toc_depth_2\">4.1<\/span> Step 1: Choose your names<\/a><\/li><li><a href=\"#Step_2_Assign_IPs\"><span class=\"toc_number toc_depth_2\">4.2<\/span> Step 2: Assign IPs<\/a><\/li><li><a href=\"#Step_3_Register_glue_at_your_registrar\"><span class=\"toc_number toc_depth_2\">4.3<\/span> Step 3: Register glue at your registrar<\/a><\/li><li><a href=\"#Step_4_Set_your_domains_nameservers_to_your_private_pair\"><span class=\"toc_number toc_depth_2\">4.4<\/span> Step 4: Set your domain\u2019s nameservers to your private pair<\/a><\/li><li><a href=\"#Step_5_Create_the_DNS_zone_on_your_server_and_add_the_right_records\"><span class=\"toc_number toc_depth_2\">4.5<\/span> Step 5: Create the DNS zone on your server and add the right records<\/a><\/li><li><a href=\"#Step_6_Check_firewall_and_service\"><span class=\"toc_number toc_depth_2\">4.6<\/span> Step 6: Check firewall and service<\/a><\/li><li><a href=\"#Step_7_Test_resolution_and_delegation\"><span class=\"toc_number toc_depth_2\">4.7<\/span> Step 7: Test resolution and delegation<\/a><\/li><\/ul><\/li><li><a href=\"#Timing_TTLs_and_Propagation_Without_Panic\"><span class=\"toc_number toc_depth_1\">5<\/span> Timing, TTLs, and Propagation Without Panic<\/a><\/li><li><a href=\"#Platform_Notes_cPanel_Plesk_DirectAdmin_and_Plain_BIND\"><span class=\"toc_number toc_depth_1\">6<\/span> Platform Notes: cPanel, Plesk, DirectAdmin, and Plain BIND<\/a><\/li><li><a href=\"#IPv6_DNSSEC_and_Other_GrownUp_Details\"><span class=\"toc_number toc_depth_1\">7<\/span> IPv6, DNSSEC, and Other Grown\u2011Up Details<\/a><\/li><li><a href=\"#Troubleshooting_The_Usual_Suspects\"><span class=\"toc_number toc_depth_1\">8<\/span> Troubleshooting: The Usual Suspects<\/a><\/li><li><a href=\"#Operational_Tips_Keeping_Your_Private_Nameservers_Happy\"><span class=\"toc_number toc_depth_1\">9<\/span> Operational Tips: Keeping Your Private Nameservers Happy<\/a><\/li><li><a href=\"#A_Quick_Reality_Check_When_It_Doesnt_Work_the_First_Time\"><span class=\"toc_number toc_depth_1\">10<\/span> A Quick Reality Check: When It Doesn\u2019t Work the First Time<\/a><\/li><li><a href=\"#WrapUp_Your_Nameservers_Your_Rules\"><span class=\"toc_number toc_depth_1\">11<\/span> Wrap\u2011Up: Your Nameservers, Your Rules<\/a><\/li><\/ul><\/div>\n<h2 id=\"section-1\"><span id=\"So_About_That_Time_My_DNS_Went_Quiet\">So, About That Time My DNS Went Quiet\u2026<\/span><\/h2>\n<p>I still remember a Tuesday morning when a client pinged me with that familiar \u201csite down?\u201d tone. They\u2019d just migrated to a shiny new <a href=\"https:\/\/www.dchost.com\/vps\">VPS<\/a>, set their own branded nameservers, and felt great about it\u2014until nothing resolved. Not the homepage, not email, not even a ping. We checked the server. Rock solid. We checked their registrar. Nameservers set. Then it hit me: they\u2019d created private nameservers but forgot the glue records. The internet had no idea where their nameservers lived, and everything stalled in a friendly little loop.<\/p>\n<p>Ever had that moment when your domain won\u2019t resolve after a move, and it feels like the whole web is ignoring you? The fix usually starts with understanding <strong>private nameservers<\/strong> and <strong>glue records<\/strong>. In this guide, I\u2019ll walk you through what they are, why they matter, and exactly how to set them up without losing a day to DNS mysteries. We\u2019ll go step by step, talk through real-world gotchas, and I\u2019ll share the little checks I run to make sure things actually stick. If you\u2019ve been meaning to finally \u201cdo it right\u201d with your DNS and brand your own nameservers, this one\u2019s for you.<\/p>\n<h2 id=\"section-2\"><span id=\"Private_Nameservers_and_Glue_Records_The_Story_Behind_the_Jargon\">Private Nameservers and Glue Records: The Story Behind the Jargon<\/span><\/h2>\n<p>Let\u2019s keep this human. Private nameservers are just nameservers branded on your domain\u2014think <strong>ns1.yourdomain.com<\/strong> and <strong>ns2.yourdomain.com<\/strong>\u2014instead of using your host\u2019s defaults. It\u2019s tidy, professional, and helpful when you\u2019re hosting multiple projects or acting as a reseller. You control your DNS stack, and you get that sleek, white-label feel without shouting someone else\u2019s brand.<\/p>\n<p>Now, glue records. Here\u2019s the thing: if your nameserver name lives under the very domain it serves\u2014like <em>ns1.yourdomain.com<\/em> serving <em>yourdomain.com<\/em>\u2014resolvers hit a chicken-and-egg problem. They ask the parent (the TLD registry and your registrar) \u201cWhere\u2019s this domain\u2019s nameserver?\u201d and get the nameserver\u2019s name back. But then they need to resolve that nameserver\u2019s name to an IP, which\u2026 needs the zone itself to resolve. Oops.<\/p>\n<p>Glue records are the fix. They\u2019re little pieces of IP information the parent zone hangs onto saying: \u201cBy the way, <strong>ns1.yourdomain.com<\/strong> is at <strong>203.0.113.10<\/strong> and <strong>ns2.yourdomain.com<\/strong> is at <strong>203.0.113.11<\/strong>.\u201d That gets resolvers through the door without looping. Think of glue like a handwritten note on the front desk telling couriers which elevator to take when the receptionist\u2019s phone is down.<\/p>\n<p>If you\u2019re curious about the bigger map in the sky, the <a href=\"https:\/\/www.iana.org\/domains\/root\/servers\" rel=\"nofollow noopener\" target=\"_blank\">IANA root servers<\/a> coordinate the very top of the DNS tree. But for your domain, the real magic happens at your registrar: you \u201cregister\u201d your hostnames (ns1, ns2) and give them IPs. That\u2019s glue.<\/p>\n<h2 id=\"section-3\"><span id=\"What_You_Need_Before_You_Start\">What You Need Before You Start<\/span><\/h2>\n<p>I\u2019ve set up private nameservers on countless stacks\u2014cPanel\/WHM, Plesk, DirectAdmin, straight BIND or PowerDNS\u2014and the prerequisites are always the same. First, you need a domain you own, and access to its registrar. Second, a server with a static IPv4 address (and ideally a second IP, or even a second server for resilience). Third, the ability to run an <strong>authoritative DNS server<\/strong> on that machine or use DNS software that\u2019s configured to serve your zones. Optional but recommended: an IPv6 address for each nameserver if you\u2019ve got v6 routes. One more thing: firewall access to open UDP and TCP 53 is essential. I\u2019ve watched that small omission chew up hours.<\/p>\n<p>And just a quick note\u2014reverse DNS (rDNS) on your server IPs is not required for glue or authority. It\u2019s great for mail deliverability. Helpful, sure. Just not part of the glue story.<\/p>\n<h2 id=\"section-4\"><span id=\"Step-by-Step_How_to_Set_Up_Private_Nameservers_and_Glue_Records\">Step-by-Step: How to Set Up Private Nameservers and Glue Records<\/span><\/h2>\n<p>Let\u2019s walk through the whole journey in the same order I use for real migrations. We\u2019ll keep it platform-agnostic so the logic sticks no matter which panel or DNS software you use.<\/p>\n<h3><span id=\"Step_1_Choose_your_names\">Step 1: Choose your names<\/span><\/h3>\n<p>Pick your branded hostnames, usually <strong>ns1.yourdomain.com<\/strong> and <strong>ns2.yourdomain.com<\/strong>. If you\u2019ve only got one server, you can temporarily point both to the same IP, though it\u2019s better to separate them when possible. For long-term sturdiness, I like true diversity: two IPs, two servers, ideally in different networks. But start simple if you need to.<\/p>\n<h3><span id=\"Step_2_Assign_IPs\">Step 2: Assign IPs<\/span><\/h3>\n<p>Decide which IPs will power these nameservers. Typically that\u2019s your server\u2019s primary IPv4 and either a secondary IPv4 or an IP on a different machine. If you have IPv6, earmark v6 addresses too so you can add AAAA glue later. Jot them down. You\u2019ll use them twice\u2014once at your registrar and once in your DNS zone.<\/p>\n<h3><span id=\"Step_3_Register_glue_at_your_registrar\">Step 3: Register glue at your registrar<\/span><\/h3>\n<p>This happens in a section often called \u201cHost records,\u201d \u201cChild nameservers,\u201d or \u201cRegister nameserver.\u201d You\u2019ll create <strong>ns1.yourdomain.com<\/strong> \u2192 <strong>IPv4\/IPv6<\/strong> and <strong>ns2.yourdomain.com<\/strong> \u2192 <strong>IPv4\/IPv6<\/strong>. Save. Some registrars apply it instantly; others can take a few minutes to populate. If you haven\u2019t seen this screen before, check your registrar\u2019s docs or look up a vendor neutral explanation like <a href=\"https:\/\/developers.cloudflare.com\/dns\/glossary\/glue-record\/\" rel=\"nofollow noopener\" target=\"_blank\">what a glue record is and why it exists<\/a>. It\u2019ll click fast once you see it laid out.<\/p>\n<h3><span id=\"Step_4_Set_your_domains_nameservers_to_your_private_pair\">Step 4: Set your domain\u2019s nameservers to your private pair<\/span><\/h3>\n<p>Still at the registrar, switch the domain\u2019s authoritative nameservers to <strong>ns1.yourdomain.com<\/strong> and <strong>ns2.yourdomain.com<\/strong>. This is the delegation change. Without it, the world won\u2019t ask your new DNS server for answers. Don\u2019t worry if things don\u2019t resolve instantly\u2014there\u2019s propagation and caching in the mix. I\u2019ll talk strategy for timing in a minute.<\/p>\n<h3><span id=\"Step_5_Create_the_DNS_zone_on_your_server_and_add_the_right_records\">Step 5: Create the DNS zone on your server and add the right records<\/span><\/h3>\n<p>On your DNS server, create the zone for <strong>yourdomain.com<\/strong>. Make sure it contains: (1) <strong>NS records<\/strong> pointing to <strong>ns1.yourdomain.com<\/strong> and <strong>ns2.yourdomain.com<\/strong>; (2) <strong>A and AAAA records<\/strong> for <strong>ns1<\/strong> and <strong>ns2<\/strong> using the same IPs you used for glue; (3) the rest of your essentials\u2014A\/AAAA for the root domain, a record for <strong>www<\/strong>, MX for email, and anything else your site uses. The key detail is that your zone must reference the same nameserver hostnames and IPs you registered as glue, or resolvers get confused and may mark the delegation lame.<\/p>\n<h3><span id=\"Step_6_Check_firewall_and_service\">Step 6: Check firewall and service<\/span><\/h3>\n<p>Before testing, confirm UDP 53 and TCP 53 are open on the server. Some setups only open UDP and forget TCP, which bites you during large responses and DNSSEC. Also confirm your DNS daemon\u2014BIND, PowerDNS, NSD, or your panel\u2019s embedded service\u2014is running and authoritative for the zone. If your logs say \u201cnot authoritative\u201d for queries to your domain, re-check the zone config.<\/p>\n<h3><span id=\"Step_7_Test_resolution_and_delegation\">Step 7: Test resolution and delegation<\/span><\/h3>\n<p>Now run a quick trace from your local machine or a remote box. Something like <code>dig +trace yourdomain.com<\/code> shows each hop\u2014from root, to your TLD, down to your nameservers. If the glue is correct, you\u2019ll see the parent handing out <em>ns1.yourdomain.com<\/em> and <em>ns2.yourdomain.com<\/em> with their IPs, then your server providing authoritative answers. If it breaks in the middle, that\u2019s a sign the glue isn\u2019t set, the IP is wrong, or your server isn\u2019t reachable. When I want a browser-based visual, I love using <a href=\"https:\/\/dnsviz.net\/\" rel=\"nofollow noopener\" target=\"_blank\">DNSViz<\/a> to map the chain and highlight weak spots like missing A\/AAAA for nameservers or DNSSEC issues.<\/p>\n<h2 id=\"section-5\"><span id=\"Timing_TTLs_and_Propagation_Without_Panic\">Timing, TTLs, and Propagation Without Panic<\/span><\/h2>\n<p>Here\u2019s a little trick I use before big DNS moves: a day or two ahead, I lower TTLs on the old zone so caches refresh quickly when I change delegation. That way, if I need to revert, I\u2019m not waiting hours for stale records to clear. If that kind of timing strategy sounds helpful, I\u2019ve written more about it here: <a href=\"https:\/\/www.dchost.com\/blog\/en\/zero-downtime-tasima-icin-ttl-stratejileri-dns-yayilimini-gercekten-nasil-hizlandirirsin\/\">The TTL Playbook for Zero\u2011Downtime Migrations<\/a>. It\u2019s the calm way to handle DNS without refreshing your browser fifty times.<\/p>\n<p>After you switch your domain\u2019s nameservers to your private pair, remember there\u2019s a separate propagation phase for the <em>delegation<\/em> itself. Caches at resolvers around the world hang on to the old NS set for a while. Usually you\u2019ll see signs of life in minutes, but full consistency can take longer depending on previous TTLs and how widely your domain is queried.<\/p>\n<h2 id=\"section-6\"><span id=\"Platform_Notes_cPanel_Plesk_DirectAdmin_and_Plain_BIND\">Platform Notes: cPanel, Plesk, DirectAdmin, and Plain BIND<\/span><\/h2>\n<p>Each control panel wraps the same DNS fundamentals with slightly different buttons. In <strong>cPanel\/WHM<\/strong>, look for \u201cBasic WebHost Manager Setup\u201d to set your default nameservers and assign IPs. WHM will also help you generate the A records for ns1\/ns2 in your selected DNS zone. Even with that convenience, you still have to register glue at your <em>registrar<\/em>, which is the part many folks miss.<\/p>\n<p>In <strong>Plesk<\/strong>, I usually adjust the DNS Template so new domains pick up the right NS entries, then verify the A\/AAAA records for ns1\/ns2 exist under the main zone. Plesk can run BIND or its internal DNS; whichever it is, make sure it\u2019s listening on the correct IPs and that your firewall permits inbound UDP and TCP 53. Plesk\u2019s event logs are handy if you suspect the service isn\u2019t authoritative.<\/p>\n<p>With <strong>DirectAdmin<\/strong>, the \u201cNameservers\u201d config sets global defaults, while per-domain DNS zones carry the actual NS\/A\/AAAA records. Again, registrar glue registration is non-negotiable so the parent can hand out your IP addresses during delegation.<\/p>\n<p>If you\u2019re running <strong>BIND<\/strong> or <strong>PowerDNS<\/strong> by hand, the flow is the same: create the zone with NS records pointing at your ns1\/ns2 hostnames, add A\/AAAA for those hostnames, and double-check the SOA and serials. I like to keep TTLs modest during the transition, bumping them later for stability once everything is humming.<\/p>\n<h2 id=\"section-7\"><span id=\"IPv6_DNSSEC_and_Other_GrownUp_Details\">IPv6, DNSSEC, and Other Grown\u2011Up Details<\/span><\/h2>\n<p>IPv6 isn\u2019t mandatory for glue, but it\u2019s a nice bonus. If your server has reliable v6 connectivity, add <strong>AAAA glue<\/strong> at the registrar alongside your A glue. Then add the corresponding AAAA records for ns1\/ns2 in your zone. Some resolvers prefer IPv6 when available, so you\u2019re future-proofing and sometimes even improving reachability.<\/p>\n<p>DNSSEC is separate from glue, but they play in the same arena. Glue gets queries to your nameserver; DNSSEC lets resolvers verify the authenticity of your answers. If you enable DNSSEC, you\u2019ll generate DS records and put them into your registrar so the signature chain validates. I tend to roll out DNSSEC after I confirm delegation and authority are solid, because if you sign a broken zone, troubleshooting becomes\u2026 sportier. Get the basics green, then add cryptographic assurance.<\/p>\n<h2 id=\"section-8\"><span id=\"Troubleshooting_The_Usual_Suspects\">Troubleshooting: The Usual Suspects<\/span><\/h2>\n<p>When something feels off, I start with a simple chain check. First, <code>dig NS yourdomain.com +trace<\/code> and watch whether the TLD returns your custom nameservers and their IPs. If it doesn\u2019t show IPs, your glue is missing at the registrar. If it shows IPs but you can\u2019t reach the server, you\u2019re probably dealing with a firewall or a service not listening. If the server answers but says it\u2019s \u201cnot authoritative,\u201d your zone isn\u2019t loaded or delegated correctly on the DNS daemon.<\/p>\n<p>I\u2019ve hit every one of these in real life. A few of my personal \u201cgotchas\u201d to double-check: (1) Did you put A\/AAAA records for ns1 and ns2 <em>inside<\/em> your zone? The glue is just at the parent; your zone must also define these hostnames. (2) Did you change the domain\u2019s nameservers to your private pair? You\u2019d be surprised how often people register glue and forget the delegation. (3) Are you blocking TCP 53? Large responses and DNSSEC need it. (4) Are you editing the right zone file? In panel-based clusters, there can be multiple DNS servers. (5) Did you set very long TTLs right before the move? That can make it feel like nothing is happening, even if everything is correct.<\/p>\n<p>If you want a second opinion beyond your terminal, plug your domain into <a href=\"https:\/\/dnsviz.net\/\" rel=\"nofollow noopener\" target=\"_blank\">DNSViz<\/a>. It\u2019s good at spotting missing records, DS mismatches, and overall delegation health. For reading up on the idea of glue from a vendor-neutral angle, this concise explanation of <a href=\"https:\/\/developers.cloudflare.com\/dns\/glossary\/glue-record\/\" rel=\"nofollow noopener\" target=\"_blank\">glue records and circular dependency<\/a> is a gentle refresher when you\u2019re staring at a blank registrar screen wondering what goes where.<\/p>\n<h2 id=\"section-9\"><span id=\"Operational_Tips_Keeping_Your_Private_Nameservers_Happy\">Operational Tips: Keeping Your Private Nameservers Happy<\/span><\/h2>\n<p>Once things are live, I treat nameservers like foundational infrastructure. Keep them monitored. If you\u2019re running a single box for both ns1 and ns2, plan a second machine when you can; you don\u2019t want a single maintenance reboot to make your entire domain vanish for a few minutes. Keep software updated\u2014BIND, PowerDNS, panel patches\u2014because DNS is a favorite playground for the internet\u2019s curious minds.<\/p>\n<p>Think about your zone\u2019s TTLs. For a stable, rarely changing domain, higher TTLs reduce query load and slightly improve perceived responsiveness. For fast-moving apps or frequent migrations, lower TTLs give you agility. If you\u2019re new to that balancing act, my write-up on <a href=\"https:\/\/www.dchost.com\/blog\/en\/zero-downtime-tasima-icin-ttl-stratejileri-dns-yayilimini-gercekten-nasil-hizlandirirsin\/\">TTL strategies for zero\u2011downtime moves<\/a> shows how to make changes feel \u201cinstant\u201d without drama.<\/p>\n<p>A final thought: private nameservers are about brand and control. If running DNS starts to feel like the tail wagging the dog, it\u2019s okay to use a managed DNS service in front of your infrastructure while keeping your branded ns hostnames. The trick is making sure those hostnames point to a resilient, well-monitored DNS backend\u2014yours or a provider you trust. The goal is predictability. You want to be the person who shrugs at DNS changes and says, \u201cGive it a minute, it\u2019ll land.\u201d<\/p>\n<h2 id=\"section-10\"><span id=\"A_Quick_Reality_Check_When_It_Doesnt_Work_the_First_Time\">A Quick Reality Check: When It Doesn\u2019t Work the First Time<\/span><\/h2>\n<p>One of my clients once set everything perfectly, but the site still wouldn\u2019t resolve from a specific ISP. After a little sleuthing, we realized their previous setup had a comically long TTL at the registrar level for the old delegation. Some resolvers were holding onto it like a precious memory. The fix was patience, plus a temporary A record on the old DNS pointing users to the new web server while caches naturally expired. No heroics, just respecting how caching works in the wild.<\/p>\n<p>That\u2019s the vibe to keep with DNS. Do clean work. Test. Give caches time. Validate with trace and a visualizer. If something feels inconsistent, it\u2019s usually caching, a missing A\/AAAA for your nameserver hostnames, or glue not being registered exactly as your DNS zone expects.<\/p>\n<h2 id=\"section-11\"><span id=\"WrapUp_Your_Nameservers_Your_Rules\">Wrap\u2011Up: Your Nameservers, Your Rules<\/span><\/h2>\n<p>We covered a lot, so let\u2019s tie it together. Private nameservers give you a clean, branded way to run DNS for your domain (and others you host). Glue records are the small but crucial breadcrumbs the parent zone needs so the world can actually find those nameservers without getting lost in a loop. The practical flow is simple: pick ns1\/ns2, assign IPs, register glue at your registrar, delegate your domain to those nameservers, and make sure your DNS zone includes the matching A\/AAAA records and is authoritative.<\/p>\n<p>If you remember just a few things, let them be these: keep your firewall open on UDP and TCP 53; confirm your zone has A\/AAAA for the nameserver hostnames; test with <code>dig +trace<\/code>; and let TTLs work in your favor by planning ahead. The rest is polish\u2014adding IPv6 glue, enabling DNSSEC once things are steady, and growing into a second server for resilience when the time\u2019s right.<\/p>\n<p>Hope this was helpful! If you\u2019re setting this up today and hit a snag, breathe, trace the path, and check the glue. It\u2019s almost always one of those three. See you in the next post\u2014where we\u2019ll take this foundation and build something fast, resilient, and a little bit fun.<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>\u0130&ccedil;indekiler1 So, About That Time My DNS Went Quiet\u20262 Private Nameservers and Glue Records: The Story Behind the Jargon3 What You Need Before You Start4 Step-by-Step: How to Set Up Private Nameservers and Glue Records4.1 Step 1: Choose your names4.2 Step 2: Assign IPs4.3 Step 3: Register glue at your registrar4.4 Step 4: Set your [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":1424,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[26],"tags":[],"class_list":["post-1423","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-teknoloji"],"_links":{"self":[{"href":"https:\/\/www.dchost.com\/blog\/en\/wp-json\/wp\/v2\/posts\/1423","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dchost.com\/blog\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dchost.com\/blog\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/en\/wp-json\/wp\/v2\/comments?post=1423"}],"version-history":[{"count":0,"href":"https:\/\/www.dchost.com\/blog\/en\/wp-json\/wp\/v2\/posts\/1423\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/en\/wp-json\/wp\/v2\/media\/1424"}],"wp:attachment":[{"href":"https:\/\/www.dchost.com\/blog\/en\/wp-json\/wp\/v2\/media?parent=1423"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/en\/wp-json\/wp\/v2\/categories?post=1423"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/en\/wp-json\/wp\/v2\/tags?post=1423"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}