{"id":3342,"date":"2014-10-21T06:35:45","date_gmt":"2014-10-21T06:35:45","guid":{"rendered":"https:\/\/live-infoblox-blog.pantheonsite.io\/?p=3342"},"modified":"2022-10-19T16:10:32","modified_gmt":"2022-10-19T23:10:32","slug":"high-availability-dhcpv6","status":"publish","type":"post","link":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/high-availability-dhcpv6\/","title":{"rendered":"High Availability DHCPv6"},"content":{"rendered":"<p>Much has been said regarding the sometimes-subtle, sometimes-obvious ways that \u201cshiny new\u201d IPv6 is different from the \u201clegacy\u201d IPv4 protocol.\u00a0 One subtle example is how IPv6 uses ICMPv6 for the Neighbor Discovery Protocol (NDP) compared to IPv4\u2019s broadcast messages and ARP method.\u00a0 One overt example is how IPv6 uses behemoth 128-bit addresses where IPv4 uses petite 32-bit addresses.\u00a0 Another subtle example is how IPv4 uses inefficient broadcast messages on a LAN and IPv6 makes far greater use of efficient multicast.\u00a0 Another noticeable difference is how IPv4 addresses may be assigned statically to end nodes or they could use Dynamic Host Configuration Protocol (DHCP).\u00a0 Compare this with how IPv6 routers use\u00a0<a href=\"https:\/\/community.infoblox.com\/blogs\/2014\/06\/16\/why-you-must-use-icmpv6-router-advertisements-ras\" target=\"_blank\" rel=\"noopener noreferrer\">ICMPv6 Router Advertisement (RA)<\/a>\u00a0messages to signal how the end nodes will acquire their IPv6 addresses.<\/p>\n<h2 id=\"toc-hId-649789054\">DHCPv6 and DHCP for IPv4<\/h2>\n<p>One of the more subtle differences between IPv4 and IPv6 is how DHCP is used by these two distinct network protocols.\u00a0 The recognizable fact is that DHCP for IPv4 (<a href=\"https:\/\/tools.ietf.org\/html\/rfc2132\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">RFC 2132<\/a>) is a completely separate protocol from DHCPv6 for IPv6 (<a href=\"https:\/\/tools.ietf.org\/html\/rfc3315\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">RFC 3315<\/a>).\u00a0 However, these protocols share some characteristics because, frankly, DHCP helped pave the way for DHCPv6.\u00a0 The following is a list of similarities between DHCP for IPv4 and DHCPv6.<\/p>\n<ul>\n<li>Both protocols use the concepts of a DHCP client, DHCP relay and DHCP server<\/li>\n<li>Both protocols use the concepts of scopes and leases<\/li>\n<li>Both protocols use a 4-message stateful exchange between client and server (DHCP for IPv4 uses Discover\/Offer\/Request\/Acknowledge (DORA), andDHCPv6 uses Solicit\/Advertise\/Request\/Reply (SARR))<\/li>\n<li>Both protocols provide DHCP options to the end-node to provide additional information (but DHCPv6 has a larger 16-bit option type code length)<\/li>\n<li>Both protocols support Rapid Commit functionality<\/li>\n<\/ul>\n<p>Following is a list of the differences between DHCP for IPv6 and DHCPv6.<\/p>\n<ul>\n<li>DHCPv6 uses DHCP Unique Identifiers (DUIDs) (<a href=\"http:\/\/tools.ietf.org\/html\/rfc6355\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">RFC 6355<\/a>) whereas DHCP for IPv4 uses MAC addresses to identify the client.<\/li>\n<li>Their message type names are different, but perform many of the same functions (<a href=\"http:\/\/www.iana.org\/assignments\/bootp-dhcp-parameters\/bootp-dhcp-parameters.xhtml\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">DHCP message types<\/a>,\u00a0<a href=\"http:\/\/www.iana.org\/assignments\/dhcpv6-parameters\/dhcpv6-parameters.xhtml\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">DHCPv6 message types<\/a>).<\/li>\n<li>Obviously, DHCP for IPv4 messages are transmitted over IPv4 packets and DHCPv6 is transmitted over IPv6 packets.<\/li>\n<li>DHCPv6 uses ICMPv6 Router Advertisement (RA) and IPv6 multicast messages and DHCP uses broadcast IPv4 messages on the LAN.<\/li>\n<li>DHCPv6 uses link-local IPv6 addresses when communicating between client and relay\/server (<a href=\"https:\/\/tools.ietf.org\/html\/rfc6939\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">RFC 6939<\/a>), and DHCP for IPv4 uses unsolicited broadcasts.<\/li>\n<li>DHCP for IPv4 and DHCPv6 UDP port numbers are different. DHCP servers and relay agents listen on UDP port 67 and clients listen on UDP port 68, DHCPv6 clients listen on UDP port 546, DHCPv6 servers and relay agents listen on UDP port 547.<\/li>\n<li>DHCPv6 servers offer randomized interface identifiers (helps limit attacker reconnaissance), DHCP offers the next IPv4 address from the scope\/pool.<\/li>\n<li>DHCPv4 can be configured on a router, stateful\u00a0<a href=\"https:\/\/community.infoblox.com\/blogs\/2014\/09\/15\/still-using-dhcp-your-routers-you-can%E2%80%99t-do-ipv6\" target=\"_blank\" rel=\"noopener noreferrer\">DHCPv6 is not typically available on routers<\/a>.<\/li>\n<li>DHCP for IPv4 can provide the default gateway IP address to the client, whereas DHCPv6 does not have this option; the IPv6 node learns about its first-hop router from the ICMPv6 RA message (<a href=\"https:\/\/tools.ietf.org\/html\/draft-ietf-mif-dhcpv6-route-option-05\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">Pending draft on this subject<\/a>).<\/li>\n<li>DHCP for IPv4 scopes are susceptible to exhaustion; DHCPv6 scopes are typically \/64s with over 18 quintillion addresses so pool exhaustion is impossible.<\/li>\n<\/ul>\n<p>Just to clarify, in this article, we are discussing stateful DHCPv6.\u00a0 We are not referring to what is called \u201cstateless DHCPv6\u201d (<a href=\"http:\/\/tools.ietf.org\/html\/rfc3736\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">RFC 3736<\/a>) or \u201cDHCPv6-Lite\u201d.\u00a0\u00a0<a href=\"http:\/\/www.cisco.com\/c\/en\/us\/td\/docs\/ios-xml\/ios\/ipaddr_dhcp\/configuration\/xe-3s\/dhcp-xe-3s-book\/ip6-dhcp-stateless-xe.html\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">Stateless DHCPv6<\/a>\u00a0is where the IPv6 client uses Stateless Address Auto-Configuration (SLAAC) for its IPv6 address, but acquires DNS information from the first-hop router to help the node obtain functional use of the network.<\/p>\n<h2 id=\"toc-hId-678418205\">DHCP High Availability Problem Statement<\/h2>\n<p>Imagine a network that has only one DHCP server and it goes offline.\u00a0 In this situation, no systems will be able to acquire a new address and effectively join the network.\u00a0 However, nodes that already have their leases and valid lease times will continue to use the IP addresses that they have been allocated.\u00a0 In other words, if your one and only DHCP server fails, new leases could not be serviced, but those nodes that already had IP addresses would continue to use them until they reached half their renewal period.\u00a0 While the one DHCP server was offline the nodes would be unable to renew their address leases.\u00a0 DHCP for IPv4 and DHCPv6 behave the same in these situations.\u00a0 Organizations don\u2019t want to have to re-assign leases to operational clients just because a DHCP server fails.\u00a0 They want lease stability and they don\u2019t want to impact the operations of working clients.\u00a0 They also want to minimize changes to dynamic DNS if node addresses change.\u00a0 Therefore, we need some solutions to help solve this problem.<\/p>\n<h2 id=\"toc-hId-707047356\">Possible Solutions for DHCP Redundancy<\/h2>\n<p>Because services like DHCP and DNS are vitally important to IP networking connectivity, it is important to have highly reliable services for these critical functions.\u00a0 We desire lease stability and no impact to operational clients if a DHCP server fails.\u00a0 Most of the solutions to the DHCP availability problem require the use of multiple DHCP servers.\u00a0 We just need a way to operate two DHCP servers without impacting the clients if a server fails.\u00a0 As you can probably guess, one possible solution would involve synchronizing lease information between multiple DHCP servers.<\/p>\n<p>There are both similarities as well as some differences between DHCP for IPv4 and DHCPv6 regarding how they work in a high-availability configuration with redundant DHCP servers.\u00a0 The IETF RFC titled \u201cDHCPv6 Redundancy Deployment Considerations\u201d (BCP 180,\u00a0<a href=\"http:\/\/tools.ietf.org\/html\/rfc6853\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">RFC 6853<\/a>) provides an overview of the issues and reviews possible solutions to the problem.\u00a0 One key difference with DHCPv6 is that a node may request a single IPv6 address or a node may also request an entire IPv6 prefix to use downstream.\u00a0 This second request for an IPv6 prefix is called DHCPv6 Prefix Delegation (DHCPv6-PD) (<a href=\"http:\/\/tools.ietf.org\/html\/rfc3633\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">RFC 3633<\/a>) and there is no equivalent function in DHCP for IPv4.<\/p>\n<h2 id=\"toc-hId-735676507\">Split Scopes, Split Prefix Ranges<\/h2>\n<p>A possible solution to the problem that may be familiar to IPv4 DHCP administrators is the concept termed \u201csplit scopes.\u201d\u00a0 This is where two DHCP servers split up the IP address space: Half the addresses are used in a scope on the first DHCP server and the second half are used in a scope on the second DHCP server.\u00a0 With IPv4 there are far fewer IP addresses to go around.\u00a0 With IPv6 there is an abundance of addresses within a single \/64 default prefix size.\u00a0 In the DHCPv6 situation these are called \u201csplit prefixes\u201d and the entire \/64 is split into two \/65 prefixes.\u00a0 For example, the prefix used on the LAN would be 2001:0DB8:1234:5678::\/64 and it would be split up into the following two \/65 prefixes used by DHCPv6.<\/p>\n<p>2001:0DB8:1234:5678:0000::\/65<\/p>\n<p>2001:0DB8:1234:5678:0000:0000:0000:0000 to 2001:db8:1234:5678:7FFF:FFFF:FFFF:FFFF<\/p>\n<p>2001:0DB8:1234:5678:8000::\/65<\/p>\n<p>2001:0DB8:1234:5678:8000:0000:0000:0000 to 2001:db8:1234:5678:FFFF:FFFF:FFFF:FFFF<\/p>\n<p>In this split prefix method, both DHCPv6 servers will respond to the Solicit message with an Advertise message.\u00a0 The two DHCPv6 servers use the DHCPv6 server preference option to tell the end-nodes which of the two DHCPv6 servers they should use.\u00a0 End-nodes will always chose the DHCPv6 server with the highest preference.\u00a0 Therefore, any DHCPv6 lease will be given by the preferred server.<\/p>\n<p>This preference value is called the \u201c<a href=\"https:\/\/tools.ietf.org\/html\/rfc3315#page-79\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">DHCPv6 Failover Preference Option<\/a>\u201d and the higher preference is configured on the primary server (while the lower preference on the secondary server).\u00a0 This preference value is sent within the DHCPv6 Advertise message.\u00a0 Typical preference values are \u201c255\u201d for the primary server and \u201c0\u201d for the secondary server.<\/p>\n<p>It is customary to use a preference value of \u201c0\u201d on the secondary server, so if the client receives that response first, it will wait a period of time until it hears another potential response with a higher preference value.\u00a0 This gives the primary server a chance to still be the primary server even if it isn\u2019t the first to respond.<\/p>\n<p>Note that if the preference value is set the same on the two DHCPv6 server Advertise messages, then the client picks one while discarding the other. The two servers would then need to synchronize their lease databases, thus increasing server load.<\/p>\n<p>It should be noted as well that an active\/passive design is much simpler to implement. In this configuration, if the primary server fails, then the nodes with IPv6 addresses will continue to function.\u00a0 New nodes joining the network will get their IPv6 addresses from the secondary server.\u00a0 However, when existing nodes need to renew their leases, the rebinding will fail to the secondary server and the node will end up getting a new address on the second \/65 from the second DHCPv6 server.\u00a0 This will not meet our goal for lease stability.<\/p>\n<h2 id=\"toc-hId-764305658\">Multiple Prefixes<\/h2>\n<p>A similar method to the split prefixes concept that we just described is one in which the two DHCPv6 servers each use a completely different \/64 prefix.\u00a0 For example, the first DHCPv6 server will use 2001<img decoding=\"async\" id=\"smileyvery-happy\" class=\"emoticon emoticon-smileyvery-happy\" title=\"Smiley Very Happy\" src=\"https:\/\/cixhp49439.i.lithium.com\/i\/smilies\/16x16_smiley-very-happy.png\" alt=\"Smiley Very Happy\" \/>B8:1:1::\/64 with a higher preference and use 2001<img decoding=\"async\" id=\"smileyvery-happy\" class=\"emoticon emoticon-smileyvery-happy\" title=\"Smiley Very Happy\" src=\"https:\/\/cixhp49439.i.lithium.com\/i\/smilies\/16x16_smiley-very-happy.png\" alt=\"Smiley Very Happy\" \/>B8:2:2::\/64 with a lower preference. Meanwhile, the second DHCPv6 server will use 2001<img decoding=\"async\" id=\"smileyvery-happy\" class=\"emoticon emoticon-smileyvery-happy\" title=\"Smiley Very Happy\" src=\"https:\/\/cixhp49439.i.lithium.com\/i\/smilies\/16x16_smiley-very-happy.png\" alt=\"Smiley Very Happy\" \/>B8:1:1::\/64 with a lower preference and will use 2001<img decoding=\"async\" id=\"smileyvery-happy\" class=\"emoticon emoticon-smileyvery-happy\" title=\"Smiley Very Happy\" src=\"https:\/\/cixhp49439.i.lithium.com\/i\/smilies\/16x16_smiley-very-happy.png\" alt=\"Smiley Very Happy\" \/>B8:2:2::\/64 with a higher preference.\u00a0 If one of the server fails, then the rebinding nodes or new nodes may get an addresses from either prefix.\u00a0 The issue here is that the local LAN would need to have both IPv6 prefixes operational on the network at the same time.\u00a0 This technique also suffers from a lack a lease stability.<\/p>\n<h2 id=\"toc-hId-792934809\">Load Balancing<\/h2>\n<p>Another idea is one that uses hash buckets on both of the DHCPv6 servers.\u00a0 Each DHCPv6 server calculates a hash value between 1 and 256 buckets.\u00a0 One server will service the requests that have a hash value that falls within buckets 1 to 128.\u00a0 The other server will service the requests that have a hash value that falls within buckets 129 to 256.\u00a0 This approach effectively distributes load across the two servers.\u00a0 And while it also solves the problem of load balancing between two or more DHCPv6 servers, it doesn\u2019t solve the high-availability redundancy problem and does not provide lease stability.\u00a0 There is an\u00a0<a href=\"http:\/\/tools.ietf.org\/html\/draft-ietf-dhc-dhcpv6-load-balancing-02\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">IETF RFC draft proposing this solution<\/a>.<\/p>\n<h2 id=\"toc-hId-821563960\">Overlapping Prefixes &#8211; DHCPv6 Failover<\/h2>\n<p>In this solution, two DHCPv6 servers use overlapping ranges and thus identical prefixes.\u00a0 For example, both DHCPv6 servers will respond to a Solicit message with an Advertise from the 2001<img decoding=\"async\" id=\"smileyvery-happy\" class=\"emoticon emoticon-smileyvery-happy\" title=\"Smiley Very Happy\" src=\"https:\/\/cixhp49439.i.lithium.com\/i\/smilies\/16x16_smiley-very-happy.png\" alt=\"Smiley Very Happy\" \/>B8:1:1::\/64 prefix.\u00a0 Each DHCPv6 server will use a different preference value such as \u201c255\u201d for the primary DHCPv6 server and \u201c0\u201d for the secondary DHCPv6 server.\u00a0 This might sound like a great option up until the point where two nodes on the same LAN are issued an identical interface identifier.\u00a0 Not only would that be a great day to go buy a lottery ticket, but it would also be the day Duplicate Address Detection (DAD) helps prevent a collision.<\/p>\n<p>To really make this a robust solution there are some other conditions that need to be addressed.\u00a0 For example, in the situation where an organization would like to have multiple DHCP servers provide addresses from a single shared pool, the two servers need to share lease information.\u00a0 If you made a pair of DHCPv6 servers share the same pool and have both servers allocate addresses then they will need some mechanism to share the state of leased IP addresses with each other. \u00a0In other words, there will need to be some form of synchronization protocol used between the two servers.\u00a0 This protocol will be required to:<\/p>\n<ul>\n<li>continuously operate as the systems are both operational<\/li>\n<li>send heartbeat messages like a health check to make sure that the other server is online and operational<\/li>\n<li>used to re-synchronize status when a server is booted up to check in and synchronize with the other operational server<\/li>\n<li>synchronize the databases of state information and note which of the servers initially serviced the lease<\/li>\n<\/ul>\n<p>While this may sound like a great idea, there are several problems with this approach.\u00a0 This surely adds complexity to the design. The other problem is that this is not currently available to implement because it is not a valid IETF RFC yet.\u00a0 There is an IETF RFC titled \u201cDHCPv6 Failover Requirements\u201d (<a href=\"http:\/\/tools.ietf.org\/html\/rfc7031\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">RFC 7031<\/a>) which covers the considerations of this failover method, but it does not specify the failover protocol.\u00a0 Unfortunately, the IETF draft that specifies the failover protocol titled \u201c<a href=\"http:\/\/tools.ietf.org\/html\/draft-ietf-dhc-dhcpv6-failover-design-04\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">DHCPv6 Failover Design<\/a>\u201d is still in draft status.\u00a0 This DHCPv6 draft is based on the\u00a0<a href=\"http:\/\/tools.ietf.org\/html\/draft-ietf-dhc-failover-12\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">DHCP Failover Protocol for IPv4<\/a>, which was proposed but never approved.\u00a0 However, that didn\u2019t stop ISC from creating and implementing their own<a href=\"https:\/\/kb.isc.org\/article\/AA-00502\/0\/A-Basic-Guide-to-Configuring-DHCP-Failover.html\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">\u00a0failover protocol method<\/a>.\u00a0 (ISC is still deciding if they want to implement this similar feature for DHCPv6.)<\/p>\n<h2 id=\"toc-hId-850193111\">Summary<\/h2>\n<p>We have reviewed many similarities and differences between DHCP for IPv4 and DHCPv6.\u00a0 They share many of the same concepts: The things that we know about DHCP will carry forward into our engineering and operation of DHCPv6 systems.\u00a0 However, there are some subtle differences between the two and we can\u2019t just assume that DHCPv6 is configured identically to the way we have been used to configuring DHCP for IPv4.\u00a0 Namely, the DHCPv6 redundancy strategy we choose will likely be different than the method we may be using for DHCPv4.\u00a0 However, this is acceptable because IPv4 and IPv6 are completely different network protocols and we can\u2019t expect that everything will be identical.\u00a0 If everything with IPv6 is the same as IPv4, then that would be boring and no fun at all.\u00a0\u00a0<a href=\"http:\/\/en.wiktionary.org\/wiki\/vive_la_diff%C3%A9rence\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">Vive la difference<\/a>!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Much has been said regarding the sometimes-subtle, sometimes-obvious ways that \u201cshiny new\u201d IPv6 is different from the \u201clegacy\u201d IPv4 protocol.\u00a0 One subtle example is how IPv6 uses ICMPv6 for the Neighbor Discovery Protocol (NDP) compared to IPv4\u2019s broadcast messages and ARP method.\u00a0 One overt example is how IPv6 uses behemoth 128-bit addresses where IPv4 uses [&hellip;]<\/p>\n","protected":false},"author":321,"featured_media":3187,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"_genesis_hide_title":false,"_genesis_hide_breadcrumbs":false,"_genesis_hide_singular_image":false,"_genesis_hide_footer_widgets":false,"_genesis_custom_body_class":"","_genesis_custom_post_class":"","_genesis_layout":"","footnotes":""},"categories":[17],"tags":[16,38,15],"class_list":{"0":"post-3342","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-ipv6-coe","8":"tag-infoblox","9":"tag-ipv6","10":"tag-security","11":"entry"},"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v27.3 (Yoast SEO v27.3) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>High Availability DHCPv6<\/title>\n<meta name=\"description\" content=\"DHCP is able to be used with both IPv4 and IPv6 services. You can learn more about DHCP and the differences between IPv4 and IPv6 operating systems here.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/high-availability-dhcpv6\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"High Availability DHCPv6\" \/>\n<meta property=\"og:description\" content=\"DHCP is able to be used with both IPv4 and IPv6 services. You can learn more about DHCP and the differences between IPv4 and IPv6 operating systems here.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/high-availability-dhcpv6\/\" \/>\n<meta property=\"og:site_name\" content=\"Infoblox Blog\" \/>\n<meta property=\"article:published_time\" content=\"2014-10-21T06:35:45+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2022-10-19T23:10:32+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/IPv6-ARIN.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"660\" \/>\n\t<meta property=\"og:image:height\" content=\"454\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Scott Hogg\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Scott Hogg\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"11 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/high-availability-dhcpv6\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/high-availability-dhcpv6\\\/\"},\"author\":{\"name\":\"Scott Hogg\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/#\\\/schema\\\/person\\\/ee71ac61fe2ea349f6e991e628d22f4c\"},\"headline\":\"High Availability DHCPv6\",\"datePublished\":\"2014-10-21T06:35:45+00:00\",\"dateModified\":\"2022-10-19T23:10:32+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/high-availability-dhcpv6\\\/\"},\"wordCount\":2193,\"publisher\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/high-availability-dhcpv6\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/wp-content\\\/uploads\\\/IPv6-ARIN.jpg\",\"keywords\":[\"Infoblox\",\"IPv6\",\"Security\"],\"articleSection\":[\"IPv6 CoE\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/high-availability-dhcpv6\\\/\",\"url\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/high-availability-dhcpv6\\\/\",\"name\":\"High Availability DHCPv6\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/high-availability-dhcpv6\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/high-availability-dhcpv6\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/wp-content\\\/uploads\\\/IPv6-ARIN.jpg\",\"datePublished\":\"2014-10-21T06:35:45+00:00\",\"dateModified\":\"2022-10-19T23:10:32+00:00\",\"description\":\"DHCP is able to be used with both IPv4 and IPv6 services. You can learn more about DHCP and the differences between IPv4 and IPv6 operating systems here.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/high-availability-dhcpv6\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/high-availability-dhcpv6\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/high-availability-dhcpv6\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/wp-content\\\/uploads\\\/IPv6-ARIN.jpg\",\"contentUrl\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/wp-content\\\/uploads\\\/IPv6-ARIN.jpg\",\"width\":660,\"height\":454,\"caption\":\"The IPv6 Tipping Point Effect\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/ipv6-coe\\\/high-availability-dhcpv6\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"IPv6 CoE\",\"item\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/category\\\/ipv6-coe\\\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"High Availability DHCPv6\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/\",\"name\":\"infoblox.com\\\/blog\\\/\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/#organization\",\"name\":\"Infoblox\",\"url\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/wp-content\\\/uploads\\\/infoblox-logo-2.svg\",\"contentUrl\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/wp-content\\\/uploads\\\/infoblox-logo-2.svg\",\"width\":137,\"height\":30,\"caption\":\"Infoblox\"},\"image\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\"}},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/#\\\/schema\\\/person\\\/ee71ac61fe2ea349f6e991e628d22f4c\",\"name\":\"Scott Hogg\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/blogs.infoblox.com\\\/wp-content\\\/uploads\\\/avatar_user_321_1574118215-96x96.jpg\",\"url\":\"https:\\\/\\\/blogs.infoblox.com\\\/wp-content\\\/uploads\\\/avatar_user_321_1574118215-96x96.jpg\",\"contentUrl\":\"https:\\\/\\\/blogs.infoblox.com\\\/wp-content\\\/uploads\\\/avatar_user_321_1574118215-96x96.jpg\",\"caption\":\"Scott Hogg\"},\"description\":\"Scott Hogg has 30 years of network and security experience and is president of Hogg Networking with. Scott Hogg specializes in teaching Internet Protocol version 6 (IPv6) and providing implementation guidance. Scott is CCIE #5133 (Emeritus) and CISSP #4610. Scott is Chair Emeritus of the Rocky Mountain IPv6 Task Force (RMv6TF), a member of the IPv6 Center of Excellence (COE), and co-author of the Cisco Press book on IPv6 Security.\",\"sameAs\":[\"https:\\\/\\\/hexabuild.io\"],\"url\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/author\\\/scott-hogg\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"High Availability DHCPv6","description":"DHCP is able to be used with both IPv4 and IPv6 services. You can learn more about DHCP and the differences between IPv4 and IPv6 operating systems here.","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:\/\/www.infoblox.com\/blog\/ipv6-coe\/high-availability-dhcpv6\/","og_locale":"en_US","og_type":"article","og_title":"High Availability DHCPv6","og_description":"DHCP is able to be used with both IPv4 and IPv6 services. You can learn more about DHCP and the differences between IPv4 and IPv6 operating systems here.","og_url":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/high-availability-dhcpv6\/","og_site_name":"Infoblox Blog","article_published_time":"2014-10-21T06:35:45+00:00","article_modified_time":"2022-10-19T23:10:32+00:00","og_image":[{"width":660,"height":454,"url":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/IPv6-ARIN.jpg","type":"image\/jpeg"}],"author":"Scott Hogg","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Scott Hogg","Est. reading time":"11 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/high-availability-dhcpv6\/#article","isPartOf":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/high-availability-dhcpv6\/"},"author":{"name":"Scott Hogg","@id":"https:\/\/www.infoblox.com\/blog\/#\/schema\/person\/ee71ac61fe2ea349f6e991e628d22f4c"},"headline":"High Availability DHCPv6","datePublished":"2014-10-21T06:35:45+00:00","dateModified":"2022-10-19T23:10:32+00:00","mainEntityOfPage":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/high-availability-dhcpv6\/"},"wordCount":2193,"publisher":{"@id":"https:\/\/www.infoblox.com\/blog\/#organization"},"image":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/high-availability-dhcpv6\/#primaryimage"},"thumbnailUrl":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/IPv6-ARIN.jpg","keywords":["Infoblox","IPv6","Security"],"articleSection":["IPv6 CoE"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/high-availability-dhcpv6\/","url":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/high-availability-dhcpv6\/","name":"High Availability DHCPv6","isPartOf":{"@id":"https:\/\/www.infoblox.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/high-availability-dhcpv6\/#primaryimage"},"image":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/high-availability-dhcpv6\/#primaryimage"},"thumbnailUrl":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/IPv6-ARIN.jpg","datePublished":"2014-10-21T06:35:45+00:00","dateModified":"2022-10-19T23:10:32+00:00","description":"DHCP is able to be used with both IPv4 and IPv6 services. You can learn more about DHCP and the differences between IPv4 and IPv6 operating systems here.","breadcrumb":{"@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/high-availability-dhcpv6\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.infoblox.com\/blog\/ipv6-coe\/high-availability-dhcpv6\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/high-availability-dhcpv6\/#primaryimage","url":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/IPv6-ARIN.jpg","contentUrl":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/IPv6-ARIN.jpg","width":660,"height":454,"caption":"The IPv6 Tipping Point Effect"},{"@type":"BreadcrumbList","@id":"https:\/\/www.infoblox.com\/blog\/ipv6-coe\/high-availability-dhcpv6\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.infoblox.com\/blog\/"},{"@type":"ListItem","position":2,"name":"IPv6 CoE","item":"https:\/\/www.infoblox.com\/blog\/category\/ipv6-coe\/"},{"@type":"ListItem","position":3,"name":"High Availability DHCPv6"}]},{"@type":"WebSite","@id":"https:\/\/www.infoblox.com\/blog\/#website","url":"https:\/\/www.infoblox.com\/blog\/","name":"infoblox.com\/blog\/","description":"","publisher":{"@id":"https:\/\/www.infoblox.com\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.infoblox.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.infoblox.com\/blog\/#organization","name":"Infoblox","url":"https:\/\/www.infoblox.com\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.infoblox.com\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/infoblox-logo-2.svg","contentUrl":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/infoblox-logo-2.svg","width":137,"height":30,"caption":"Infoblox"},"image":{"@id":"https:\/\/www.infoblox.com\/blog\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/www.infoblox.com\/blog\/#\/schema\/person\/ee71ac61fe2ea349f6e991e628d22f4c","name":"Scott Hogg","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/blogs.infoblox.com\/wp-content\/uploads\/avatar_user_321_1574118215-96x96.jpg","url":"https:\/\/blogs.infoblox.com\/wp-content\/uploads\/avatar_user_321_1574118215-96x96.jpg","contentUrl":"https:\/\/blogs.infoblox.com\/wp-content\/uploads\/avatar_user_321_1574118215-96x96.jpg","caption":"Scott Hogg"},"description":"Scott Hogg has 30 years of network and security experience and is president of Hogg Networking with. Scott Hogg specializes in teaching Internet Protocol version 6 (IPv6) and providing implementation guidance. Scott is CCIE #5133 (Emeritus) and CISSP #4610. Scott is Chair Emeritus of the Rocky Mountain IPv6 Task Force (RMv6TF), a member of the IPv6 Center of Excellence (COE), and co-author of the Cisco Press book on IPv6 Security.","sameAs":["https:\/\/hexabuild.io"],"url":"https:\/\/www.infoblox.com\/blog\/author\/scott-hogg\/"}]}},"_links":{"self":[{"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/posts\/3342","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/users\/321"}],"replies":[{"embeddable":true,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/comments?post=3342"}],"version-history":[{"count":2,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/posts\/3342\/revisions"}],"predecessor-version":[{"id":8102,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/posts\/3342\/revisions\/8102"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/media\/3187"}],"wp:attachment":[{"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/media?parent=3342"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/categories?post=3342"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/tags?post=3342"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}