Background:
Just to make sure my understanding of your set-up is correct:
Two routable ISP feeds, with two different “breakout” addresses, say A and B
One (Balance?) multi-WAN Peplink router, with A and B being two (of the) WANs. Call it “Router”
Outbound rules work - you can direct outgoing traffic to A or B as you see fit. The recipient of traffic through A or B will see the routable A (or B) breakout address as the source.
You want the breakout address to be the one used by devices contacting Router
A is preferred for incoming access whenever available, B only when A is not
You have a DNS name for traffic destined for the above Router, say “router.domain.com”.
Assumption:
You want the traffic addressed to router.domain.com to be sent to A, unless A is down, in which case it should go to B.
Suggested solution
First of all - this is a DNS challenge (as you point out). You want a DNS resolution for router.domain.com to resolve to A or B as appropriate.
One way to achieve this is for Router to update a dynamic DNS server with its preferred IP address as A whenever A is available, and B if A is not.
Peplink’s Find My Peplink Service will handle it:
Enroll Router in InControl2
On the Device Detail page, activate “Find My Peplink Service”
Provide a name in “Find My Peplink Address” (e.g. “MyRouter”)
That creates a FQDN, “MyRouter.mypep.link”. It will resolve to the IP address Router employs to contact IC2.
Create an outbound policy on Router that prioritizes WAN1 for connections to IC2. Create a new priority rule, the source being “any”, the destination being “peplink.com”, the protocol being UDP and the port 5246. WAN1 as priority 1, WAN2 as priority 2. (If you don’t want the domain check, simply omit that component and require all traffic to UDP port 5246 to go to WAN1 if available, which is what you want anyway)
Create a CNAME record at your DNS server, “router.domain.com CNAME MyRouter.mypep.link.”
That should do it - all access to router.domain.com will resolve to A (if up), and to B (if A is down).
If i can add dns for testcompany.com from the PREFIX A and the testcompany.com from the Prefix B
like below in my domain registrars DNS server (external ) testcompany.com 1.1.1.1 ( from ISP A) testcompany.com 2.2.2.2 ( from ISP B)
What need to be done from the peplink side
What you describe seems to be a different approach than the one I suggested. I must admit that I do not understand the particulars of what you propose, so I cannot answer your question.
InControl2 (“IC2”) is a network management service for your Peplink devices (see https://www.peplink.com/software/network-management-solution-incontrol-2/). The 1st year is covered by your purchase warranty, subsequent years may be covered in various ways (e.g., as part of one of the Care packages, or by a direct subscription). The cost depends on the kind of device you are enrolling. I believe it starts at US$29/year.
This sounds like a DNS issue - you want the users/clients (on the internet side of things) to gain access to your web server by means of ISP A (preferred) or ISP B (if A is down) without having to do anything on the client side of things (in other words, invisibly).
