Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for a DNS provider per ACME domain #2773

Closed
MaikelH opened this issue Jan 27, 2018 · 5 comments
Closed

Support for a DNS provider per ACME domain #2773

MaikelH opened this issue Jan 27, 2018 · 5 comments

Comments

@MaikelH
Copy link

@MaikelH MaikelH commented Jan 27, 2018

Do you want to request a feature or report a bug?

feature

What did you do?

Tried to set different a DNS provider for a domain inacme.domains

What did you expect to see?

Currently it is only possible to set a global dnsProvider for acme. Since we have domains on different registries we would like to use a different dnsProvider for some domains. For an example how this could work see the example configuration below.

It would be nice if you could still set a default dnsProvider and then have the ability to override it in the acme.domains section.

    [acme]
    email = "test@test.com"
    storage = "acme.json"
    entryPoint = "https"
    onDemand = false
    dnsProvider = "route53"
    acmeLogging = true

    [[acme.domains]]
       main = "abc.com"
       sans = []

    [[acme.domains]]
      main = "1234.com"
      dnsProvider =  "namecheap"
      sans = []

In the example above abc.com will default to route53 and 1234.com will use the override (namecheap)

@ldez

This comment has been minimized.

Copy link
Member

@ldez ldez commented Jan 27, 2018

Duplicate of #2710

@ldez ldez marked this as a duplicate of #2710 Jan 27, 2018
@ldez ldez closed this Jan 27, 2018
@MaikelH

This comment has been minimized.

Copy link
Author

@MaikelH MaikelH commented Jan 27, 2018

#2710 is not a duplicate of this issue. #2710 describes different dnsProviders per entrypoint, not per domain.

In the config we use have only one https endpoint which serves multiple domains. The feature as described in #2710 will not solve the issue since we are still forced to use the same dnsProvider for all domains under that entrypoint.

@ldez ldez reopened this Jan 27, 2018
@ldez ldez marked this as not a duplicate of #2710 Jan 29, 2018
@Berndinox

This comment was marked as off-topic.

Copy link

@Berndinox Berndinox commented Sep 14, 2018

+1

moqmar added a commit to moqmar/traefik that referenced this issue Apr 26, 2019
Fix containous#2773 and containous#3378, and make environment variables for the providers configurable from the configuration provider

Example:

[acme.dnsChallenge]
  provider = "route53"
  environment = ["AWS_ACCESS_KEY_ID=abcd", "AWS_SECRET_ACCESS_KEY=efgh"]

[[acme.domains]]
  main = "*.example.org"
  sans = ["example.org"]
  challenge = "dns" # dns/http/tls
  dnsProvider = "cloudflare"
  dnsEnvironment = ["CF_API_EMAIL=mail@example.org", "CT_API_KEY=1234"]
moqmar added a commit to moqmar/traefik that referenced this issue Apr 26, 2019
Fix containous#2773 and containous#3378, and make environment variables for the providers configurable from the configuration provider

Example:

[acme.dnsChallenge]
  provider = "route53"
  environment = ["AWS_ACCESS_KEY_ID=abcd", "AWS_SECRET_ACCESS_KEY=efgh"]

[[acme.domains]]
  main = "*.example.org"
  sans = ["example.org"]
  challenge = "dns" # dns/http/tls
  dnsProvider = "cloudflare"
  dnsEnvironment = ["CF_API_EMAIL=mail@example.org", "CT_API_KEY=1234"]
moqmar added a commit to moqmar/traefik that referenced this issue Apr 29, 2019
Fix containous#2773 and containous#3378, and make environment variables for the providers configurable from the configuration provider

Example:

[acme.dnsChallenge]
  provider = "route53"
  environment = ["AWS_ACCESS_KEY_ID=abcd", "AWS_SECRET_ACCESS_KEY=efgh"]

[[acme.domains]]
  main = "*.example.org"
  sans = ["example.org"]
  challenge = "dns" # dns/http/tls
  dnsProvider = "cloudflare"
  dnsEnvironment = ["CF_API_EMAIL=mail@example.org", "CT_API_KEY=1234"]
@tehKapa

This comment has been minimized.

Copy link

@tehKapa tehKapa commented May 12, 2019

I’ve the same need. use the dns challenge with different providers

@ldez

This comment has been minimized.

Copy link
Member

@ldez ldez commented May 14, 2019

Close in favor of #4872 - Feel free to subscribe there for updates.

@ldez ldez closed this May 14, 2019
@containous containous locked and limited conversation to collaborators Sep 1, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
6 participants
You can’t perform that action at this time.