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

Wildcard domain can't be excluded #4766

Closed
GitHanter opened this issue Sep 22, 2024 · 3 comments
Closed

Wildcard domain can't be excluded #4766

GitHanter opened this issue Sep 22, 2024 · 3 comments
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@GitHanter
Copy link

GitHanter commented Sep 22, 2024

What happened:
time="2024-09-22T14:36:23Z" level=info msg="add *.xxx.com IN A -> 192.168.1.220"
time="2024-09-22T14:36:23Z" level=fatal msg="Failed to do run once: Domain '*.xxx.com' is not valid"

What you expected to happen:

Provide configuration option to exclude wildcard domains.

How to reproduce it (as minimally and precisely as possible):

I installed external-dns by Helm, configured with source ingress, when I try to create a ingress with TLS certificate domain name *.xxx.com and a certificate issuer with DNS-01 resolver, host is my-ingress.xxx.com, external-dns try to call Pihole API to create an A record for *.xxx.com, which throws the error and external-dns turn to CrashLoopBackOff

Anything else we need to know?:

Environment:

  • External-DNS version (use 0.15.0):
  • DNS provider: PiHole
  • Others:
@GitHanter GitHanter added the kind/bug Categorizes issue or PR as related to a bug. label Sep 22, 2024
@GitHanter
Copy link
Author

GitHanter commented Sep 25, 2024

Oh.. For this issue, we have another ticket #4621

@GitHanter
Copy link
Author

Fixed with #4904
/close

@k8s-ci-robot
Copy link
Contributor

@GitHanter: Closing this issue.

In response to this:

Fixed with #4904
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

2 participants