Jason Kulatunga

not sure what you mean @jvanasco , you should be able to change the domain to anything you want by modifying: https://github.com/AnalogJ/lexicon/blob/master/tests/providers/test_namecheap.py#L15 `lexicontest.com` is a made up domain that someone...

From your image its a bit difficult to determine exactly what the cause is. There are a couple of lexicon providers that need to be changed to support record sets,...

Yeah, currently the Route53 provider does not support record sets, theres an open issue for it: https://github.com/AnalogJ/lexicon/issues/262 I don't use Route53 with lexicon so it's a bit hard for me...

Hey @kapouer This is very similar to #286, so I'm just going to copy my comment from there: lexicon's primary purpose to interact with providers in a standardized way. Theoretically...

Hey @alainwolf Thanks again for researching this. Yeah, I agree. It looks like there's enough support for CAA records across the large providers to make this a meaningful change. If...

Hey @kapouer @rqelibari @alainwolf Yeah, @rqelibari hit the question on the nose. If `CAA` records can be treated like `TXT`/`A`/`CNAME`/etc records where `name` and `content` are the primary requirements, then...

You can use the `update` action to modify an existing record.

Yeah, adding support for record sets to Route53 (and a couple other providers) is still necessary. From what I've seen regarding LetEncrypt clients (like dehydrated, Certbot, Acme.sh) they are usually...

Hey @alexzorin Seems I never got around to responding to your question. Yeah the create operation should be idempotent, creating a record set (or reusing it if it already exists)...

Hey @ravichandra22 Is this issue still occurring for you? Can you try creating the record and waiting a couple minutes before listing the records? Some providers have a significant delay...