How can I publish external node ip for kafka headless service?

[vsfomin]

I can't figure out how to publish a DNS record that will match the node where the kafka Pod is located.
Ingress hosts work fine, CoreDNS can resolve it. But I need to resolve headless services too.
Now I've deployed Kafka 3 brokers and can ping it dnstools# ping kafka-0.kafka.default.svc.cluster.local but I need to ping it from external by ping kafka-0.dh-dev.dmp.example.com

apiVersion: v1
kind: Service
metadata:
  name: kafka
  namespace: default
  annotations:
    external-dns.alpha.kubernetes.io/endpoints-type: NodeExternalIP
    external-dns.alpha.kubernetes.io/hostname: dh-dev.dmp.example.com
    external-dns.alpha.kubernetes.io/internal-hostname: int.dh-dev.dmp.x5.ru
spec:
  ports:
    - name: internal
      protocol: TCP
      port: 29092
      targetPort: 29092
    - name: external
      protocol: TCP
      port: 30092
      targetPort: 9092
  selector:
    service: kafka
  clusterIP: None
  clusterIPs:
    - None
  type: ClusterIP
  sessionAffinity: None
  ipFamilies:
    - IPv4
  ipFamilyPolicy: SingleStack
  internalTrafficPolicy: Cluster

apiVersion: apps/v1
kind: Deployment
metadata:
  name: external-dns
  namespace: external-dns
spec:
  strategy:
    type: Recreate
  selector:
    matchLabels:
      app: external-dns
  template:
    metadata:
      labels:
        app: external-dns
    spec:
      serviceAccountName: external-dns
      containers:
      - name: external-dns
        image: docker-registry.example.com/bitnami/external-dns:0.13.2
        args:
        - --source=ingress
	- --source=service
        - --provider=coredns
        - --log-level=debug # debug only
        env:
        - name: ETCD_URLS
          value: http://etcd.external-dns.svc.cluster.local:2379

CoreDNS Config:

:53 {
    etcd dh-dev.dmp.example.com {
        stubzones
        path /skydns
        endpoint http://etcd.external-dns.svc.cluster.local:2379
    }
    errors
    health {
        lameduck 10s
    }
    ready
    prometheus 0.0.0.0:9153
    forward . /etc/resolv.conf
    cache 30
    loop
    reload
    loadbalance
}

CoreDNS exposed by the NodePort 32333 outside.
I test it like this: dig @100.78.3.38 -p 32333 kafka-0.dh-dev.dmp.example.com or kafka-0.kafka.dh-dev.dmp.example.com and with namespace but the record is not returned.

If I look at ingress like this: dig @100.78.3.38 -p 32333 cdh-redpanda01.dh-dev.dmp.example.com this return to me:

;; ANSWER SECTION:
cdh-redpanda01.dh-dev.dmp.example.com. 30 IN A 100.78.3.40
cdh-redpanda01.dh-dev.dmp.example.com. 30 IN A 100.78.3.38
cdh-redpanda01.dh-dev.dmp.example.com. 30 IN A 100.78.3.39

In external-dns logs I see No endpoints could be generated from service default/ksvc

[ivankatliarchuk]

Selectors do not match. Anyway check the tutorial in docs folder