|
Hello, We're consolidating our domains in one AWS account. I'm wondering how Lego will behave when I update the registered domain from "old account's zone NS servers" to "new account's zone NS servers". I wish I could switch seamlessly, not failing DNS challenge for "up to 24h", time advertised by AWS for the switch. Lego docs says
How is it determined ? "List all the zones in the current account and find the one with the proper FQDN" ? Because then it would still edit the zone in the old account, ignoring the switch to the new one, hence my DNS challenges would fail. If somehow Lego rely on the NS / SOA records to match the zone hence follow up the switch. That could work more seamlessly, updating the new zone as soon as it's switched. Anyone ever tried that, of understand the code well enough to have an idea ? |
Replies: 1 comment 1 reply
|
Hello, I guess you are using Route53.
lego uses SOA calls to find the zone and them it will query the Route53 API to list the zones and find the zone ID. |
Hello,
I guess you are using Route53.
lego uses SOA calls to find the zone and them it will query the Route53 API to list the zones and find the zone ID.