#919 Server-to-server connection failed: DNS resolution failed
Reporter
Tim
Owner
Zash
Created
Updated
Stars
★ (1)
Tags
Priority-Medium
Milestone-0.9
Type-Defect
Status-Fixed
Tim
on
What steps will reproduce the problem?
1. s2s connection with sinthofen.net (running prosody 0.9.12) from any prosody server
2. the other server will not connect to sinthofen.net, due to: Server-to-server connection failed: DNS resolution failed
dig sinthofen.net resolves the domain successfully
Connections with ejabberd servers work
What version of the product are you using? On what operating system?
Prosody 0.9.12; Debian Jessie (raspbian)
Zash
on
Thanks for the report!
You should have mentioned that you have a TTL of 1.
I looked into this and there's some weird math going on. It sums the TTL and the current (high precision) time, then subtracts the time, then rounds the result downwards. Because time would have passed, this would always result in the value being rounded down to zero, and then it gets expired because the TTL was reached.
What steps will reproduce the problem? 1. s2s connection with sinthofen.net (running prosody 0.9.12) from any prosody server 2. the other server will not connect to sinthofen.net, due to: Server-to-server connection failed: DNS resolution failed dig sinthofen.net resolves the domain successfully Connections with ejabberd servers work What version of the product are you using? On what operating system? Prosody 0.9.12; Debian Jessie (raspbian)
Thanks for the report! You should have mentioned that you have a TTL of 1. I looked into this and there's some weird math going on. It sums the TTL and the current (high precision) time, then subtracts the time, then rounds the result downwards. Because time would have passed, this would always result in the value being rounded down to zero, and then it gets expired because the TTL was reached.
ChangesShould be fixed in https://hg.prosody.im/0.9/rev/2c65f8be38aa
Changes