Skip to main content

Updating your DNS records for the V1 network decommission

Learn how to update your DNS records from the V1 network to V2.

Updated over 2 weeks ago

The V1 redirect network will be decommissioned on November 19, 2025. Any hostnames still pointing to V1 after that date will stop redirecting traffic during planned service interruptions, and will stop redirecting permanently on January 19, 2026.

All updates must be made through your DNS provider.


What you need to do

Step 1: Identify hostnames still using V1

In your urllo dashboard, check hostnames individually by clicking into each one or export your source hostnames to CSV to review in bulk. Look for the following V1 values:

A record values (V1):

  • 34.213.106.51

  • 54.68.182.72

CNAME value (V1):

  • *.easyredirengine.com


Step 2: Update to the V2 values

Update your hostnames to the current V2 records listed in your urllo dashboard:

A record values (V2):

  • 13.248.160.137

  • 76.223.34.124

CNAME value (V2):

  • *.edge.easyredir.net

All updates must be made through your DNS provider.


Step 3: Confirm migration

Ensure that all hostnames no longer point to the old V1 values by pulling your source hostname CSV report again. This confirmation prevents any interruption in redirect traffic when V1 is turned off.


Planned service interruptions before shutdown

To help customers identify and update any remaining V1 hostnames, we will be running a series of planned service interruptions. During each outage, hostnames still on V1 will temporarily stop redirecting.

Outage schedule

  • November 19, 2025 – End of normal V1 service

  • November 25, 2025 – First planned outage (2 hours)

  • December 9, 2025 – Second planned outage (6 hours)

  • January 6, 2026 – Third planned outage (24 hours)

  • January 13, 2026 – Fourth planned outage (72 hours)

  • January 19, 2026V1 permanently turned off


Need Help?

If you need assistance or have questions about updating your DNS records, please contact us—we’re here to help ensure a smooth transition to V2.

Did this answer your question?