Strange DNS-Simply.com behaviour
-
While creating a certificate for HAProxy I am seeing some strange behaviour in the DNS-Simply.com validation.
I have few domains under different accounts at simply.com
Let's call them domain1.com and domain2.com.
domain1.com with it's own account name and API key
domain2.com with it's own account name and API keyWhen issuing the certificate it fails immediately with domain1.com but using credentials from domain2.com which obviously doesn't contain DNS for domain1.com.
I can see it in the log that the URL is using the account name for domain2.com when trying to add the TXT record for _acme_challenge.domain1.comIs this default behaviour or is there a bug?
Regards,
Jens -
@gallenat0r said in Strange DNS-Simply.com behaviour:
While creating a certificate for HAProxy I am seeing some strange behaviour in the DNS-Simply.com validation.
I have few domains under different accounts at simply.com
Let's call them domain1.com and domain2.com.
domain1.com with it's own account name and API key
domain2.com with it's own account name and API keyWhen issuing the certificate it fails immediately with domain1.com but using credentials from domain2.com which obviously doesn't contain DNS for domain1.com.
I can see it in the log that the URL is using the account name for domain2.com when trying to add the TXT record for _acme_challenge.domain1.comIs this default behaviour or is there a bug?
Regards,
JensWorkaround was to create a certificate for each simply.com account and then do shared frontend in HAproxy.