[GH-ISSUE #603] Use DNS SRV records for the default server setting #455

New issue

Closed

opened 2026-05-07 00:24:20 +02:00 by BreizhHardware · 2 comments

BreizhHardware commented

2026-05-07 00:24:20 +02:00

Owner

Originally created by @piwi82 on GitHub (Feb 6, 2023).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/603

The Default server setting in the mobile application (Android/iOS) could be eased by using only the domain name (domain.tld) instead of the full URL (https://ntfy.domain.tld) through a DNS SRV record.

Syntax : _ntfy._tcp.domain.tld. ttl IN SRV priority weight port target.
Example : _ntfy._tcp.ntfy.sh. 600 IN SRV 0 0 443 ntfy.sh.

Mine would look like : _ntfy._tcp.domain.tld. 86400 IN SRV 0 0 443 ntfy.host.domain.tld.

This way, the user has just to input domain.tld in Settings > GENERAL > Default server (also in Settings > USERS > + Add user > Service URL) and let the applications resolve _ntfy._tcp.domain.tld (and build the URL).

You will probably have to check the port value to determine whether http or https should be used :

No ambiguity if a standard value is used (80 or 443),
If another value is used, try https first. Fallback to http if https failed (https://ntfy.sh:8088 > http://ntfy.sh:8088)

No hard work, just happy end users 😀 (#597 is a good one too)

Originally created by @piwi82 on GitHub (Feb 6, 2023). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/603 The _Default server_ setting in the mobile application (Android/iOS) could be eased by using only the domain name (`domain.tld`) instead of the full URL (https://ntfy.domain.tld) through a DNS SRV record. Syntax : `_ntfy._tcp.domain.tld. ttl IN SRV priority weight port target.` Example : `_ntfy._tcp.ntfy.sh. 600 IN SRV 0 0 443 ntfy.sh.` Mine would look like : `_ntfy._tcp.domain.tld. 86400 IN SRV 0 0 443 ntfy.host.domain.tld.` This way, the user has just to input `domain.tld` in _Settings_ > _GENERAL_ > _Default server_ (also in _Settings_ > _USERS_ > _+ Add user_ > _Service URL_) and let the applications resolve `_ntfy._tcp.domain.tld` (and build the URL). You will probably have to check the **port** value to determine whether `http` or `https` should be used : - No ambiguity if a standard value is used (80 or 443), - If another value is used, try `https` first. Fallback to `http` if `https` failed (https://ntfy.sh:8088 > http://ntfy.sh:8088) No hard work, just happy end users 😀 (#597 is a good one too)

BreizhHardware closed this issue

2026-05-07 00:24:20 +02:00

BreizhHardware commented

2026-05-07 00:24:21 +02:00

Author

Owner

@binwiederhier commented on GitHub (Feb 8, 2023):

While this is a fascinating idea, I do not see a lot of value in it, especially since the base-url concept is pretty much ingrained into every fiber of ntfy. If anything, this is a UX problem: We could ease the URL entry, or have the Android/iOS/web app probe the URLs automatically.

Most users do not know what a SRV record even is. Many do not have their own DNS server, or control all aspects of it.

I am taking the liberty of closing this as WONT DO. I hope you understand. Please keep other ideas coming. I love seeing ideas like this.

@binwiederhier commented on GitHub (Feb 8, 2023): While this is a fascinating idea, I do not see a lot of value in it, especially since the base-url concept is pretty much ingrained into every fiber of ntfy. If anything, this is a UX problem: We could ease the URL entry, or have the Android/iOS/web app probe the URLs automatically. Most users do not know what a SRV record even is. Many do not have their own DNS server, or control all aspects of it. I am taking the liberty of closing this as WONT DO. I hope you understand. Please keep other ideas coming. I love seeing ideas like this.

BreizhHardware commented

2026-05-07 00:24:21 +02:00

Author

Owner

@piwi82 commented on GitHub (Apr 28, 2024):

I do understand 😉
This one certainly has the lowest priority regarding other requests like links #587 and markdown #1072 on mobile.

@piwi82 commented on GitHub (Apr 28, 2024): I do understand 😉 This one certainly has the lowest priority regarding other requests like links #587 and markdown #1072 on mobile.