[external-dns] Private hosts in public DNZ zone

[bonddim]

Hi,
I'm trying to add internal ingress using instruction https://learn.microsoft.com/en-us/azure/aks/create-nginx-ingress-private-controller.
Current controller implementation does not provide configuration options for external-dns controller.

Issue

All hosts from Private DNS Zone private.example.com created in DNS zone example.com also.
This makes impossible to use operator for split-horizon/split-view DNS completely.

Proposal

Add configuration options to NginxIngressController for external-dns controller to filter watched ingresses:

• annotation-filter
• label-filter
• ingress-class (available from v0.13.5)

[OliverMKing]

I like the proposal. I'll look into the solutions for this and get back to you.

[OliverMKing]

Can you use zones that don't have overlapping domains until we have a path forward for this?

[bonddim]

Hi,
As it's not possible to disable external-dns without disabling addon completely, I configured Private DNS Zone only - it's better to have public IPs in private zone, than the other way around.
Public DNZ Zone is managed with additional external-dns deployment with required filters.