Skip to content

DOCSP-47044: Polling DNS SRV records #93

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.

Sign up for GitHub

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

Merged
merged 3 commits into from
Mar 4, 2025
Merged

DOCSP-47044: Polling DNS SRV records #93

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
7bf7613
DOCSP-47044: Polling DNS SRV records
norareidy Mar 3, 2025
1071056
remove header
norareidy Mar 3, 2025
80171db
MW feedback
norareidy Mar 3, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions dbx/srv-polling.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
To use DNS service discovery to look up the DNS SRV record of the service you're connecting to,
specify the SRV connection format in your connection string. Additionally, if you enable
the SRV connection format, the {+driver-short+} automatically re-scans for new hosts without
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no hyphen here AFAICT

Suggested change
the SRV connection format, the {+driver-short+} automatically re-scans for new hosts without
the SRV connection format, the {+driver-short+} automatically rescans for new hosts without

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s:

Suggested change
specify the SRV connection format in your connection string. Additionally, if you enable
the SRV connection format, the {+driver-short+} automatically re-scans for new hosts without
specify the SRV connection format in your connection string. If you specify
this format, the {+driver-short+} automatically re-scans for new hosts without

having to change the client configuration.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this syntax is a little odd. it makes it sound like the driver (subject of the sentence) is the thing that has to or doesn't have to change the config, even though it's the user who does that. what if we just ditch the last part?

Suggested change
the SRV connection format, the {+driver-short+} automatically re-scans for new hosts without
having to change the client configuration.
the SRV connection format, the {+driver-short+} automatically re-scans for new hosts.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I added an extra sentence that's hopefully more clear, let me know what you think


The following code shows a connection string that uses the SRV connection format:

|srv-uri|

To learn more about the SRV connection format, see the :manual:`SRV Connection Format </reference/connection-string/#std-label-connections-dns-seedlist>`
entry in the {+mdb-server+} manual.