Yes, using mypep.link through InControl2 you can set a unique dns name. eg martins-lab.mypep.link
If you do a DNS lookup against that DNS name incontrol2 will return the WAN IPs of WAN1 and WAN2 (and WAN3 and WAN4 etc). So if you ping martins-lab.mypep.link you will be pinging WAN1 so long as its healthy. If WAN1 fails, then InControl2 updates the DNS entries and a ping to martins-lab.mypep.link will resolve to the IP address of WAN2 instead.
Whats also nice about mypep.link is that you also get DNS entries per WAN port so:
wan2.martins-lab.mypep.link would resolve to the respective IPs.
But perhaps of most use to you since you will be using failover is the InControl2 detected IP address (the one that is actively being used right now for traffic) and this becomes
Yes exactly right - that’s the limitation of using IP addresses for remote access - they are typically tied to a form of internet access. You get round this by either using dynamic DNS above, or you move to VPN for remote access which is more secure and generally easier as you don’t care or need to know what the external IP addressing is.
An added bonus of using either DDNS or VPN is that you can add additional connectivity into the mix, so an LTE connection for example to provide additional bandwidth and resilience.