Best Practice for HA1 IP address

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Best Practice for HA1 IP address

L5 Sessionator

I have a lots of customers who uses HA pair with 1.1.1.1/30 and 1.1.1.2/30 for HA1 port.

This HA1 port connected directly. And reason for selecting these IPs are because nobody was using it in the past.

 

Today, I read this article:

https://blog.cloudflare.com/announcing-1111/

https://www.theverge.com/2018/4/1/17185732/cloudflare-dns-service-1-1-1-1

 

According to this thread, it sounds okay to keep using 1.1.1.1 for HA1, though I'm curious... do they need to change IPs?

 

In addition, with my quick test in my lab, I can access to 1.1.1.1 DNS server even HA1 is using 1.1.1.1, thus I believe 1.1.1.1 for HA1 is okay.

 

Regards.

Emr

1 accepted solution

Accepted Solutions

Cyber Elite
Cyber Elite

@emr_1,

HA links are usually directly connected and therefore the IP doesn't really matter since the traffic will never be routed.

APNIC releasing 1.1.1.1 to CloudFlare is one of the most unreasonable things I've seen in a long time. APNIC has attempted to analyze how much traffic attempt to route to 1.1.1.1 multiple different times and have been unable; CloudFlare offering to do this for them in exchange of allowing them to utilize the IP is the only reason they were allocated the address. 

View solution in original post

3 REPLIES 3

Cyber Elite
Cyber Elite

@emr_1,

HA links are usually directly connected and therefore the IP doesn't really matter since the traffic will never be routed.

APNIC releasing 1.1.1.1 to CloudFlare is one of the most unreasonable things I've seen in a long time. APNIC has attempted to analyze how much traffic attempt to route to 1.1.1.1 multiple different times and have been unable; CloudFlare offering to do this for them in exchange of allowing them to utilize the IP is the only reason they were allocated the address. 

Hello,

I agree with @BPry. That said I always use RFC 1918 addresses for my HA IP's. This way they can never get routed externally even if the two devices have to be be routed if they are in different locations, etc.

 

Regards,

oh wow, this is a pretty important thing to consider when 'nonchalantly' using 1.1.1.1 instead of a proper RFC1918 or RFC5735 (documentation) IP

 

just thinking dns sinkhole,....

Tom Piens
PANgurus - Strata specialist; config reviews, policy optimization
  • 1 accepted solution
  • 3456 Views
  • 3 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!