Actually both MX and HTTPS are the name of a services. That service may or may not use addresses at the same name as the connection end point.
Getaddrinfo(port=25) looking up MX makes some sense. HTTPS for 80 and 443. SRV for those that use SRV. But you also need to add flags to disable the lookup. You won’t know if an implementation supports the protocol you care about so you can’t write portable code. The structure needs to be extended to return the auxiliary data. We have APIs to lookup arbitrary types. They are REQUIRED by STD13 (DNS). They are not hard to use.I really don’t see the need to try to squish each new protocol inside of getaddrinfo. Mark -- Mark Andrews > El 10 sept 2025, a las 6:48, [email protected] escribió: > > >> >> On 9/09/25 18:12, Viktor Dukhovni wrote: >> The getaddrinfo() API has never resolved MX records when handling (node, >> "smtp"), or nSRV records when handling ("node", "xmpp-server"), and I >> see no reson why it has any business attempting anything of the sort >> with HTTPS or SVCB. That logic belongs in "libcurl", ... not >> getaddrinfo(). > Note that a domain name which has an MX record is *not* the name of an SMTP > service, but one with an HTTPS record *is* the name of an HTTP service. > _______________________________________________ > dns-operations mailing list > [email protected] > https://lists.dns-oarc.net/mailman/listinfo/dns-operations _______________________________________________ dns-operations mailing list [email protected] https://lists.dns-oarc.net/mailman/listinfo/dns-operations
