diff options
| author | xengineering <me@xengineering.eu> | 2022-12-04 12:41:39 +0100 |
|---|---|---|
| committer | xengineering <me@xengineering.eu> | 2022-12-04 12:41:39 +0100 |
| commit | 0de21ec65f3c28f2acc947c00c3cb26dc9ea4ecd (patch) | |
| tree | 1d8490f38520908f55f38edbc050920f9eebb15e /README.md | |
| parent | d3a952c04f16723a5dc86fccc5919082dcd1c90e (diff) | |
| download | limox-0de21ec65f3c28f2acc947c00c3cb26dc9ea4ecd.tar limox-0de21ec65f3c28f2acc947c00c3cb26dc9ea4ecd.tar.zst limox-0de21ec65f3c28f2acc947c00c3cb26dc9ea4ecd.zip | |
Implement DNS with a temporary solution
The DNS resolution implemented with this commit uses getaddrinfo() from
the standard library to get an IPv4 address for the domainpart of the
user-given Jabber ID (JID).
This is by far not the process described in [RFC 6120][1]. This XMPP
core standard prefers SRV entry lookups. Taking A records like in this
implementation is referenced as "fallback process".
Furthermore this implementation just takes the first A record it finds
which could also be improved. It could for example be that IPv4 is
blocked in the referenced network and a AAAA IPv6 record is given and
functional. In this case this implementation would needlessly fail to connect.
[1]: https://www.rfc-editor.org/rfc/rfc6120
Diffstat (limited to 'README.md')
0 files changed, 0 insertions, 0 deletions