Skip to content

rfc2136 provider - flags not found #6370

@vstoppe

Description

@vstoppe

What happened:

I was following the Documentation for Setting up the rfc2136 provider with:

  • Helm-Chart 1.2.0
  • Image: latest
  • DNS-Server: Microsoft DNS
  • Kubernetes 1.32.12

I get errors like:

time="2026-04-14T13:21:28Z" level=fatal msg="flag parsing error: unknown long flag '--rfc2136-kerberos-username'"
msg="flag parsing error: unknown long flag '--rfc2136-kerberos-password'"
msg="flag parsing error: unknown long flag '--rfc2136-kerberos-realm'"
msg="flag parsing error: unknown long flag '--rfc2136-gss-tsig'"

These are my flag in the helm-Chart:

    extraArgs:
      - --provider=rfc2136
      - --rfc2136-host=my.dc.mydomain.com
      - --rfc2136-port=53
      - --rfc2136-tsig-axfr
      - --rfc2136-zone=mydomain.com
      - --rfc2136-kerberos-username="DOMAIN\Username"
      - --rfc2136-kerberos-password="SuPeRsEcrEtPaSs"
      - --rfc2136-kerberos-realm=mydomain.com
      - --rfc2136-gss-tsig

What you expected to happen:

I expected that the parameters would be accepted.

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

Configure rfc2136 with these extraArgs.

Checklist

  • I have searched existing issues and tried to find a fix myself
  • I am using the latest release,
    or have checked the staging image to confirm the bug is still reproducible
  • I have provided the actual process flags (not Helm values)
  • I have provided kubectl get <resource> -o yaml output including status
  • I have provided full external-dns debug logs
  • I have described what DNS records exist and what I expected => not reached this state so far

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/bugCategorizes issue or PR as related to a bug.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions