▲ | somat 4 days ago | |||||||
DNS (queue the "now you have two problems" meme) Theoretically SRV records can be set in dns to solve the port issue, realistically Nothing uses them so.... You are probably out of luck there. The way SRV records work is you are supposed to ask a network "Where is the foo service at?"(SRV _foo._tcp.my.network.) and dns sez "it's at these machines and ports" (SRV 1(pri) 1(weight) 9980(port) misc.my.network.(target)) https://www.rfc-editor.org/rfc/rfc2782 My personal low priority project is to put mac address in DNS, I am about as far as "I could fit them in an AAAA record" As for specific software recomendations, I am probably not a good source. I run a couple of small openbsd machines(apu-2) that serve most of my home networking needs. But, I am a sys-admin by trade, while I like it, I am not sure how enjoyable others would find the setup. | ||||||||
▲ | nbngeorcjhe 4 days ago | parent | next [-] | |||||||
> My personal low priority project is to put mac address in DNS There's the EUI48 rr type, but I don't know how widely supported it is | ||||||||
| ||||||||
▲ | mdaniel 4 days ago | parent | prev [-] | |||||||
> realistically Nothing uses them Depending on how one defines "nothing," they are honored by XMPP clients. CoreDNS in Kubernetes also publishes SRV records, for any client in-cluster who wishes to look up the port number used by a named port on a v1.Service | ||||||||
|