{"id":2899,"date":"2016-02-25T18:53:10","date_gmt":"2016-02-25T18:53:10","guid":{"rendered":"https:\/\/live-infoblox-blog.pantheonsite.io\/?p=2899"},"modified":"2020-05-06T10:30:04","modified_gmt":"2020-05-06T17:30:04","slug":"using-route-53-four-potholes-that-can-ruin-your-ride","status":"publish","type":"post","link":"https:\/\/www.infoblox.com\/blog\/company\/using-route-53-four-potholes-that-can-ruin-your-ride\/","title":{"rendered":"Using Route 53? Four Potholes That Can Ruin Your Ride"},"content":{"rendered":"

Back in August 2015, we announced\u00a0Infoblox DDI for AWS and Public Cloud<\/a>,\u00a0which extended our industry-leading DNS and IP address management solution to the public cloud.<\/p>\n

Many AWS users tell us they already use Amazon\u2019s Route 53 DNS service, but still asked to be able to use Infoblox with Route 53. Why?<\/p>\n

While Route 53 offers private DNS functionality within AWS VPCs, an enterprise using a hybrid cloud or connecting back to an on-premises datacenter faces four challenges:<\/p>\n

    \n
  1. Limited DNS:<\/strong>\u00a0DNS resolution or responses to queries are isolated within their AWS network, which causes issues when communication is needed outside that particular AWS Private Hosted Zone. To circumvent this, IT teams often spin up multiple BIND servers to pass DNS traffic outside the isolated AWS zones. This approach adds complexity and lacks consistency across disparate DNS approaches.<\/li>\n
  2. No IPAM:<\/strong>\u00a0AWS has no IP address management (IPAM) solution for virtual instances, which adds operational overhead and time for day-to-day management, troubleshooting, and reclamation of network and IP addresses. It also adds time to gather data required for auditing and compliance purposes.<\/li>\n
  3. Lack of visibility for hybrid cloud:<\/strong>\u00a0Without a consistent DNS and IPAM solution across the hybrid cloud, enterprise IT has to use several tools to access DNS and IP address data. This leads to longer troubleshooting times, reduces the ability to perform network planning, and increases security risks. It also increases inconsistencies in enterprise-wide management of the DNS and IP address space.<\/li>\n
  4. Limited DNS security:<\/strong>\u00a0Route 53 has limited DNS security for both AWS and hybrid cloud deployments. Data exfiltration using DNS tunneling and malware that uses DNS to spread are common DNS-based attacks that can cripple IT networks.<\/li>\n<\/ol>\n

    Since most users will need to merge off AWS Route 53 to communicate across on-premises and\/or other cloud platforms, they need to understand how to make these different traffic lanes work together\u2014or have a major crash.<\/p>\n

    With the newest release of Infoblox DDI for AWS and Public Cloud in January, we added functionality that enables Infoblox to work directly with Route 53. So now users can leverage Route 53 within AWS but have a consistent and consolidated view across multiple platforms.<\/p>\n

    With the Route 53 integration, Infoblox users can:<\/p>\n