{"id":1182,"date":"2026-11-20T02:36:09","date_gmt":"2026-11-20T02:36:09","guid":{"rendered":"https:\/\/windows-vps.org\/blog\/?p=1182"},"modified":"2026-11-20T02:36:09","modified_gmt":"2026-11-20T02:36:09","slug":"windows-vps-domain-controller-dns-time-dependencies","status":"publish","type":"post","link":"https:\/\/windows-vps.org\/blog\/windows-vps-domain-controller-dns-time-dependencies\/","title":{"rendered":"DNS and Time Dependencies When a Windows VPS Hosts a Domain Controller"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Putting a domain controller on a rented Windows server is legal, works, and fails in a handful of very specific ways. Almost none of those ways involve Active Directory itself. They involve the two services a DC treats as infrastructure it can trust without question: DNS and time. Get either wrong and the symptoms surface somewhere else entirely \u2014 as a workstation that cannot join, a replication partner that reports 8524, or a GPO that refuses to apply.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This article is about those two dependencies, plus the operational differences that a hypervisor introduces. It is not an AD tutorial; it assumes you can promote a server. It also assumes a single-VPS deployment on a host you control \u2014 the kind of small footprint our <a href=\"https:\/\/windows-vps.org\/\">Windows VPS hosting<\/a> is typically used for, where one VM carries the whole domain.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Why DNS is the real prerequisite<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Active Directory is a DNS application. Every domain controller registers a set of SRV records under <code>_msdcs<\/code>, <code>_sites<\/code>, <code>_tcp<\/code> and <code>_udp<\/code>, and every client finds a logon server by querying those records. If the client is pointed at a public resolver, or at a DNS server that does not host the AD zone, the records do not resolve and the workstation concludes there is no domain.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The failure is confusing because name resolution itself works. The machine can reach the internet, it can ping the DC by IP, but it cannot find <code>_ldap._tcp.dc._msdcs.contoso.local<\/code>. That is the signature of a client pointed at the wrong DNS server, and it accounts for a large share of &#8220;the domain is broken&#8221; reports.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Resolve-DnsName -Name \"_ldap._tcp.dc._msdcs.contoso.local\" -Type SRV\nResolve-DnsName -Name \"contoso.local\" -Type SOA\nGet-DnsClientServerAddress -AddressFamily IPv4 | Select-Object InterfaceAlias, ServerAddresses<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">On the domain controller itself, the NIC should point at <code>127.0.0.1<\/code> as the primary DNS server and at nothing else \u2014 or at loopback first and a second DC second. Pointing a DC at a public resolver creates a circular dependency where the DC needs DNS to start DNS, and it also lets the DC register its SRV records in the wrong place.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Designing the zone and forwarding<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The DC hosts a forward lookup zone for the AD namespace and resolves everything else by forwarding. That split is fundamental: internal names come from the local zone, external names go upstream. Configure forwarders to at least two resolvers, ideally from different operators, so one outage does not take out resolution for the whole domain.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Add-DnsServerForwarder -IPAddress 1.1.1.1, 8.8.8.8 -PassThru\nGet-DnsServerForwarder\n\nGet-DnsServerZone | Select-Object ZoneName, ZoneType, IsDsIntegrated, IsReverseLookupZone\nGet-DnsServerResourceRecord -ZoneName \"contoso.local\" -RRType A | Select-Object HostName, RecordType, TimeToLive<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Two settings earn their keep. First, disable recursion for the AD zone if you ever expose DNS to anything untrusted \u2014 otherwise the DC performs recursion for anyone who asks, which is both a workload risk and an amplification vector. Second, create a reverse lookup zone for your private range; it is not required, but it makes <code>nslookup<\/code> and event log correlation far less painful.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Scavenging deserves a deliberate decision rather than a default. Enable aging and scavenging on the forward zone with a no-refresh interval of seven days and a refresh interval of seven days, and confirm that dynamic updates are set to Secure Only. Without scavenging, stale records accumulate for years; with it misconfigured, records for machines that are legitimately offline for a fortnight disappear.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Set-DnsServerScavenging -ScavengingState $true -ScavengingInterval 7.00:00:00 -ApplyOnAllZones\nSet-DnsServerPrimaryZone -Name \"contoso.local\" -DynamicUpdate Secure\nSet-DnsServerZoneAging -Name \"contoso.local\" -Aging $true -NoRefreshInterval 7.00:00:00 -RefreshInterval 7.00:00:00<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Time: the PDC emulator owns the forest clock<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Kerberos tolerates five minutes of skew. A domain controller that is more than a few minutes off true time cannot authenticate clients, and the errors it produces \u2014 4771, 4776, KRB_AP_ERR_SKEW \u2014 do not mention the clock. The DC that holds the PDC emulator role is the authority for the whole forest, and it has to get its time from something external.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>REM run only on the PDC emulator\nw32tm \/config \/manualpeerlist:\"time.cloudflare.com,0x8 time.google.com,0x8\" \/syncfromflags:manual \/reliable:yes \/update\nRestart-Service w32time\nw32tm \/resync\nw32tm \/query \/status\n\nREM every other DC and member: leave W32Time at its default and let the hierarchy work<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Confirm which DC holds the role before running any of that. On a single-DC domain it is trivially the one server, but on a small multi-DC setup it is an easy mistake to configure every DC against public NTP, which produces internal disagreement and intermittent ticket failures.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Get-ADDomain | Select-Object PDCEmulator\nnetdom query fsmo\nw32tm \/query \/source<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">There is a second, subtler interaction. A virtual machine that is suspended and resumed, or restored from a snapshot, comes back with the guest clock where it was at suspend time. If that gap is large, the DC will be serving wrong time to the entire domain until it resyncs. After any snapshot restore, force a resync on the restored machine before letting it serve clients.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What a hypervisor does to a DC<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Three virtualisation-specific hazards apply. Host time synchronisation integration services can fight W32Time; on a DC, disable host time sync and let the DC&#8217;s own configuration own the clock. Snapshot restores can resurrect a DC with a stale USN rollback state, which requires reinitialising the database. And disk-level snapshot backups that are not VSS-aware can capture the AD database mid-write.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>dcdiag \/test:replications \/v\ndcdiag \/test:dns \/v \/e\nrepadmin \/showrepl\n\nREM if a snapshot restore caused USN rollback\nntdsutil \"activate instance ntds\" files \"info\" quit quit<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The USN rollback case is the one worth losing sleep over on an inexpensive host, because it is silent. A DC restored to an earlier state can keep serving authentication while its replication partners reject its changes, and the domain quietly diverges. If you snapshot a DC, treat the restore as a disaster-recovery event with a full verification pass afterwards, not as a fast undo.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">A single-DC domain: what changes<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">One DC means no replication to disagree with, no FSMO transfers, and no site link topology. It also means a reboot is a full authentication outage and a restore is a restore of the whole identity system. Size the maintenance window accordingly, and accept that the box must be treated as production-critical.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Two habits make a single-DC domain tolerable. First, do not put anything else on the machine if you can avoid it \u2014 a server that is both a DC and an application host complicates both roles. Second, keep a second DC on different infrastructure, even a cheap one, if you can afford the licence. If not, make sure the system state backup is current and restore has been tested at least once.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>wbadmin start systemstatebackup -backupTarget:E:\\ -quiet\nwbadmin get versions -backupTarget:E:\\\n\nGet-WindowsFeature AD-Domain-Services, DNS | Select-Object Name, InstallState<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">System state is the correct backup unit for a DC. It captures NTDS.dit together with the registry, SYSVOL and the boot files needed to bring the role back. A file copy of <code>NTDS.dit<\/code> while the service is running is not a backup, and a restored copy that was never tested is only a hypothesis. Our notes on backup target design on a <a href=\"https:\/\/windows-vps.org\/\">low-cost Windows server<\/a> cover the offsite side of this.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Exposure: this machine should not face the internet<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A DC exposes LDAP, Kerberos, SMB, RPC and DNS. None of those belong on a public IP. If the host is internet-facing, the minimum is a provider firewall allowing RDP from a known allowlist, plus local firewall rules scoping LDAP and SMB to the VPN or private network that clients arrive from.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Get-NetFirewallProfile | Select-Object Name, Enabled, DefaultInboundAction\nGet-NetTCPConnection -State Listen | Where-Object LocalPort -in 53,88,389,445,135,3389 |\n  Select-Object LocalAddress, LocalPort, OwningProcess\n\nNew-NetFirewallRule -DisplayName \"LDAP from VPN\" -Direction Inbound -Protocol TCP `\n  -LocalPort 389,636 -RemoteAddress 10.20.0.0\/24 -Action Allow<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The realistic architecture is a DC with no public services at all, reachable only through a VPN endpoint on the same VPS or an RD Gateway host. Clients then point at it for DNS over the tunnel. This costs one extra role and removes an entire class of exposure.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Monitoring the two dependencies<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Add two checks to whatever monitoring you already run: DNS SRV resolution of your own domain, and clock offset on the PDC. Both are trivial to script and both fail before anything else does.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># DNS health\nResolve-DnsName \"_ldap._tcp.dc._msdcs.contoso.local\" -Type SRV -Server 127.0.0.1 -ErrorAction Stop\n\n# Clock offset, parsed from stripchart\nw32tm \/stripchart \/computer:time.cloudflare.com \/samples:3 \/dataonly\n\n# Recent AD-relevant errors\nGet-WinEvent -FilterHashtable @{LogName='Directory Service'; Level=1,2} -MaxEvents 20 |\n  Select-Object TimeCreated, Id, Message<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Directory Service event IDs 1863, 2089 and 1311 all point at connectivity or replication problems that begin as name-resolution failures. Watching for them directly is more reliable than waiting for a user to report that group policy has stopped applying.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Treat the DC as the one machine on the account whose DNS and time configuration is not negotiable. Loopback DNS, forwarding upstream, external NTP on the PDC only, host time sync disabled, system state backups tested, and no public service exposure. Every one of those is a five-minute change that prevents a failure mode with an eight-hour debugging tail.<\/p>\n\n","protected":false},"excerpt":{"rendered":"<p>Putting a domain controller on a rented Windows server is legal, works, and fails in a handful of very specific ways. Almost none of those ways involve Active Directory itself. They involve the two services a DC treats as infrastructure it can trust without question: DNS and time. Get either wrong and the symptoms surface &#8230; <a title=\"DNS and Time Dependencies When a Windows VPS Hosts a Domain Controller\" class=\"read-more\" href=\"https:\/\/windows-vps.org\/blog\/windows-vps-domain-controller-dns-time-dependencies\/\" aria-label=\"Read more about DNS and Time Dependencies When a Windows VPS Hosts a Domain Controller\">Read more<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":2,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-1182","post","type-post","status-publish","format-standard","hentry","category-reviews"],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v26.1 (Yoast SEO v26.1) - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>DNS and Time Dependencies When a Windows VPS Hosts a Domain Controller - Windows VPS Blog<\/title>\n<meta name=\"description\" content=\"Putting a domain controller on a rented Windows server is legal, works, and fails in a handful of very specific ways. Almost none of those ways involve\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/windows-vps.org\/blog\/windows-vps-domain-controller-dns-time-dependencies\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"DNS and Time Dependencies When a Windows VPS Hosts a Domain Controller\" \/>\n<meta property=\"og:description\" content=\"DNS and Time Dependencies When a Windows VPS Hosts a Domain Controller\" \/>\n<meta property=\"og:url\" content=\"https:\/\/windows-vps.org\/blog\/windows-vps-domain-controller-dns-time-dependencies\/\" \/>\n<meta property=\"og:site_name\" content=\"Windows VPS Blog\" \/>\n<meta property=\"article:published_time\" content=\"2026-11-20T02:36:09+00:00\" \/>\n<meta name=\"author\" content=\"windows-vps\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@myxiechengxuan\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"windows-vps\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"8 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/windows-vps.org\/blog\/windows-vps-domain-controller-dns-time-dependencies\/\",\"url\":\"https:\/\/windows-vps.org\/blog\/windows-vps-domain-controller-dns-time-dependencies\/\",\"name\":\"DNS and Time Dependencies When a Windows VPS Hosts a Domain Controller - Windows VPS Blog\",\"isPartOf\":{\"@id\":\"https:\/\/windows-vps.org\/blog\/#website\"},\"datePublished\":\"2026-11-20T02:36:09+00:00\",\"author\":{\"@id\":\"https:\/\/windows-vps.org\/blog\/#\/schema\/person\/44caceed916d0db318aa08d5623a7a58\"},\"description\":\"Putting a domain controller on a rented Windows server is legal, works, and fails in a handful of very specific ways. Almost none of those ways involve\",\"breadcrumb\":{\"@id\":\"https:\/\/windows-vps.org\/blog\/windows-vps-domain-controller-dns-time-dependencies\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/windows-vps.org\/blog\/windows-vps-domain-controller-dns-time-dependencies\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/windows-vps.org\/blog\/windows-vps-domain-controller-dns-time-dependencies\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/windows-vps.org\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"DNS and Time Dependencies When a Windows VPS Hosts a Domain Controller\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/windows-vps.org\/blog\/#website\",\"url\":\"https:\/\/windows-vps.org\/blog\/\",\"name\":\"Windows VPS Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/windows-vps.org\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/windows-vps.org\/blog\/#\/schema\/person\/44caceed916d0db318aa08d5623a7a58\",\"name\":\"windows-vps\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/windows-vps.org\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/3f2573db5afcd1a6ab9abcc5d48fc8e42584bc87ab9d98cc156e5b2097766dd9?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/3f2573db5afcd1a6ab9abcc5d48fc8e42584bc87ab9d98cc156e5b2097766dd9?s=96&d=mm&r=g\",\"caption\":\"windows-vps\"},\"sameAs\":[\"https:\/\/windows-vps.org\/blog\",\"https:\/\/x.com\/myxiechengxuan\"],\"url\":\"https:\/\/windows-vps.org\/blog\/author\/myxiechengxuan\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"DNS and Time Dependencies When a Windows VPS Hosts a Domain Controller - Windows VPS Blog","description":"Putting a domain controller on a rented Windows server is legal, works, and fails in a handful of very specific ways. Almost none of those ways involve","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/windows-vps.org\/blog\/windows-vps-domain-controller-dns-time-dependencies\/","og_locale":"en_US","og_type":"article","og_title":"DNS and Time Dependencies When a Windows VPS Hosts a Domain Controller","og_description":"DNS and Time Dependencies When a Windows VPS Hosts a Domain Controller","og_url":"https:\/\/windows-vps.org\/blog\/windows-vps-domain-controller-dns-time-dependencies\/","og_site_name":"Windows VPS Blog","article_published_time":"2026-11-20T02:36:09+00:00","author":"windows-vps","twitter_card":"summary_large_image","twitter_creator":"@myxiechengxuan","twitter_misc":{"Written by":"windows-vps","Est. reading time":"8 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/windows-vps.org\/blog\/windows-vps-domain-controller-dns-time-dependencies\/","url":"https:\/\/windows-vps.org\/blog\/windows-vps-domain-controller-dns-time-dependencies\/","name":"DNS and Time Dependencies When a Windows VPS Hosts a Domain Controller - Windows VPS Blog","isPartOf":{"@id":"https:\/\/windows-vps.org\/blog\/#website"},"datePublished":"2026-11-20T02:36:09+00:00","author":{"@id":"https:\/\/windows-vps.org\/blog\/#\/schema\/person\/44caceed916d0db318aa08d5623a7a58"},"description":"Putting a domain controller on a rented Windows server is legal, works, and fails in a handful of very specific ways. Almost none of those ways involve","breadcrumb":{"@id":"https:\/\/windows-vps.org\/blog\/windows-vps-domain-controller-dns-time-dependencies\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/windows-vps.org\/blog\/windows-vps-domain-controller-dns-time-dependencies\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/windows-vps.org\/blog\/windows-vps-domain-controller-dns-time-dependencies\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/windows-vps.org\/blog\/"},{"@type":"ListItem","position":2,"name":"DNS and Time Dependencies When a Windows VPS Hosts a Domain Controller"}]},{"@type":"WebSite","@id":"https:\/\/windows-vps.org\/blog\/#website","url":"https:\/\/windows-vps.org\/blog\/","name":"Windows VPS Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/windows-vps.org\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/windows-vps.org\/blog\/#\/schema\/person\/44caceed916d0db318aa08d5623a7a58","name":"windows-vps","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/windows-vps.org\/blog\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/3f2573db5afcd1a6ab9abcc5d48fc8e42584bc87ab9d98cc156e5b2097766dd9?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/3f2573db5afcd1a6ab9abcc5d48fc8e42584bc87ab9d98cc156e5b2097766dd9?s=96&d=mm&r=g","caption":"windows-vps"},"sameAs":["https:\/\/windows-vps.org\/blog","https:\/\/x.com\/myxiechengxuan"],"url":"https:\/\/windows-vps.org\/blog\/author\/myxiechengxuan\/"}]}},"_links":{"self":[{"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/posts\/1182","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/comments?post=1182"}],"version-history":[{"count":1,"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/posts\/1182\/revisions"}],"predecessor-version":[{"id":1185,"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/posts\/1182\/revisions\/1185"}],"wp:attachment":[{"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/media?parent=1182"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/categories?post=1182"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/tags?post=1182"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}