{"id":782,"date":"2026-09-16T13:42:35","date_gmt":"2026-09-16T13:42:35","guid":{"rendered":"https:\/\/www.vps.tc\/blog\/?p=782"},"modified":"2026-09-16T09:41:26","modified_gmt":"2026-09-16T09:41:26","slug":"windows-server-dhcp-setup","status":"publish","type":"post","link":"https:\/\/www.vps.tc\/blog\/en\/windows-server-dhcp-setup\/","title":{"rendered":"How to Install and Configure DHCP on Windows Server"},"content":{"rendered":"<div class=\"aiw-summary\" id=\"aiw-ozet\">\n<p class=\"aiw-summary-title\">Quick Summary &#8211; Windows Server DHCP Setup<\/p>\n<p>A reliable DHCP deployment starts with a clear network plan, not with the role installation wizard. Assign the server a static IP, define the scope carefully, and test the complete client path afterward.<\/p>\n<ul>\n<li><strong>Plan the network<\/strong> \u2014 Record the subnet, gateway, DNS servers, static assignments, and lease duration before installing DHCP.<\/li>\n<li><strong>Install the role<\/strong> \u2014 Use PowerShell or Server Manager, then verify the service and authorize the server when the deployment uses Active Directory.<\/li>\n<li><strong>Create the scope<\/strong> \u2014 Define a valid IPv4 range and keep network, broadcast, and static device addresses out of the dynamic pool.<\/li>\n<li><strong>Set options<\/strong> \u2014 Configure the gateway, reachable DNS servers, domain suffix, and a lease duration suited to the client population.<\/li>\n<li><strong>Add resilience<\/strong> \u2014 Use reservations for predictable client addresses and DHCP failover when one server is not enough.<\/li>\n<li><strong>Test the path<\/strong> \u2014 Verify the client lease, gateway, DNS resolution, bindings, logs, and configuration export.<\/li>\n<\/ul>\n<\/div>\n<p class=\"aiw-lead\">Windows Server DHCP setup is straightforward when the network plan is settled first: give the server a static IP, install and authorize the DHCP role, create a scope, configure gateway and DNS options, then test from a client. Most failures come from wrong bindings, missing relay configuration, or overlapping static addresses-not from the installation command.<\/p>\n<div class=\"aiw-toc\" style=\"border:1px solid #dbe3ea;border-radius:8px;padding:16px 20px;margin:0 0 28px\">\n<p class=\"aiw-toc-head\"><strong>Table of Contents<\/strong><span class=\"aiw-toc-meta\"> \u00b7 12 min read<\/span><\/p>\n<ol style=\"margin:10px 0 0;padding-left:22px\">\n<li><a href=\"#plan-the-network-before-installing-dhcp-on-windows-server\">Plan the network before installing DHCP on Windows Server<\/a><\/li>\n<li><a href=\"#installing-the-dhcp-server-role\">Installing the DHCP Server role<\/a><\/li>\n<li><a href=\"#creating-a-new-dhcp-scope\">Creating a new DHCP scope<\/a><\/li>\n<li><a href=\"#which-values-belong-in-the-scope-options\">Which values belong in the scope options?<\/a><\/li>\n<li><a href=\"#when-should-you-use-a-dhcp-reservation\">When should you use a DHCP reservation?<\/a><\/li>\n<li><a href=\"#configuring-dhcp-failover\">Configuring DHCP failover<\/a><\/li>\n<li><a href=\"#dhcp-security-and-unauthorized-server-checks\">DHCP security and unauthorized server checks<\/a><\/li>\n<li><a href=\"#testing-and-troubleshooting-after-installation\">Testing and troubleshooting after installation<\/a><\/li>\n<li><a href=\"#check-these-before-going-live\">Check These Before Going Live<\/a><\/li>\n<li><a href=\"#frequently-asked-questions\">Frequently Asked Questions<\/a><\/li>\n<li><a href=\"#sources\">Sources<\/a><\/li>\n<\/ol>\n<\/div>\n<h2 id=\"plan-the-network-before-installing-dhcp-on-windows-server\">Plan the network before installing DHCP on Windows Server<\/h2>\n<p>I have seen DHCP installations fail for reasons that had nothing to do with the installation itself. The role was present, the service was running, and clients still received the wrong gateway because another device was answering first. Before you install anything, assign the server a static IP, choose the address pool, and check that no unauthorized DHCP server is active on the same VLAN.<\/p>\n<p>DHCP uses UDP port 68 on the client and UDP port 67 on the server for IPv4. Clients on different VLANs need a DHCP relay configured on the router or Layer 3 switch so their requests can reach the server. The DORA sequence-Discover, Offer, Request, Acknowledge-is the basic address-allocation process described in RFC 2131.<\/p>\n<h3>Information to prepare first<\/h3>\n<ul>\n<li>The DHCP server&#8217;s static IPv4 address<\/li>\n<li>The network block and subnet mask to distribute<\/li>\n<li>Static device addresses that must stay outside the dynamic pool<\/li>\n<li>The default gateway<\/li>\n<li>The IP addresses of internal DNS servers<\/li>\n<li>The domain name and intended lease duration<\/li>\n<\/ul>\n<p>For example, on <code>192.168.10.0\/24<\/code>, you might use <code>192.168.10.1<\/code> as the gateway, allocate <code>192.168.10.50<\/code> through <code>192.168.10.200<\/code>, and define an internal DNS server at <code>192.168.10.2<\/code>. Do not leave the DHCP server itself dependent on DHCP for its address.<\/p>\n<p><strong>What to do<\/strong> &#8211; Write down the network block, gateway, DNS addresses, static assignments, and pool boundaries before you begin.<\/p>\n<div class=\"aiw-callout aiw-callout-tip\">\n<p class=\"aiw-callout-label\">Tip<\/p>\n<p>Keep the scope and static assignments visible in your network documentation. A short written plan prevents the common mistake of putting a printer or server inside the dynamic pool.<\/p>\n<\/div>\n<h2 id=\"installing-the-dhcp-server-role\">Installing the DHCP Server role<\/h2>\n<p>You can install DHCP through Server Manager or PowerShell. I use PowerShell when I expect to repeat the setup, but Server Manager is perfectly reasonable for a one-off deployment. This command installs the role and its management tools:<\/p>\n<pre><code>Install-WindowsFeature DHCP -IncludeManagementTools<\/code><\/pre>\n<p>A <code>Success : True<\/code> result confirms that the role installation completed. The DHCP service is installed at this point, but the server still needs authorization in Active Directory and a configured scope.<\/p>\n<p>Check both the role and service:<\/p>\n<pre><code>Get-WindowsFeature -Name DHCP\nGet-Service -Name DHCPServer<\/code><\/pre>\n<p>On a domain-joined server, DHCP authorization requires suitable Active Directory credentials. After checking the server&#8217;s FQDN and static IP address, you can authorize it from the DHCP console by right-clicking the server name and selecting <code>Authorize<\/code>. The PowerShell equivalent is:<\/p>\n<pre><code>Add-DhcpServerInDC -DnsName \"dhcp01.example.local\" -IpAddress 192.168.10.10\nGet-DhcpServerInDC<\/code><\/pre>\n<p>Authorization applies to Active Directory-integrated DHCP deployments. A workgroup server does not use this authorization process, but it still needs a correct scope, network path, and protection against other DHCP servers.<\/p>\n<p>The Server Manager wizard installs the same role through a graphical interface. After installation, complete the DHCP configuration task shown in the notification area so the required security group and authorization settings are not forgotten.<\/p>\n<p><strong>What to do<\/strong> &#8211; Verify the role, service, FQDN, static address, and authorization state before creating the first scope.<\/p>\n<h2 id=\"creating-a-new-dhcp-scope\">Creating a new DHCP scope<\/h2>\n<p>A scope defines the addresses that may be leased on one network, along with the options distributed with those addresses. Do not confuse the network address with the broadcast address. In <code>192.168.10.0\/24<\/code>, the network address is <code>192.168.10.0<\/code> and the broadcast address is <code>192.168.10.255<\/code>; neither belongs to a client.<\/p>\n<h3>Creating an IPv4 scope with PowerShell<\/h3>\n<pre><code>Add-DhcpServerv4Scope -Name \"Office LAN\" -StartRange 192.168.10.50 -EndRange 192.168.10.200 -SubnetMask 255.255.255.0 -State Active<\/code><\/pre>\n<p>This creates a pool of 151 addresses. The range from <code>192.168.10.1<\/code> through <code>192.168.10.49<\/code> remains outside the pool and can be used for servers, printers, and network devices. Addresses above <code>192.168.10.200<\/code> are outside the pool too, so they do not need to be added as exclusions.<\/p>\n<p>If a reserved address falls inside the scope, exclude it explicitly:<\/p>\n<pre><code>Add-DhcpServerv4ExclusionRange -ScopeId 192.168.10.0 -StartRange 192.168.10.60 -EndRange 192.168.10.60<\/code><\/pre>\n<p>In this example, <code>192.168.10.60<\/code> stays available for a static device. The range must be inside the scope for an exclusion to be useful. I prefer keeping most infrastructure addresses outside the scope, because that makes the design easier to read and reduces the number of rules someone has to remember six months later.<\/p>\n<p>Check separately that statically configured devices do not overlap the DHCP pool. Giving the same IP address to two devices can create unstable ARP behavior and intermittent connectivity; the basics are covered in <a href=\"https:\/\/www.vps.tc\/blog\/en\/what-is-arp-address-resolution-protocol-explained\/\">What Is ARP? Address Resolution Protocol Explained<\/a>.<\/p>\n<p><strong>What to do<\/strong> &#8211; Keep static assignments outside the dynamic pool where possible, and use exclusions for reserved addresses that must remain inside it.<\/p>\n<div class=\"aiw-callout aiw-callout-example\">\n<p class=\"aiw-callout-label\">Example<\/p>\n<p>For 192.168.10.0\/24, a pool from .50 through .200 leaves .1 through .49 and .201 through .254 available for infrastructure. The network and broadcast addresses remain unusable for clients.<\/p>\n<\/div>\n<h2 id=\"which-values-belong-in-the-scope-options\">Which values belong in the scope options?<\/h2>\n<p>An IP address alone is not enough. Without a gateway, a client cannot reach other networks; without DNS, it cannot resolve hostnames. In the Windows DHCP console, these values are configured under <code>Scope Options<\/code>. In PowerShell, use the option command for gateway, DNS, and domain suffix values.<\/p>\n<pre><code>Set-DhcpServerv4OptionValue -ScopeId 192.168.10.0 -Router 192.168.10.1 -DnsServer 192.168.10.2,192.168.10.3 -DnsDomain \"example.local\"<\/code><\/pre>\n<p>DHCP option 003 represents the router, option 006 represents DNS servers, and option 015 represents the DNS domain suffix, as documented in RFC 2132. Use DNS server addresses that clients can actually reach. If you use public DNS, decide separately how internal names will be resolved.<\/p>\n<p>When name resolution fails, first inspect what the client received:<\/p>\n<pre><code>ipconfig \/all\nipconfig \/release\nipconfig \/renew\nnslookup example.local<\/code><\/pre>\n<p>Read the <code>DHCP Enabled<\/code>, <code>IPv4 Address<\/code>, <code>Default Gateway<\/code>, and <code>DNS Servers<\/code> lines together in the <code>ipconfig \/all<\/code> output. Looking only at the IP address gives you an incomplete diagnosis. <a href=\"https:\/\/www.vps.tc\/blog\/en\/how-to-fix-dns-probe-finished-nxdomain-error\/\">What Is DNS_PROBE_FINISHED_NXDOMAIN and How to Fix It<\/a> also explains the basic DNS side of this investigation.<\/p>\n<h3>Choosing the lease duration<\/h3>\n<p>The lease duration determines how long an address remains assigned to a client. Permanently connected desktops may work well with a longer period such as eight days. A guest network, busy wireless network, or network with short-lived devices may be better served by four hours or one day. A lease that is unnecessarily short creates extra DHCP traffic; one that is too long delays the return of unused addresses to the pool.<\/p>\n<pre><code>Set-DhcpServerv4Scope -ScopeId 192.168.10.0 -LeaseDuration 8.00:00:00<\/code><\/pre>\n<p>The value uses the <code>days.hours:minutes:seconds<\/code> format. Changing it does not immediately remove existing leases; clients receive the new duration during a renewal.<\/p>\n<h2 id=\"when-should-you-use-a-dhcp-reservation\">When should you use a DHCP reservation?<\/h2>\n<p>A reservation assigns the same IP address to a particular client identifier each time. It is useful for printers, cameras, IP phones, and management interfaces that should use DHCP but must remain reachable at a predictable address. Unlike a manually configured static IP, the device remains centrally managed through DHCP.<\/p>\n<pre><code>Add-DhcpServerv4Reservation -ScopeId 192.168.10.0 -IPAddress 192.168.10.60 -ClientId \"00-11-22-33-44-55\" -Name \"Office Printer\" -Description \"Accounting printer\"<\/code><\/pre>\n<p>Depending on the Windows Server version and client type, <code>ClientId<\/code> may appear in a format different from the familiar MAC address. Inspect current leases before adding a reservation:<\/p>\n<pre><code>Get-DhcpServerv4Lease -ComputerName dhcp01 -ScopeId 192.168.10.0 | Format-Table IPAddress,ClientId,HostName,AddressState<\/code><\/pre>\n<p>Do not create multiple reservations for the same client identifier. In virtualized environments, inspect the network identities of cloned machines too. Copied MAC addresses can lead to surprising assignments.<\/p>\n<h2 id=\"configuring-dhcp-failover\">Configuring DHCP failover<\/h2>\n<p>If a single DHCP server fails, new clients cannot obtain addresses and existing clients may have trouble renewing their leases. Windows Server DHCP failover lets two DHCP servers share scope information. The two supported operating modes are:<\/p>\n<table>\n<thead>\n<tr>\n<th>Mode<\/th>\n<th>How it works<\/th>\n<th>General approach<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Load balance<\/td>\n<td>Both servers operate together<\/td>\n<td>Client load is divided between them<\/td>\n<\/tr>\n<tr>\n<td>Hot standby<\/td>\n<td>One server is active and the other waits<\/td>\n<td>The standby takes over during a failure<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>For a failover partnership, both servers need synchronized clocks, network connectivity, and the same scope. DHCP failover communication uses TCP port 647, so firewall rules must allow that connection between the partners.<\/p>\n<pre><code>Add-DhcpServerv4Failover -ComputerName dhcp01 -PartnerServer dhcp02 -Name \"DHCP-Failover\" -ScopeId 192.168.10.0 -SharedSecret \"Strong-Shared-Secret\" -Mode LoadBalance -LoadBalancePercent 50<\/code><\/pre>\n<p>Do not leave the shared secret in command history in production. Review PowerShell history and centralized logging policies, and use a safer credential-handling method where appropriate.<\/p>\n<p>Check the partnership after creating it:<\/p>\n<pre><code>Get-DhcpServerv4Failover -ComputerName dhcp01\nGet-DhcpServerv4FailoverStatistics -ComputerName dhcp01<\/code><\/pre>\n<p>The relationship should show normal communication, with the partner reachable and scope synchronization confirmed. Failover is not a backup, so export the DHCP configuration separately.<\/p>\n<p><strong>What to do<\/strong> &#8211; During a controlled maintenance window, disable the first server and confirm that a new client can still obtain an address from the partner.<\/p>\n<h2 id=\"dhcp-security-and-unauthorized-server-checks\">DHCP security and unauthorized server checks<\/h2>\n<p>DHCP is one of the first configuration sources on a network, so a rogue server can cause serious damage. It could give clients an attacker&#8217;s gateway or DNS server. If your switch supports DHCP snooping, mark only the port connected to the legitimate DHCP server as trusted.<\/p>\n<p>On Windows Server, check these items regularly:<\/p>\n<ul>\n<li>Confirm that the DHCP server is authorized in Active Directory when the deployment uses a domain.<\/li>\n<li>Monitor scope utilization and address conflicts.<\/li>\n<li>Keep DHCP audit logs enabled.<\/li>\n<li>Limit administrative access to the people who need it.<\/li>\n<li>Do not expose the DHCP server to unnecessary internet access.<\/li>\n<\/ul>\n<p>DHCP audit logs are normally stored under <code>C:\\Windows\\System32\\dhcp<\/code>. Their names follow the <code>DhcpSrvLog-*.log<\/code> pattern. Review service status, scope information, and lease records together. Restarting the service without reading the logs does not remove the cause of a problem.<\/p>\n<div class=\"aiw-callout aiw-callout-warn\">\n<p class=\"aiw-callout-label\">Caution<\/p>\n<p>A DHCP server on the wrong VLAN or an unauthorized server can distribute a gateway and DNS configuration that breaks connectivity for many clients. Check authorization, switch controls, and relay settings before blaming Windows.<\/p>\n<\/div>\n<h2 id=\"testing-and-troubleshooting-after-installation\">Testing and troubleshooting after installation<\/h2>\n<p>For the first test, use a Windows client on the same VLAN. Clear its current configuration and request a new lease:<\/p>\n<pre><code>ipconfig \/release\nipconfig \/renew\nipconfig \/all\nping 192.168.10.1\nnslookup example.com<\/code><\/pre>\n<p>If the client receives an address in the <code>169.254.0.0\/16<\/code> range, it may not have received a DHCP response. Check the VLAN, switch port, cable, Windows Firewall, DHCP service, and relay configuration in that order. A client on another VLAN will not reach the server if DHCP relay is missing, because the server will never see its Discover packet.<\/p>\n<p>View active scopes and leases on the server:<\/p>\n<pre><code>Get-DhcpServerv4Scope\nGet-DhcpServerv4Lease -ScopeId 192.168.10.0\nGet-DhcpServerv4Binding<\/code><\/pre>\n<p>In the <code>Get-DhcpServerv4Binding<\/code> output, confirm that DHCP is bound to the intended network adapter. A server with multiple NICs can be bound to the wrong interface. If packet-level inspection is necessary, use Wireshark to follow DHCP Discover and Offer packets. If the client&#8217;s request is visible but no Offer returns, investigate the server, binding, scope, and firewall.<\/p>\n<p>You can export the configuration with the Windows Server DHCP export command:<\/p>\n<pre><code>Export-DhcpServer -ComputerName dhcp01 -File \"C:\\Backup\\dhcp-config.xml\" -Leases -Force<\/code><\/pre>\n<p>Before restoring, verify both the XML file and the target server&#8217;s network settings. Creating the backup file is not enough; test the import on an isolated test server. I once put a printer&#8217;s manually assigned address inside a DHCP pool and spent too long looking at the printer before checking the scope boundaries. Since then, I write static assignments beside the pool range, not in a separate document that nobody opens.<\/p>\n<p><strong>What to do<\/strong> &#8211; Check <code>ipconfig \/all<\/code>, gateway reachability, DNS resolution, bindings, and logs as one test sequence instead of treating the IP address as the whole diagnosis.<\/p>\n<div class=\"aiw-callout aiw-callout-field\">\n<p class=\"aiw-callout-label\">From the field<\/p>\n<p>I once put a printer&#039;s manually assigned address inside the dynamic pool. The printer looked broken, but the real problem was my scope documentation; checking the pool boundaries fixed the diagnosis.<\/p>\n<\/div>\n<h2 id=\"check-these-before-going-live\">Check These Before Going Live<\/h2>\n<ul class=\"aiw-checklist\">\n<li>Assign the DHCP server a static IP address.<\/li>\n<li>Document the subnet, gateway, DNS servers, static assignments, and pool boundaries.<\/li>\n<li>Install the DHCP role and verify the DHCPServer service.<\/li>\n<li>Authorize the server in Active Directory when the deployment requires it.<\/li>\n<li>Create the scope without overlapping network, broadcast, or static addresses.<\/li>\n<li>Configure gateway, DNS, domain suffix, reservations, and lease duration.<\/li>\n<li>Test a client lease, gateway connection, DNS lookup, logs, failover, and backup restore.<\/li>\n<\/ul>\n<div class=\"aiw-cta\">\n<p>If you are setting up DHCP on a new Windows Server, begin with the subnet and static-assignment plan, then test one client before migrating the rest of the VLAN. Keep the export file, lease data, and failover test result with your server documentation.<\/p>\n<p class=\"aiw-cta-action\"><a href=\"https:\/\/www.vps.tc\/en\/vps\">Explore VPS plans<\/a><\/p>\n<\/div>\n<h2 id=\"frequently-asked-questions\">Frequently Asked Questions<\/h2>\n<div class=\"aiw-faq\">\n<details class=\"aiw-faq-item\" open>\n<summary>Does a Windows Server DHCP server need a static IP address?<\/summary>\n<p>Yes. The DHCP server should use a manually assigned static IP address or a reliable reservation outside the dynamic scope. Clients need a stable destination for DHCP relay and administration, and the server should not depend on the service it provides to discover its own address. Also make sure the chosen address does not overlap the lease pool.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>Do I need to authorize DHCP in Active Directory?<\/summary>\n<p>You need authorization when using DHCP in an Active Directory domain environment. An authorized server is registered in the directory and can lease addresses there. A workgroup deployment does not use Active Directory authorization, but it still needs correct network connectivity, scope configuration, and protection against other DHCP servers on the same broadcast domain.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>Why is my DHCP client receiving a 169.254 address?<\/summary>\n<p>A 169.254.0.0\/16 address usually means the client did not receive a usable DHCP response. Check the client VLAN, switch port, cable, Windows Firewall, DHCPServer service, active scope, and DHCP binding. If the client is on another VLAN, verify that the router or Layer 3 switch has a DHCP relay configured for the server.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>What is the difference between a DHCP reservation and a static IP?<\/summary>\n<p>A reservation keeps the device configured for DHCP while the server repeatedly assigns the same address to its client identifier. A static IP is manually configured on the device itself. Reservations are easier to manage centrally, but they depend on DHCP availability. Both approaches require you to keep the address outside the dynamic pool or otherwise prevent conflicts.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>Should I use DHCP failover or just export the configuration?<\/summary>\n<p>They solve different problems. Failover keeps another DHCP server able to serve clients during a partner failure. An export gives you configuration data for recovery or migration; it does not provide active service during an outage. A production deployment may need both, along with a tested restore procedure and a controlled failover test.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>How can I check whether DHCP is using the correct network adapter?<\/summary>\n<p>Run Get-DhcpServerv4Binding on the server and compare the enabled binding with the intended interface address and VLAN. A multi-homed server may listen on the wrong NIC even when the role and scope look correct. Also check the server&#039;s routing, firewall rules, and relay path before changing client settings.<\/p>\n<\/details>\n<\/div>\n<h2 id=\"sources\">Sources<\/h2>\n<ul class=\"aiw-sources\">\n<li><a href=\"https:\/\/learn.microsoft.com\/en-us\/windows-server\/networking\/technologies\/dhcp\/dhcp-top\" target=\"_blank\" rel=\"noopener\">Microsoft Learn &#8211; DHCP Overview<\/a> \u2014 learn.microsoft.com<\/li>\n<li><a href=\"https:\/\/www.rfc-editor.org\/rfc\/rfc2131\" target=\"_blank\" rel=\"noopener\">RFC 2131 &#8211; Dynamic Host Configuration Protocol<\/a> \u2014 rfc-editor.org<\/li>\n<li><a href=\"https:\/\/www.rfc-editor.org\/rfc\/rfc2132\" target=\"_blank\" rel=\"noopener\">RFC 2132 &#8211; DHCP Options and BOOTP Vendor Extensions<\/a> \u2014 rfc-editor.org<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>A practical Windows Server DHCP setup guide covering role installation, IPv4 scopes, options, reservations, failover, security, and troubleshooting.<\/p>\n","protected":false},"author":2,"featured_media":780,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6],"tags":[],"class_list":["post-782","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-windows"],"lang":"en","translations":{"en":782,"tr":781},"pll_sync_post":[],"_links":{"self":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts\/782","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/comments?post=782"}],"version-history":[{"count":1,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts\/782\/revisions"}],"predecessor-version":[{"id":784,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts\/782\/revisions\/784"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/media\/780"}],"wp:attachment":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/media?parent=782"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/categories?post=782"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/tags?post=782"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}