No, I can't find any. Look like domains pointed to surge.sh have internal write access by anyone with an account when it should be private write access by only me (at least in first time deploy).
Hi, I think I figured out how it works! Authentication is done by checking if the e-mail of your Surge account and DNS provider is matching. So you need to use the same e-mail for both, otherwise, you will get "Aborted - you do not have permission to publish to..." I hope it helps! :)
No, I can't find any. Look like domains pointed to surge.sh have internal write access by anyone with an account when it should be private write access by only me (at least in first time deploy).
Hi, I think I figured out how it works! Authentication is done by checking if the e-mail of your Surge account and DNS provider is matching. So you need to use the same e-mail for both, otherwise, you will get "Aborted - you do not have permission to publish to..." I hope it helps! :)
Thanks for your answer...
It's seem inflexible to force that policy.