---
title: "Creating Anycast Configuration"
canonical: "https://docs.infoblox.com/space/BloxOneCloud/35464240/Creating%20Anycast%20Configuration"
format: markdown
---
To create an anycast configuration profile, complete the following:

1. From the Infoblox Portal, click **Network** > **Anycast**.
2. Click **Create Anycast Configuration**.
3. In the **Create Anycast Config** dialog, complete the following:
  - **Name**: Enter the name of the anycast configuration.
  - **Anycast IPv4 Address**: Enter the anycast IPv4 address. <span style="color: #000000">Up to two IPv4 IP addresses may be added when setting up anycast. </span>
  - **Description**: Enter the description of the anycast configuration.
  - **Service**: <span style="color: #000000">From the drop-down, select the service for which you want to configure anycast. For example, if you want to configure anycast for DNS, select </span><span style="color: #000000">**DNS**</span><span style="color: #000000"> from the list.</span>
  - Expand the **Tags** section and add tags for this anycast configuration. For more information, see *[Managing Tags](https://infoblox-docs.atlassian.net/wiki/spaces/BloxOneCloud/pages/35397076)*.
  - Expand the **Service Instances** section, click **Add **and complete the following:
    - **NAME**: Click **Select List** and choose the anycast service instance you have previously configured. This is optional.
  - Expand the **Service Instances** section and add select a list from among the available dropdown options. Optionally, use the search tool to search for a list to add.
4. Click **Save & Close** to save the anycast configuration.
5. After you have created an anycast configuration profile, you can proceed to create an anycast service instance. For information, see <span style="color: #111111">*[Creating Anycast Services](https://infoblox-docs.atlassian.net/wiki/spaces/BloxOneInfrastructure/pages/149815516)*</span>.

### <span style="color: #172b4d">Creating a Static Route to an Anycast IP</span>

1. Configure a static route for the Anycast IP with an administrative distance (AD) that exceeds that of the eBGP route, i.e., greater than 20.
2. Use the command: ip route <anycast-ip/32> <on-prem1-peer-ip> <AD>
3. Similarly, apply the command: ip route <anycast-ip/32> <on-prem2-peer-ip> <AD>
4. Setting a lower AD ensures that the static route will route traffic only when the BGP advertised routes are down.