You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
The text was updated successfully, but these errors were encountered:
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.
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 ismy-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 toCrashLoopBackOff
Anything else we need to know?:
Environment:
0.15.0
):The text was updated successfully, but these errors were encountered: