The admin site tells me that it wants me to set the following SRV records up:
_xmpp-client._tcp.domain.com. 86400 IN SRV 0 5 5222 ofhost.
_xmpps-client._tcp.domain.com. 86400 IN SRV 0 5 5223 ofhost.
_xmpps-server._tcp.domain.com. 86400 IN SRV 0 5 5270 ofhost.
Actually, I have set them up! They exist, on my DNS server, under that domain, under TCP protocol:
Service|Proto|TTL|Type|Priority|Weight|Port|Host
_xmpp-client._tcp|86400|SRV|0 5 5222 ofhost
_xmpps-client._tcp|86400|SRV|0 5 5223 ofhost
_xmpps-server._tcp|86400|SRV|0 5 5270 ofhost
Does anybody know what is missing?
grutto
August 7, 2022, 2:41pm
#2
The domain is missing in your example (_xmpp-client._tcp.YOUR_DOMAIN).
Which result do you get when you try to query the SRV record from within a terminal?
> Linux, OS X> `host -t SRV _xmpp-client._tcp.YOUR_DOMAIN`
> Linux, OS X> `host -t SRV _xmpp-server._tcp.YOUR_DOMAIN`
> Linux, OS X> `dig _xmpp-client._tcp.YOUR_DOMAIN SRV`
> Linux, OS X> `dig _xmpp-server._tcp.YOUR_DOMAIN SRV`
> Windows> `nslookup -querytype=SRV _xmpp-client._tcp.YOUR_DOMAIN`
> Windows> `nslookup -querytype=SRV _xmpp-server._tcp.YOUR_DOMAIN`
If you’re not certain about how the result should look like, try the following example,
dig SRV _xmpp-server._tcp.igniterealtime.org
......
;; ANSWER SECTION:
_xmpp-server._tcp.igniterealtime.org. 300 IN SRV 0 10 5269 xmpp2.igniterealtime.org.
_xmpp-server._tcp.igniterealtime.org. 300 IN SRV 0 10 5269 xmpp.igniterealtime.org.
See also:
https://wiki.xmpp.org/web/SRV_Records#XMPP_SRV_records
https://kingant.net/check_xmpp_dns/?h=jabber.org
The domain is not shown because it is selected, in the router settings, for that whole window, like I said in the OP.
Your queries work:
[user1@localhost]$ host -t SRV _xmpp-client._tcp.domain.com
_xmpp-client._tcp.domain.com has SRV record 0 5 5222 ofhost.domain.com .
[user1@localhost]$
;; ANSWER SECTION:
_xmpp-client._tcp.domain.com. 86400 IN SRV 0 5 5222 ofhost.domain.com .
I only notice that you query _xmpp_server whereas the server UI asks me to create _xmpps_server. Dunno if that matters or is the root cause.
Never mind!
I realized that the server was complaining not about SRV records but about the fact that the Server Host Name included the host name alone. Once I added the domain, to arrive at its FQDN, the warning disappeared.