{"id":5904,"date":"2021-02-15T15:21:04","date_gmt":"2021-02-15T23:21:04","guid":{"rendered":"https:\/\/blogs.infoblox.com\/?p=5904"},"modified":"2022-10-20T14:59:44","modified_gmt":"2022-10-20T21:59:44","slug":"using-infoblox-for-hybrid-name-resolution-of-aws-privatelink-interface-endpoints","status":"publish","type":"post","link":"https:\/\/www.infoblox.com\/blog\/community\/using-infoblox-for-hybrid-name-resolution-of-aws-privatelink-interface-endpoints\/","title":{"rendered":"Using Infoblox for Hybrid Name Resolution of AWS PrivateLink Interface Endpoints"},"content":{"rendered":"<p><span style=\"font-weight: 400;\">AWS <\/span><a href=\"https:\/\/docs.aws.amazon.com\/vpc\/latest\/userguide\/vpce-interface.html\"><span style=\"font-weight: 400;\">Interface Endpoints<\/span><\/a><span style=\"font-weight: 400;\"> can be used to access services provided through AWS PrivateLink. The supported services can include some native AWS services, services hosted by other AWS customers, and supported AWS Marketplace Partner Services. PrivateLink allows your VMs and applications to connect to these services using a private IP address, keeping all traffic within AWS networks and off the public Internet.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">When these interface endpoints are created, AWS creates a unique DNS hostname and record for the endpoint. Additionally, if you enable the private DNS option for an endpoint, AWS associates a private hosted zone with your VPC that contains record sets for the default name of the service, for example ec2.us-west-1.amazonaws.com which will resolve to the interface endpoint when using the default Route 53 resolver in that VPC. However, this only works for VMs or other clients deployed into the same VPC where the interface endpoint lives, and only if you are using the default DNS resolver.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">In this post, we\u2019ll look at two scenarios where you can benefit from using Infoblox NIOS and AWS Route 53 Resolver Inbound Endpoints to resolve these PrivateLink Interface Endpoint services.<\/span><\/p>\n<h3><b>Resolving Interface Endpoints from On-Premises Networks<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">For this example, we\u2019ll use an interface endpoint in a VPC, providing access to the AWS EC2 service with a default name of ec2.us-west-1.amazonaws.com. We want on-premises clients to connect using this endpoint for access to EC2 services. Consider the diagram below, showing the path of a DNS request for this endpoint.<\/span><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-5913\" src=\"https:\/\/blogs.infoblox.com\/wp-content\/uploads\/AWS-Interface-1.png\" alt=\"\" width=\"1466\" height=\"495\" srcset=\"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/AWS-Interface-1.png 1466w, https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/AWS-Interface-1-300x101.png 300w, https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/AWS-Interface-1-1024x346.png 1024w, https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/AWS-Interface-1-768x259.png 768w\" sizes=\"auto, (max-width: 1466px) 100vw, 1466px\" \/><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Client queries Infoblox DNS for ec2.us-west-1.amazonaws.com.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Infoblox DNS forwards query to Route 53 Resolver inbound endpoint in VPC via VPN or AWS Direct Connect.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">The inbound endpoint uses Route 53 Resolver to resolve query to private hosted zone associated with the VPC.<\/span><\/li>\n<\/ul>\n<h3><b>Infoblox NIOS as Primary Name Server in VPCs<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">For this example, we\u2019ll again use an interface endpoint in a VPC, providing access to the AWS EC2 service with a default name of ec2.us-west-1.amazonaws.com. In this case, we want to use Infoblox vNIOS deployed in AWS as primary DNS for our VPCs, to allow for centralized DNS management and gain benefits provided by Infoblox DNS such as response policy zones, query logging, and many other security and management features. The diagram below depicts the path for DNS requests for this endpoint. Please note that the Infoblox DNS server does not need to be in the same VPC as the interface endpoints; it is pictured that way here for simplicity and as one possible solution.<\/span><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-5912\" src=\"https:\/\/blogs.infoblox.com\/wp-content\/uploads\/AWS-Interface-2.png\" alt=\"\" width=\"1433\" height=\"650\" srcset=\"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/AWS-Interface-2.png 1433w, https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/AWS-Interface-2-300x136.png 300w, https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/AWS-Interface-2-1024x464.png 1024w, https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/AWS-Interface-2-768x348.png 768w\" sizes=\"auto, (max-width: 1433px) 100vw, 1433px\" \/><\/p>\n<ul>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Infoblox vNIOS instance set as primary name server for VPCs<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">EC2 instance or other client queries Infoblox DNS for ec2.us-west-1.amazonaws.com via Transit Gateway or VPC peering.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">Infoblox DNS forwards query to Route 53 Resolver inbound endpoint.<\/span><\/li>\n<li style=\"font-weight: 400;\" aria-level=\"1\"><span style=\"font-weight: 400;\">The inbound endpoint uses Route 53 Resolver to resolve query to private hosted zone associated with the VPC.<\/span><\/li>\n<\/ul>\n<h3><b>Implementation<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Infoblox NIOS or vNIOS appliances should be deployed and configured either on-prem or in an AWS VPC using Infoblox best practices. Refer to Infoblox deployment guides at <\/span><a href=\"https:\/\/infoblox.com\/resources\"><span style=\"font-weight: 400;\">https:\/\/infoblox.com\/resources<\/span><\/a><span style=\"font-weight: 400;\"> for details on deployment and configuration. AWS Interface Endpoints and Route 53 Resolver Endpoints should be deployed using AWS best practices. For details on deploying required AWS resources, refer to AWS documentation at <\/span><a href=\"https:\/\/docs.aws.amazon.com\/\"><span style=\"font-weight: 400;\">https:\/\/docs.aws.amazon.com\/<\/span><\/a><span style=\"font-weight: 400;\">.\u00a0<\/span><\/p>\n<p><span style=\"font-weight: 400;\">Once your Infoblox name server and AWS resources are configured according to one of the diagrams above, or a combination of the two if you will use Infoblox for DNS resolution on-premises and in your VPCs, the final configuration consists of setting up DNS conditional forwarding for the appropriate zone.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">In the AWS Management Console, find the IP address(es) for your Route 53 Resolver inbound endpoint on the Route 53 &gt; Resolver &gt; Inbound endpoints detail page for your endpoint.<\/span><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-5911\" src=\"https:\/\/blogs.infoblox.com\/wp-content\/uploads\/AWS-Interface-3.png\" alt=\"\" width=\"809\" height=\"560\" srcset=\"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/AWS-Interface-3.png 809w, https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/AWS-Interface-3-300x208.png 300w, https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/AWS-Interface-3-768x532.png 768w\" sizes=\"auto, (max-width: 809px) 100vw, 809px\" \/><\/p>\n<p><span style=\"font-weight: 400;\">Next, log into your Infoblox Grid Manager and navigate to the Data Management &gt; DNS &gt; Zones tab. Expand the Add dropdown and select Forward Zone.<\/span><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-5910\" src=\"https:\/\/blogs.infoblox.com\/wp-content\/uploads\/AWS-Interface-4.png\" alt=\"\" width=\"596\" height=\"324\" srcset=\"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/AWS-Interface-4.png 596w, https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/AWS-Interface-4-300x163.png 300w\" sizes=\"auto, (max-width: 596px) 100vw, 596px\" \/><\/p>\n<p><span style=\"font-weight: 400;\">On step 1 of the Add Forward Zone Wizard, select <\/span><b>Add a forward forward-mapping zone<\/b><span style=\"font-weight: 400;\">.<\/span><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-5909\" src=\"https:\/\/blogs.infoblox.com\/wp-content\/uploads\/AWS-Interface-5.png\" alt=\"\" width=\"739\" height=\"206\" srcset=\"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/AWS-Interface-5.png 739w, https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/AWS-Interface-5-300x84.png 300w\" sizes=\"auto, (max-width: 739px) 100vw, 739px\" \/><\/p>\n<p><span style=\"font-weight: 400;\">On step 2, enter the name of the zone for forwarding, in this case <\/span><b>ec2.us-west-1.amazonaws.com<\/b><span style=\"font-weight: 400;\">. If you will be using interface endpoints for other AWS services in this region, you could instead use <\/span><b>us-west-1.amazonaws.com<\/b><span style=\"font-weight: 400;\"> to forward to Route 53 Resolver for all of these services.<\/span><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-5908\" src=\"https:\/\/blogs.infoblox.com\/wp-content\/uploads\/AWS-Interface-6.png\" alt=\"\" width=\"736\" height=\"159\" srcset=\"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/AWS-Interface-6.png 736w, https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/AWS-Interface-6-300x65.png 300w\" sizes=\"auto, (max-width: 736px) 100vw, 736px\" \/><\/p>\n<p>&nbsp;<\/p>\n<p><span style=\"font-weight: 400;\">On step 3, select <\/span><b>Use this set of name servers<\/b><span style=\"font-weight: 400;\">. Use the Add button to add your Route 53 Resolver endpoint as the name servers. Add as many of the available IPs for your Route 53 endpoint as desired to scale availability and capacity.<\/span><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-5907\" src=\"https:\/\/blogs.infoblox.com\/wp-content\/uploads\/AWS-Interface-7.png\" alt=\"\" width=\"738\" height=\"330\" srcset=\"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/AWS-Interface-7.png 738w, https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/AWS-Interface-7-300x134.png 300w\" sizes=\"auto, (max-width: 738px) 100vw, 738px\" \/><\/p>\n<p><span style=\"font-weight: 400;\">On step 4, select <\/span><b>Use this set of name servers<\/b><span style=\"font-weight: 400;\">. Use the Add button to add Infoblox name servers that will serve this forward zone. Please note that for forwarding to work, the name servers must have recursion enabled.<\/span><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-5906\" src=\"https:\/\/blogs.infoblox.com\/wp-content\/uploads\/AWS-Interface-8.png\" alt=\"\" width=\"737\" height=\"261\" srcset=\"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/AWS-Interface-8.png 737w, https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/AWS-Interface-8-300x106.png 300w\" sizes=\"auto, (max-width: 737px) 100vw, 737px\" \/><\/p>\n<p><span style=\"font-weight: 400;\">Save and Close the wizard. Restart the DNS service for Infoblox members when prompted.<\/span><\/p>\n<p><span style=\"font-weight: 400;\">To test the configuration, use Dig or other tools to resolve for ec2.us-west-1.amazonaws.com. Notice the private IP addresses returned in this screenshot.<\/span><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-5905\" src=\"https:\/\/blogs.infoblox.com\/wp-content\/uploads\/AWS-Interface-9.png\" alt=\"\" width=\"1600\" height=\"729\" srcset=\"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/AWS-Interface-9.png 1600w, https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/AWS-Interface-9-300x137.png 300w, https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/AWS-Interface-9-1024x467.png 1024w, https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/AWS-Interface-9-768x350.png 768w, https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/AWS-Interface-9-1536x700.png 1536w\" sizes=\"auto, (max-width: 1600px) 100vw, 1600px\" \/><\/p>\n<h3><b>Conclusion<\/b><\/h3>\n<p><span style=\"font-weight: 400;\">Using DNS forward zones and Route 53 Resolver Inbound Endpoints, you can resolve AWS PrivateLink Interface Endpoints from anywhere, gaining all the advantages of Infoblox solutions and AWS private networking. Combine the use cases shown in this post for resolution across your hybrid and multi-cloud environments.<\/span><\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>AWS Interface Endpoints can be used to access services provided through AWS PrivateLink. The supported services can include some native AWS services, services hosted by other AWS customers, and supported AWS Marketplace Partner Services. PrivateLink allows your VMs and applications to connect to these services using a private IP address, keeping all traffic within AWS [&hellip;]<\/p>\n","protected":false},"author":335,"featured_media":5432,"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":[3],"tags":[126,418,419],"class_list":{"0":"post-5904","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-community","8":"tag-aws","9":"tag-aws-privatelink","10":"tag-aws-interface-endpoints","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>Using Infoblox for Hybrid Name Resolution of AWS PrivateLink Interface Endpoints<\/title>\n<meta name=\"description\" content=\"Amazon Web Services are able to be used in addition to Infoblox services to enhance your network. Learn how Infoblox can improve hybrid name resolution 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\/community\/using-infoblox-for-hybrid-name-resolution-of-aws-privatelink-interface-endpoints\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Using Infoblox for Hybrid Name Resolution of AWS PrivateLink Interface Endpoints\" \/>\n<meta property=\"og:description\" content=\"Amazon Web Services are able to be used in addition to Infoblox services to enhance your network. Learn how Infoblox can improve hybrid name resolution here.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.infoblox.com\/blog\/community\/using-infoblox-for-hybrid-name-resolution-of-aws-privatelink-interface-endpoints\/\" \/>\n<meta property=\"og:site_name\" content=\"Infoblox Blog\" \/>\n<meta property=\"article:published_time\" content=\"2021-02-15T23:21:04+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2022-10-20T21:59:44+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/CNA@2x.png\" \/>\n\t<meta property=\"og:image:width\" content=\"577\" \/>\n\t<meta property=\"og:image:height\" content=\"404\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Jason Radebaugh\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Jason Radebaugh\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"4 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/community\\\/using-infoblox-for-hybrid-name-resolution-of-aws-privatelink-interface-endpoints\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/community\\\/using-infoblox-for-hybrid-name-resolution-of-aws-privatelink-interface-endpoints\\\/\"},\"author\":{\"name\":\"Jason Radebaugh\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/#\\\/schema\\\/person\\\/e73a98dc247a7c6097f549a288228088\"},\"headline\":\"Using Infoblox for Hybrid Name Resolution of AWS PrivateLink Interface Endpoints\",\"datePublished\":\"2021-02-15T23:21:04+00:00\",\"dateModified\":\"2022-10-20T21:59:44+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/community\\\/using-infoblox-for-hybrid-name-resolution-of-aws-privatelink-interface-endpoints\\\/\"},\"wordCount\":890,\"publisher\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/community\\\/using-infoblox-for-hybrid-name-resolution-of-aws-privatelink-interface-endpoints\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/wp-content\\\/uploads\\\/CNA@2x.png\",\"keywords\":[\"AWS\",\"AWS PrivateLink\",\"AWS Interface Endpoints\"],\"articleSection\":[\"Community\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/community\\\/using-infoblox-for-hybrid-name-resolution-of-aws-privatelink-interface-endpoints\\\/\",\"url\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/community\\\/using-infoblox-for-hybrid-name-resolution-of-aws-privatelink-interface-endpoints\\\/\",\"name\":\"Using Infoblox for Hybrid Name Resolution of AWS PrivateLink Interface Endpoints\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/community\\\/using-infoblox-for-hybrid-name-resolution-of-aws-privatelink-interface-endpoints\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/community\\\/using-infoblox-for-hybrid-name-resolution-of-aws-privatelink-interface-endpoints\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/wp-content\\\/uploads\\\/CNA@2x.png\",\"datePublished\":\"2021-02-15T23:21:04+00:00\",\"dateModified\":\"2022-10-20T21:59:44+00:00\",\"description\":\"Amazon Web Services are able to be used in addition to Infoblox services to enhance your network. Learn how Infoblox can improve hybrid name resolution here.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/community\\\/using-infoblox-for-hybrid-name-resolution-of-aws-privatelink-interface-endpoints\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/community\\\/using-infoblox-for-hybrid-name-resolution-of-aws-privatelink-interface-endpoints\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/community\\\/using-infoblox-for-hybrid-name-resolution-of-aws-privatelink-interface-endpoints\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/wp-content\\\/uploads\\\/CNA@2x.png\",\"contentUrl\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/wp-content\\\/uploads\\\/CNA@2x.png\",\"width\":577,\"height\":404},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/community\\\/using-infoblox-for-hybrid-name-resolution-of-aws-privatelink-interface-endpoints\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Community\",\"item\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/category\\\/community\\\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Using Infoblox for Hybrid Name Resolution of AWS PrivateLink Interface Endpoints\"}]},{\"@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\\\/e73a98dc247a7c6097f549a288228088\",\"name\":\"Jason Radebaugh\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/blogs.infoblox.com\\\/wp-content\\\/uploads\\\/jason-pic-thumbnail-96x96.jpg\",\"url\":\"https:\\\/\\\/blogs.infoblox.com\\\/wp-content\\\/uploads\\\/jason-pic-thumbnail-96x96.jpg\",\"contentUrl\":\"https:\\\/\\\/blogs.infoblox.com\\\/wp-content\\\/uploads\\\/jason-pic-thumbnail-96x96.jpg\",\"caption\":\"Jason Radebaugh\"},\"description\":\"Jason is a Senior Manager of Technical Marketing Engineer at Infoblox. He is currently focused on the Universal DDI product suite for consolidated visibility and management of core network services in public and private cloud platforms including Azure, AWS, GCP, VMWare, and others. Jason\u2019s background includes deployment and operation of hybrid and multi-cloud networks, datacenter management, virtualization, and scripting. He holds a Bachelor of Science in Information Technology. Jason is from Washington state and enjoys hiking, biking, and kayaking in his free time.\",\"url\":\"https:\\\/\\\/www.infoblox.com\\\/blog\\\/author\\\/jason-radebaugh\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Using Infoblox for Hybrid Name Resolution of AWS PrivateLink Interface Endpoints","description":"Amazon Web Services are able to be used in addition to Infoblox services to enhance your network. Learn how Infoblox can improve hybrid name resolution 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\/community\/using-infoblox-for-hybrid-name-resolution-of-aws-privatelink-interface-endpoints\/","og_locale":"en_US","og_type":"article","og_title":"Using Infoblox for Hybrid Name Resolution of AWS PrivateLink Interface Endpoints","og_description":"Amazon Web Services are able to be used in addition to Infoblox services to enhance your network. Learn how Infoblox can improve hybrid name resolution here.","og_url":"https:\/\/www.infoblox.com\/blog\/community\/using-infoblox-for-hybrid-name-resolution-of-aws-privatelink-interface-endpoints\/","og_site_name":"Infoblox Blog","article_published_time":"2021-02-15T23:21:04+00:00","article_modified_time":"2022-10-20T21:59:44+00:00","og_image":[{"width":577,"height":404,"url":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/CNA@2x.png","type":"image\/png"}],"author":"Jason Radebaugh","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Jason Radebaugh","Est. reading time":"4 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.infoblox.com\/blog\/community\/using-infoblox-for-hybrid-name-resolution-of-aws-privatelink-interface-endpoints\/#article","isPartOf":{"@id":"https:\/\/www.infoblox.com\/blog\/community\/using-infoblox-for-hybrid-name-resolution-of-aws-privatelink-interface-endpoints\/"},"author":{"name":"Jason Radebaugh","@id":"https:\/\/www.infoblox.com\/blog\/#\/schema\/person\/e73a98dc247a7c6097f549a288228088"},"headline":"Using Infoblox for Hybrid Name Resolution of AWS PrivateLink Interface Endpoints","datePublished":"2021-02-15T23:21:04+00:00","dateModified":"2022-10-20T21:59:44+00:00","mainEntityOfPage":{"@id":"https:\/\/www.infoblox.com\/blog\/community\/using-infoblox-for-hybrid-name-resolution-of-aws-privatelink-interface-endpoints\/"},"wordCount":890,"publisher":{"@id":"https:\/\/www.infoblox.com\/blog\/#organization"},"image":{"@id":"https:\/\/www.infoblox.com\/blog\/community\/using-infoblox-for-hybrid-name-resolution-of-aws-privatelink-interface-endpoints\/#primaryimage"},"thumbnailUrl":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/CNA@2x.png","keywords":["AWS","AWS PrivateLink","AWS Interface Endpoints"],"articleSection":["Community"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www.infoblox.com\/blog\/community\/using-infoblox-for-hybrid-name-resolution-of-aws-privatelink-interface-endpoints\/","url":"https:\/\/www.infoblox.com\/blog\/community\/using-infoblox-for-hybrid-name-resolution-of-aws-privatelink-interface-endpoints\/","name":"Using Infoblox for Hybrid Name Resolution of AWS PrivateLink Interface Endpoints","isPartOf":{"@id":"https:\/\/www.infoblox.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.infoblox.com\/blog\/community\/using-infoblox-for-hybrid-name-resolution-of-aws-privatelink-interface-endpoints\/#primaryimage"},"image":{"@id":"https:\/\/www.infoblox.com\/blog\/community\/using-infoblox-for-hybrid-name-resolution-of-aws-privatelink-interface-endpoints\/#primaryimage"},"thumbnailUrl":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/CNA@2x.png","datePublished":"2021-02-15T23:21:04+00:00","dateModified":"2022-10-20T21:59:44+00:00","description":"Amazon Web Services are able to be used in addition to Infoblox services to enhance your network. Learn how Infoblox can improve hybrid name resolution here.","breadcrumb":{"@id":"https:\/\/www.infoblox.com\/blog\/community\/using-infoblox-for-hybrid-name-resolution-of-aws-privatelink-interface-endpoints\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.infoblox.com\/blog\/community\/using-infoblox-for-hybrid-name-resolution-of-aws-privatelink-interface-endpoints\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.infoblox.com\/blog\/community\/using-infoblox-for-hybrid-name-resolution-of-aws-privatelink-interface-endpoints\/#primaryimage","url":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/CNA@2x.png","contentUrl":"https:\/\/www.infoblox.com\/blog\/wp-content\/uploads\/CNA@2x.png","width":577,"height":404},{"@type":"BreadcrumbList","@id":"https:\/\/www.infoblox.com\/blog\/community\/using-infoblox-for-hybrid-name-resolution-of-aws-privatelink-interface-endpoints\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.infoblox.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Community","item":"https:\/\/www.infoblox.com\/blog\/category\/community\/"},{"@type":"ListItem","position":3,"name":"Using Infoblox for Hybrid Name Resolution of AWS PrivateLink Interface Endpoints"}]},{"@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\/e73a98dc247a7c6097f549a288228088","name":"Jason Radebaugh","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/blogs.infoblox.com\/wp-content\/uploads\/jason-pic-thumbnail-96x96.jpg","url":"https:\/\/blogs.infoblox.com\/wp-content\/uploads\/jason-pic-thumbnail-96x96.jpg","contentUrl":"https:\/\/blogs.infoblox.com\/wp-content\/uploads\/jason-pic-thumbnail-96x96.jpg","caption":"Jason Radebaugh"},"description":"Jason is a Senior Manager of Technical Marketing Engineer at Infoblox. He is currently focused on the Universal DDI product suite for consolidated visibility and management of core network services in public and private cloud platforms including Azure, AWS, GCP, VMWare, and others. Jason\u2019s background includes deployment and operation of hybrid and multi-cloud networks, datacenter management, virtualization, and scripting. He holds a Bachelor of Science in Information Technology. Jason is from Washington state and enjoys hiking, biking, and kayaking in his free time.","url":"https:\/\/www.infoblox.com\/blog\/author\/jason-radebaugh\/"}]}},"_links":{"self":[{"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/posts\/5904","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\/335"}],"replies":[{"embeddable":true,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/comments?post=5904"}],"version-history":[{"count":3,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/posts\/5904\/revisions"}],"predecessor-version":[{"id":8185,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/posts\/5904\/revisions\/8185"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/media\/5432"}],"wp:attachment":[{"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/media?parent=5904"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/categories?post=5904"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.infoblox.com\/blog\/wp-json\/wp\/v2\/tags?post=5904"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}