Bug 24551 - [mad idea] Provide a SRV-resolution test hostname
Summary: [mad idea] Provide a SRV-resolution test hostname
Alias: None
Product: Telepathy
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
Depends on:
Reported: 2009-10-15 05:55 UTC by Simon McVittie
Modified: 2019-12-09 11:21 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Description Simon McVittie 2009-10-15 05:55:35 UTC
As a service to the Internet in general, and Telepathy users in particular, we could try to arrange with the fd.o admins to have the following:

srvtest.telepathy.freedesktop.org (an A record)
_xmpp-client._tcp.srvtest.freedesktop.org (an SRV record)

They don't need to point to anything in particular (we could have them both resolve to or something), as long as they are resolvable.

Given that, we could have an easy diagnostic in connection managers and/or UIs for "SRV records are broken on your network, please fix it or specify the server name manually", shown when:

* a connection cannot connect, and
* srvtest.telepathy.freedesktop.org A resolves successfully, and
* _xmpp-client._tcp.srvtest.telepathy.freedesktop.org SRV does not resolve

For instance, dnsmasq >= 1.5 has a misleadingly-named option ("filterwin2k") that deliberately breaks SRV to avoid dial-on-demand, and in versions < 2.12 it's even on by default. Unfortunately, several embedded Linux distributions for routers use dnsmasq versions between 1.5 and 2.12...
Comment 1 GitLab Migration User 2019-12-09 11:21:32 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-spec/issues/150.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.