external-dns with multiple LoadBalancers

[darkpixel]

I'm stumped on having multiple load balancers with external-dns.

If I create an Ingress and point it to a service like so:

---
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: test
  namespace: test
  annotations:
    cert-manager.io/cluster-issuer: "letsencrypt"
    kubernetes.io/ingress.class: test
    external-dns.alpha.kubernetes.io/hostname: test.radacted.tld
    nginx.ingress.kubernetes.io/ssl-redirect: "false"
    nginx.ingress.kubernetes.io/server-snippet: |-
      real_ip_header proxy_protocol;
      set_real_ip_from 10.0.0.0/8;
spec:
  tls:
  - hosts:
      - test.redacted.tld
    secretName: test.redacted.tld-tls
  rules:
    - host: test.redacted.tld
      http:
        paths:
          - path: /
            pathType: Prefix
            backend:
              service:
                name: test
                port:
                  number: 3000

external-dns creates an A record pointing to the correct IP address.
But ingress-nginx gives 400 errors.

If I add add one line:
ingressClassName: test to the spec, ingress-nginx starts working properly, but external-dns switches the IP to the default load balancer for the cluster making it inaccessible.

I've been looking at bug #348.

external-dns.alpha.kubernetes.io/target is mentioned, but the FAQ implied it should be used when external-dns can't find the IP of the controller.

The bug also mentions standing up multiple instances of external-dns, but it's referencing an external-vs-internal DNS setup.

It seems like external-dns should be able to figure out which LoadBalancer an Ingress is attached to based on the kubernetes.io/ingress.class annotation and/or spec.ingressClassName and add the correct IP address.

Am I missing something?