Configuring DNS Anycast in Universal DDI (2577)

Scenario

You already have DNS services running on oph1.techblue.net and oph2.techblue.net, but you want clients to use a single DNS address that remains reachable as long as at least one DNS server is online. To provide that resiliency, your team decided to use DNS anycast with BGP and advertise the shared IPv4 address 10.24.7.53 from both NIOS-X servers. Your goal is to create the anycast configuration, attach it to DNS anycast service instances on both servers, verify the anycast route is reachable, and confirm that DNS queries succeed through the anycast address.

Estimated Completion Time

  • 20 to 30 minutes

Prerequisites

Tasks

  1. Create Anycast Configuration.

  2. Create Anycast Service Instances.

  3. Verify Anycast Service is Online.

  4. Verify DNS Service over Anycast.

Task 1: Create Anycast Configuration

In the Infoblox Portal, navigate to Network → Anycast and create an anycast configuration named Techblue DNS Anycast BGP. Set the anycast IPv4 address to 10.24.7.53 and set Service to DNS. This creates the shared anycast object that both NIOS-X servers will advertise.

Task 2: Create Anycast Service Instances

Create two Anycast service instances and attach both to the anycast configuration from Task 1. Use the values below.

Service Instance

ASN

Keepalive

Hold Down

Neighbor Router

Remote ASN

Techblue Anycast Service 1

65400

4

16

10.100.0.1

65247

Techblue Anycast Service 2

65400

4

16

10.200.0.1

65247

The Anycast Profile would be Techblue DNS Anycast BGP (10.24.7.53).

After saving both service instances, wait a few minutes for the anycast services to start.

Task 3: Verify Anycast Service is Online

In Network → Anycast, confirm that Techblue DNS Anycast BGP shows a green Active status and that both service instances appear online. Then switch to vyos-router, log in with vyos / vyos, run show ip bgp, and confirm that the router shows routes associated with oph1 (10.100.0.110) and oph2 (10.200.0.110). Finally, from testing-linux, run ping 10.24.7.53 and confirm that the anycast address is reachable. Optionally, power off oph1 and oph2 one at a time while the ping continues to verify that the address stays reachable as long as one server remains online.

Task 4: Verify DNS Service over Anycast

From testing-linux, run dig @10.24.7.53 techblue.net. A and confirm that the anycast address returns a DNS response. This verifies that the shared anycast address is not only reachable, but is also serving DNS successfully.


Solutions

Task 1 Solution: Create Anycast Configuration

Start by creating the shared anycast object. This defines the single IPv4 address that clients will use, while the service instances you create later will advertise it from both NIOS-X servers.

  1. Log in to your lab’s jump-desktop.

  2. Use the Education Infoblox Portal credentials to sign in to the Infoblox Portal.

  3. Navigate to Network → Anycast.

  4. Click Create Anycast Configuration.

    image-20260520-121935.png
  5. In the Name field, enter Techblue DNS Anycast BGP.

  6. In Anycast IPv4 Address, enter 10.24.7.53.

  7. In Service, select DNS.

    image-20260520-122049.png
  8. Click Save & Close.

Task 2 Solution: Create Anycast Service Instances

After the anycast configuration exists, create service instances on both NIOS-X servers so they can advertise the same DNS anycast address through BGP. The values are nearly identical on both servers, with the only operational difference being the neighbor router address.

  1. In the Infoblox Portal, navigate to Network → Services & Servers → Protocol Service.

  2. Click Create Service and select Anycast.

    image-20260520-122248.png
  3. In the General Info tab, enter Techblue Anycast Service 1 in the Name field.

  4. Click Select Server, choose oph1.techblue.net, and click Select.

  5. Click Next or open the Anycast Settings tab.

    image-20260520-122503.png
  6. In the ANYCAST PROFILE section, click Add.

  7. Select Techblue DNS Anycast BGP (10.24.7.53) and enable BGP.

    image-20260520-122646.png
  8. In the BGP CONFIGURATION section, set ASN to 65400, BGP Timers to 4, and Hold Down to 16.

  9. In the BGP NEIGHBOR CONFIGURATION section, click Add and set Neighbor Router to 10.100.0.1 and Remote ASN to 65247.

  10. Click Add.

  11. Click Next, review the summary.

    image-20260520-122915.png
  12. Click Save & Close.

  13. Repeat steps 2 through 10 to create Techblue Anycast Service 2 on oph2.techblue.net.

  14. For Techblue Anycast Service 2, keep the same anycast and BGP settings, but set Neighbor Router to 10.200.0.1.

    image-20260520-123127.png
  15. Click Save & Close.

  16. You may need to wait a few minutes for the Anycast services to start on both instances.

    image-20260520-123419.png

Task 3 Solution: Verify Anycast Service is Online

Before testing DNS itself, verify that the anycast advertisement and BGP routing are working. If the route is not active yet, DNS over anycast will fail even if the DNS services themselves are healthy.

  1. In the Infoblox Portal, navigate to Network → Anycast.

  2. Check the status of Techblue DNS Anycast BGP and confirm it is green and Active.

  3. Confirm that both anycast service instances appear online to the right of the configuration.

    image-20260520-123528.png
  4. Switch to the virtual machine vyos-router.

  5. Log in with username vyos and password vyos.

  6. Run show ip bgp.

  7. Review the routing table and look for the IP addresses of oph1 (10.100.0.110) and oph2 (10.200.0.110).

    image-20260520-123710.png
  8. Switch to testing-linux and open a terminal window.

  9. Run ping 10.24.7.53 and confirm that the anycast address responds.

    image-20260520-123805.png
  10. Optionally, power off oph1 and oph2 one at a time while keeping the ping running to confirm that 10.24.7.53 remains reachable as long as one server stays online.

Task 4 Solution: Verify DNS Service over Anycast

Now test DNS over the shared anycast address. This confirms that the address is not only reachable through BGP, but is also serving DNS successfully for clients.

  1. On testing-linux, open a terminal window if one is not already open.

  2. Run dig @10.24.7.53 techblue.net. A.

  3. Confirm that the query returns a DNS response from the anycast address.

    image-20260520-124001.png