Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error adding certain DNS SRV records #1549

Closed
jaydenseric opened this issue Aug 24, 2018 · 3 comments
Closed

Error adding certain DNS SRV records #1549

jaydenseric opened this issue Aug 24, 2018 · 3 comments

Comments

@jaydenseric
Copy link

While attempting to setup FastMail, the following commands don't work:

now dns add enamor.app _imap._tcp SRV 0 0 0 .
now dns add enamor.app _pop3._tcp SRV 0 0 0 .
now dns add enamor.app _carddav._tcp SRV 0 0 0 .
now dns add enamor.app _caldav._tcp SRV 0 0 0 .

They result in an error like this:

screen shot 2018-08-24 at 5 16 14 pm

I remember discussing this bug with the Zeit team in Slack, a few months ago, but the chat history is gone now and I can't remember an outcome.

@jaydenseric
Copy link
Author

Here is the purpose of this type of record, from FastMail support (received back in January):

Hi Jayden,

Thank you for writing to us.

Are there any benefits to having these entries present, and if not, should they be removed from the FastMail DNS docs? If they are useful the Zeit engineers will try to add support.

With SRV RRs it is possible to indicate that a particular service is not supported at all at a particular domain by setting the target of an SRV RR to ".". If such records are present, clients MUST assume that the specified service is not available, and instead make use of the other SRV RRs for the purposes of determining the domain preference.

Example: service records for IMAP and POP3 with both TLS and non-TLS service types are present. Both IMAP and POP3 non-TLS service types are marked as not available. IMAP (with TLS) has a lower-numbered priority value 0 than POP3 (with TLS) at priority 10, indicating to the MUA that IMAP is preferred over POP3, when the MUA can support either service, and only the TLS versions of the services are available.

_imap._tcp SRV 0 0 0 .
_imaps._tcp SRV 0 1 993 imap.example.com.
_pop3._tcp SRV 0 0 0 .
_pop3s._tcp SRV 10 1 995 pop3.example.com.

Hope this clarifies your concern. Let me know if you have any questions.

@OlliV
Copy link
Contributor

OlliV commented Aug 24, 2018

It's not a bug but an unsupported feature. Our upstream provider doesn't support these records. What would happen if these records don't exist? Is there an example of a a software that can't find the TLS records if the non-encrypted records don't exist?

@leo
Copy link
Contributor

leo commented Nov 13, 2018

Closing this, now that we didn't receive a response in 3 months.

@leo leo closed this as completed Nov 13, 2018
@vercel vercel locked and limited conversation to collaborators Nov 13, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants