Duplicate TXT and A records on Digitalocean #487
Comments
|
I've had the same problem, I had to disable external-dns :( It created ~2k records (half of them A, half TXT) overnight. |
|
@mikkeloscar something for you to look into? |
|
@hjacobs I'm using cloudflare not DO :) But a quick test on DO shows this problem, so I can confirm there is a bug in the digital ocean provider. Unless someone else want to look into it, I'll try to have a look one of the next days. |
mikkeloscar
added a commit
to mikkeloscar/external-dns
that referenced
this issue
Mar 16, 2018
The DomainRecord response from the Digital Ocean API does not contain the zone as part of the name and thus we must append the zone name when converting it to an endpoint for the plan calculation. Furthermore the root domain is identified by `@` and must be converted to the zone name for the endpoint, and converted back to `@` when the record is submitted to the DO API. https://developers.digitalocean.com/documentation/v2/#retrieve-an-existing-domain-record Fix kubernetes-sigs#487
grimmy
pushed a commit
to grimmy/external-dns
that referenced
this issue
Apr 10, 2018
The DomainRecord response from the Digital Ocean API does not contain the zone as part of the name and thus we must append the zone name when converting it to an endpoint for the plan calculation. Furthermore the root domain is identified by `@` and must be converted to the zone name for the endpoint, and converted back to `@` when the record is submitted to the DO API. https://developers.digitalocean.com/documentation/v2/#retrieve-an-existing-domain-record Fix kubernetes-sigs#487
lou-lan
pushed a commit
to lou-lan/external-dns
that referenced
this issue
May 11, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi guys, i'm trying to use external dns on Digitalocean.
I'm using the v0.5.0-alpha.1
Everything works fine but i've noticed on my digitalocean's network tab that i have a lot of entries with same values
I've create two different deployments and one service for each deployment: 2 deployments 2 services. Domains are correctly created but the list continue to grow.
I haven't scale or done nothing else beyond of this. Anyone in the same situation?
The text was updated successfully, but these errors were encountered: