Skip to content

--domain-filter functionality #64

@hfi-wiit

Description

@hfi-wiit

Hi,

we currently use external-dns with its designate provider.
We have an openstack tenant that holds multiple zones, however each cluster only needs to access a specific domain/zone.
So we have access tokens that only have access to the zone in question and our external-dns is started with --domain-filter=mysub.my.domain.

Switching to your webhook, everything worked in a testing environment without limited access.
However in production, where access is limited, I get a lot of errors in logs like the following.

[pod/external-dns-895bb548b-zd9jq/webhook] time="2025-09-15T10:33:38Z" level=error msg="Failed to get Records: Successfully re-authenticated, but got error executing request: Expected HTTP response code [200 204 300] when accessing [GET https://.../v2/zones/d28f0ff7-.../recordsets], but got 401 instead: {\"error\": {\"code\": 401, \"title\": \"Unauthorized\", \"message\": \"The request you have made requires authentication.\"}}"

It actually seems to try to access all the zones, not only the one it is meant to.
Is there a way to limit access to the requested zone?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions