Differences

This shows you the differences between two versions of the page.

--- infoblox_uddi:aws_route53 [2026/03/24 21:46] – bstafford
+++ infoblox_uddi:aws_route53 [2026/03/24 21:46] (current) – removed bstafford
@@ Line 1: / Line 1: @@
-====== AWS Route 53 ======
-Both NIOS and BloxOne DDI integrate with AWS Route 53.
-Note that Route-53 Private Zones are only accessible to IP addresses located within the VPCs that are assigned to the Private Zones. This means you cannot query x.x.x.2 from on-prem. This is where NIOS integration comes in very handy.
-The integration is bi-directional. Changes on an AWS Route 53 zone that are made on one platform will sync to the other.
-The advantage of using BloxOne DDI / NIOS is that if you delete a record, you have the recycle bin.
-Syncs every minute (configurable)
-AWS (and Azure) refuse to allow zone transfer from their hosted DNS. This is why syncing to NIOS can be good.
-AWS Route53 Hosted Zones are either "Public hosted" or "Private hosted".
-A single private zone can be made available to multiple VPC's.
-Private hosted zones created using Amazon Route 53 cannot resolve resources outside of AWS VPCs nor can it respond to DNS requests outside of the VPCs.
-For each VPC that you associate with a private hosted zone, you must set the Amazon VPC settings ''enableDnsSupport'' and ''enableDnsHostnames'' and  to true. UPDATE - possibly ''enableDnsResolution'' and ''enableDnsHostnames''
-[[https://docs.infoblox.com/space/BloxOneDDI/186400761/Limitations+of+AWS+Route+53+Integration|BloxOne DDI AWS Limitations]].
-[[https://docs.infoblox.com/space/BloxOneDDI/186680896/Permissions+required+in+AWS+R53|BloxOne DDI AWS Route-53 Required Permissions]]