- Last Updated: Saturday, 15 February 2014 16:58
This second article in our series "Anycast DNS" is a recipe for deploying Anycast DNS using static routes. In this article we'll show our recipe for configuring Anycast using static routes, and provide an explanation as to why this is the least optimal way of building an Anycast DNS environment.
Recipe - Single Anycast IP Address 192.168.0.1/32
The goal of this recipe is to configure Anycast DNS on two (2) Linux caching only DNS servers. While this solution can accommodate additional servers, we'll only deal with two servers in our scenario. Our fictitious company, ABC Corporation, uses RIPv2 as its IGP routing routing protocol. NOTE: for this solution there is no requirement for any host-based routing software.
The figure above shows two name servers, Server A & B, deployed on two different subnets 10.0.1.0/24 and 10.0.2.0/24 respectively. Both servers are shown configured with a virtual loopback interface of 192.168.0.1. Each of these systems has an upstream router that will be responsible for originating a static route to the Anycast DNS address of 192.168.0.1/32. The upstream router's job is not only to originate the route, but to redistribute it into the IGP cloud.