All the DDNS posts seem to be a bit old, and I have to believe my understanding of SFC is a bit off. So here are my assumptions, and my situation.
I assumed SFC provides Hot Failover for two internet connections (Satellite and cellular for me) and maintains session stability, meaning instead of switching IP addresses in failover my connection to remote things (servers) remains up and functioning. After reading for the DDNS piece, I’m beginning to question this assumption.
I have a server that has access control for inbound connections. So I need to be able to list my IP/dns name for that access control. Originally I assumed the SFC connection would give me that address, but it does not.
Then I found “Find My Peplink” and thought THIS would do it for sure. I turned on Find My Peplink for my device. I see (device).mypep.link in nslookups now.
I also see in the InControl Wan panels dns names for my links, wan.(device).mypep.link and cellular.(device).mypep.link. These do not resolve in nslookup, however.
I also see ic2-detected.(device).mypep.link, that is the same as (device).mypep.link. This one does resolve in nslookup.
However, to solve my server access control problem, none of these addresses are what is shown by myip.com or what my server sees attempting to access it. My server and myip.com agree on what my IP address is to the outside world.
So, my questions are:
-
Does SFC maintain sessions during failover?
-
If it does, how does it do that since the SFC IP address seems to matter not at all?
-
If it doesn’t, how is it better than failover on the router itself?
-
Why does InControl show me DNS names for things that don’t resolve?
-
Why are none of these IP addresses the IP address that is actually presented to the Internet?
Thanks for helping me understand!
-Michele