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

Issues with domain-names containing "-int" #45

Open
dti-horvath opened this issue Dec 21, 2023 · 0 comments
Open

Issues with domain-names containing "-int" #45

dti-horvath opened this issue Dec 21, 2023 · 0 comments

Comments

@dti-horvath
Copy link

We stumbled upon an issue, where for domain names containing "-int" in their name, the ns1-webhook would not create the "_acme-challenge" entry in NS1.
So we would not see the log line "trace.go:116] Trace[114712491]: "Create" url:/apis/acme.nsone.net/v1alpha1/ns1 [...]" when using "-int" in the domain name.

What did not work:

  • login-int.example.com
  • cloud-int.example.com

What did work:

  • loginint.example.com
  • login-in.example.com
  • login-string.example.com
  • login.example.com
  • login-stage.example.com

Such a Certificate looks like this:

apiVersion: cert-manager.io/v1
kind: Certificate
metadata:
  name: login-int.example.com
spec:
  dnsNames:
  - "login-int.example.com"
  issuerRef:
    name: example-domain-letsencrypt-staging
    kind: ClusterIssuer
  secretName: test-example-tls-secret

Changing only the single entry in dnsNames to the mentioned values.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant