Hi everyone, I know it’s possible to make a CNAME record on our domain that points to the Find My Peplink address for a device, but we offer the devices as part of a monthly managed service to our customers. So instead of providing the customer with the name.mypep.link address, if I was to create a CNAME on our custom domain hosted by Route 53, such as customername.ourdomain.com and provide them that, I know that’s of course possible but what if they then want to make their own CNAME record on their domain, such as remote.theirdomain.com which points to customername.ourdomain.com? Would there be any potential problems in doing it this way?
I’m mainly concerned about it slowing down, as right now if WAN1 is up and the mypep.link resolves to that, and I disconnect it, it takes 20-30 seconds on average (but sometimes up to 2 minutes) before that mypep.link address resolves to the secondary WAN connection. Same with when the WAN1 is restored, it’s on average 20-30 seconds to update. If I did it as the above, a CNAME on our domain pointing to the mypep.link and then the customer has a CNAME on their domain pointing to ours, should it update just as quickly or anything I should be aware of in that case?