Azure Insights: Route Server; Using External-DNS with Azure DNS and AKS

Azure pros share their thoughts on Route Server and how to use External-DNS with Azure DNS and Kubernetes Service.

Making sense of Azure Route Server

An author on We do Azure shared thoughts on Azure Route Server. In March, Microsoft announced new routing features in preview. Route Server, as its name implies, is intended to support dynamic routing. Users are able to swap routes by BGP between NVA and a VNet, potentially swapping between NVA and Azure SDN.

[T]he key to understanding this service is having familiarity with implementing an NVA in an environment without it. So, say we build a Palo Alto, or any vendor NVA in our VNET. It is a flat VNET which has several subnets. And we want all our traffic to route via the NVA for filtering. Without Route Server, we have to implement single, or multiple, Route Tables on the subnets and manually manage route modifications on the NVA. Meaning a lot of admin overhead and room for potential user error.

The author explained that Route Server gets rid of these requirements, using BGP to expose VNet system routing tables and letting a NVA write directly. Once setup, users are able to carry out peering and configuration for NVAs. The offering also works with VNets, and according to the author should be enabled on the VNet itself. Users can educate themselves more with documentation.

Using External-DNS with Azure DNS and AKS

FREE Membership Required to View Full Content:

Joining MSDynamicsWorld.com gives you free, unlimited access to news, analysis, white papers, case studies, product brochures, and more. You can also receive periodic email newsletters with the latest relevant articles and content updates.
Learn more about us here

Get full access

or login