Bug 55971 - Missing full support of RFC6764 due to collision of TXT records with SRV records (LDAP DN)
Missing full support of RFC6764 due to collision of TXT records with SRV reco...
Status: NEW
Product: UCS
Classification: Unclassified
Component: DNS
UCS 5.2
All All
: P5 enhancement (vote)
: ---
Assigned To: UCS maintainers
UCS maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2023-04-14 21:30 CEST by Mike Williams
Modified: 2023-04-14 21:30 CEST (History)
0 users

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mike Williams 2023-04-14 21:30:30 CEST
As per RFC 6764[https://www.rfc-editor.org/rfc/rfc6764], Section 4, it should be possible to define a "context path" for locating the correct DAV entrypoint, namely for the services _caldav, _caldavs, _carddav and _carddavs.

While it is possible to define the respective SRV records, creating the TXT records fail to be created due to a conflict of the beforehand already existing DN by the SRV record.

DNS Records ought to be possible for multiple types with identical records, as can be seen as below:

# dig +short -t TXT _caldav._tcp.grommunio.com @1.1.1.2
"path=/dav"
# dig +short -t SRV _caldav._tcp.grommunio.com @1.1.1.2
0 0 443 srv-mail-01.grommunio.com.

We do have the workaround of the RFC 6764 (which we support), however to fully be compliant the records would be required to be set as well.

Are there any hints we have missed to create TXT records alongside existing SRV records?