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.

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

Jump to bottom

SSSD man: man_dns_resolver_parameter_modification #5645

Closed
wants to merge 3 commits into from
Closed

SSSD man: man_dns_resolver_parameter_modification #5645

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
9ab6cc0
SSSD man: man_dns_resolver_parameter_modification
DDDas7 May 20, 2021
2f3c2b0
SSSD man: man_dns_resolver_parameter_modification
DDDas7 May 20, 2021
5c422e6
SSSD man: man_dns_resolver_parameter_modification
DDDas7 May 22, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
39 changes: 39 additions & 0 deletions src/man/sssd.conf.5.xml
View file
Open in desktop
Expand Up @@ -3406,6 +3406,45 @@ pam_gssapi_indicators_map = sudo:pkinit, sudo-i:pkinit
</listitem>
</varlistentry>

<varlistentry>
<term>dns_resolver_server_timeout (integer)</term>
<listitem>
<para>
Defines the amount of time (in milliseconds)
SSSD would try to talk to DNS server before
trying next DNS server.
Copy link
Contributor

Choose a reason for hiding this comment

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

Hi, I read this a couple times but it's not really clear to me what it means.

I interpret this as SSSD would try to talk to a DNS server for 1 second before trying a next DNS server, but why would SSSD only communicate with a DNS server for 1 second? Does it mean SSSD connects to a DNS server but only waits for a response for 1 second?

Copy link
Contributor

Choose a reason for hiding this comment

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

I think that the timer is only used to resolve the DNS server, once it's resolved the timer no longer applies.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I have rephrased the complete sentence. Can you pls check the latest changes.

Also I have split the dns_resolver_* parameters from “failover.xml” and created a new file “dns_options.xml” to sync the parameter definition since currently the definition for the parameter “dns_resolver_timeout” is different in files “failover.xml” and “sssd.conf.5.xml”.

It will help maintaining the dns_resolver_* parameters definition from a single file.

</para>
<para>
Please see the section <quote>FAILOVER</quote>
for more information about the service
resolution.
</para>
<para>
Default: 1000
</para>
</listitem>
</varlistentry>

<varlistentry>
<term>dns_resolver_op_timeout (integer)</term>
<listitem>
<para>
Defines the amount of time (in seconds) to
wait to resolve single DNS query
DDDas7 marked this conversation as resolved.
Show resolved Hide resolved
DDDas7 marked this conversation as resolved.
Show resolved Hide resolved
(e.g. resolution of a hostname or an SRV record)
before try next hostname or DNS discovery.
DDDas7 marked this conversation as resolved.
Show resolved Hide resolved
</para>
<para>
Please see the section <quote>FAILOVER</quote>
for more information about the service
resolution.
</para>
<para>
Default: 3
</para>
</listitem>
</varlistentry>

<varlistentry>
<term>dns_resolver_timeout (integer)</term>
<listitem>
Expand Down