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
I was migrating from Google Cloud DNS to TransIP with a new domain name, and it stopped working.
These three log lines keep repeating. I'm assuming the first one is the real problem and the others are just noise.
time="2021-09-11T09:03:30Z" level=error msg="unknown time zone Europe/Amsterdam"
W0911 09:03:44.296169 1 transport.go:288] Unable to cancel request for *instrumented_http.Transport
W0911 09:04:14.299905 1 transport.go:288] Unable to cancel request for *instrumented_http.Transport
No DNS records were added.
What you expected to happen:
I hoped it'd add all our subdomains to the new domain at TransIP.
How to reproduce it (as minimally and precisely as possible):
I'm not doing anything special, so I suppose just using external-dns with TransIP and maybe a .nl domain name?
Anything else we need to know?:
I wasn't able to figure out where the "unknown time zone Europe/Amsterdam" error message was even coming from.
Environment:
External-DNS version (use external-dns --version): 0.9.0
DNS provider: TransIP
Others:
The text was updated successfully, but these errors were encountered:
What happened:
I was migrating from Google Cloud DNS to TransIP with a new domain name, and it stopped working.
These three log lines keep repeating. I'm assuming the first one is the real problem and the others are just noise.
No DNS records were added.
What you expected to happen:
I hoped it'd add all our subdomains to the new domain at TransIP.
How to reproduce it (as minimally and precisely as possible):
I'm not doing anything special, so I suppose just using external-dns with TransIP and maybe a .nl domain name?
Anything else we need to know?:
I wasn't able to figure out where the "unknown time zone Europe/Amsterdam" error message was even coming from.
Environment:
external-dns --version
): 0.9.0The text was updated successfully, but these errors were encountered: