external-dns icon indicating copy to clipboard operation
external-dns copied to clipboard

Published 20 hours ago • verified publisher icon kubernetes-sigs

AWS Route 53 registry TXT record for alias prefixed fix cname_ instead of a_

Open yohancourbe opened this issue 2 years ago • 6 comments
trafficstars

What happened:

When creating an alias record for a NLB, the TXT record created for registry is prefixed with cname_ while alias is a A record. The bug seems to be cosmetic as is doesn't prevent external-dns to handle it correctly.

What you expected to happen:

Registry record should be prefixed with a_.

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

Create a service of type LoadBalancer with AWS Load Balancer Controller creating the NLB and External DNS creating the alias record.

Anything else we need to know?:

Environment:

  • External-DNS version (use external-dns --version): v0.13.5
  • DNS provider: AWS Route 53
  • Others:

yohancourbe avatar Aug 14 '23 09:08 yohancourbe

Observed same issue on creating alias A record for an ALB.

Environment:

  • External-DNS version (use external-dns --version): v0.13.5
  • DNS provider: AWS Route 53

ibmboy19 avatar Aug 28 '23 03:08 ibmboy19

This issue is not entirely cosmetic, as if you are migrating from an IP address target A record to an alias A record, or vice-versa, external-dns will leak the older TXT record.

alex-hunt-materialize avatar Oct 02 '23 23:10 alex-hunt-materialize

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar Jan 29 '24 13:01 k8s-triage-robot

/remove-lifecycle stale

joaocc avatar Jan 29 '24 15:01 joaocc

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar Apr 28 '24 15:04 k8s-triage-robot

/remove-lifecycle stale

joaocc avatar Apr 29 '24 06:04 joaocc

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar Jul 28 '24 07:07 k8s-triage-robot

/remove-lifecycle stale

yohancourbe avatar Jul 28 '24 13:07 yohancourbe