aenigma icon indicating copy to clipboard operation
aenigma copied to clipboard

SRV Record Not Working

Open kilo6eight opened this issue 5 years ago • 7 comments

The configuration/setup says:

The | SRV | record | 5 1 5223 ae.mydomain.com. | for DNS name | _xmpps-client._tcp.mydomain.com | still appears NOT to be registered.

On my domain control panel for SRV I have the following DEFAULT options:

Type: Name: @ TTL: 900 Priority: 10 Weight: 0 Port: Content:

I replace it with the following:

Type: SRV Name: _xmpps-client._tcp.mydomain.com (I remove the @ that is prefilled) TTL: 60 Priority: 5 Weight: 1 Port: 5223 Content: ae.mydomain.com. (Note it has a "." at the end. That is how it's outputted on the terminal so I just copied and pasted. I tried in case it was a developer mistake both with the "." and without the "." at the end. Clarify?)

This is exactly what I am typing in. I am using NJALLA as the domain registrar since it is pretty reputable and recommended on privacytools.io

It's not working what am I doing wrong?

kilo6eight avatar May 19 '19 09:05 kilo6eight

Hi @kilo6eight ! can you PM me with your actual domain? nz at os dot vu

nordurljosahvida avatar May 19 '19 09:05 nordurljosahvida

email sent

kilo6eight avatar May 19 '19 09:05 kilo6eight

@kilo6eight hi! you should have my replies in your inbox, please check ;]

nordurljosahvida avatar May 22 '19 09:05 nordurljosahvida

will get back to you tomorrow sorry for the delay

nordurljosahvida avatar Jun 01 '19 16:06 nordurljosahvida

re-running the setup a few times and i passed the SRV error

ghost avatar Aug 07 '19 14:08 ghost

What record was giving you issues? All other SRVs were ok?

On August 7, 2019 16:51:05 bonmerx [email protected] wrote:

re-running the setup a few times and i passed the SRV error — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

nordurljosahvida avatar Aug 07 '19 17:08 nordurljosahvida

I think both SRVs for 5222, 5223 ports. I cant remember well, the auto check didnt work, but rerunning setup passed it. After that it didnt build for the converse.js. I will maybe backup/restore and rerun the setup in the next days.

ghost avatar Aug 08 '19 17:08 ghost