Skip to content

external-dns cannot automatically change record type in Google DNS #433

@james-masson

Description

@james-masson

I'm migrating from managing DNS records using CNAMEs

ie.

external-dns.alpha.kubernetes.io/target:

to a more standard setup of using an A record to point at a LoadBalancer.

When I removed the target annotation, I get this error:

time="2018-01-04T16:28:41Z" level=info msg="Del records: test-consul.dev.foo.io. CNAME [helm.dev.foo.io.]"
time="2018-01-04T16:28:41Z" level=info msg="Add records: test-consul.dev.foo.io. CNAME [10.1.1.8]"
time="2018-01-04T16:28:42Z" level=error msg="googleapi: Error 400: Invalid value for 'entity.change.additions[0].rrdata[0]': '10.1.1.8', invalid"

It looks like it's trying to replace the CNAME value with an IP, rather than delete the CNAME record and create a new A record.

Manually removing the old CNAME DNS record allows external-dns to do the right thing.

time="2018-01-04T16:31:44Z" level=info msg="Add records: test-consul.dev.foo.io. A [10.1.1.8]"
time="2018-01-04T16:31:44Z" level=info msg="Add records: helm-dev-test-consul.dev.foo.io. TXT ["heritage=external-dns,external-dns/owner=helm-dev"]"

Any hints on how to avoid a manual migration here?

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/provider/gcpIssues or PRs related to gcp providerclosing-soon-if-no-responsehelp wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions