SRV records not supported by TXT registry?

[cbrianhill]

Hi, I have created a DNSEndpoint like this:

apiVersion: externaldns.k8s.io/v1alpha1
kind: DNSEndpoint
metadata:
  name: dns-endpoint
  namespace: default
spec:
  endpoints:
  - dnsName: [port].[protocol].[domain]
    recordTTL: 60
    recordType: SRV
    targets:
    - 10 100 [port] [pod]

I notice that external-dns will create the SRV record for me, but it skips updates due to an owner ID mismatch:

time="2025-12-09T20:18:01Z" level=debug msg="Skipping endpoint [old_endpoint_value] because owner id does not match, found: \"\", required: \"[actual_owner_id]\""
time="2025-12-09T20:18:01Z" level=debug msg="Skipping endpoint [new_endpoint_value] because owner id does not match, found: \"\", required: \"[actual_owner_id]\""

Route53 is my provider and I added --managed-record-types SRV to my command line. I also added crd as a source.

Has anyone experienced this before? My suspicion is that I'm reaching this error because the txt registry doesn't list SRV in its supported record types here. It seems like adding an entry to this list would be relatively simple, but I'm cautious in case there is a known reason why we shouldn't or can't use the txt registry to track SRV records. Can anyone shed some light on this?