Continuing the discussion from SRV Resource Record supported?:
It’s just a crazy idea but a feature to update SRV Resource records using some UDP-based protocol would enable quite elegant NAT hole punching for custom services.
- The DDNS manager server would need to get information about the affected SRV resource record (Name, Priority, Weight) and the received UDP datagram’s sender port number. The [Server] (target hostname) field could either be supplied by the client or deduced from the sender’s IP address (reverse lookup - could cause problems if multiple hostnames have the same IP address assigned).
- The datagram’s content either has to be digitally signed somehow or a more complex handshake and challenge-response algorithm could be used that would need retransmission logic and so on.
Personally I do have some services in mind where this could be useful but I can live without this feature too.