From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [RFC] unbound: Increase timeout value for unknown dns-server
Date: Thu, 07 Jan 2021 14:54:41 +0000 [thread overview]
Message-ID: <A207910E-CB65-4552-8C51-F8E10190B4B1@ipfire.org> (raw)
In-Reply-To: <20210107143517.GA562315@vesikko.tarvainen.info>
[-- Attachment #1: Type: text/plain, Size: 1319 bytes --]
Hello,
Yes that would be the easiest way to test this.
But in general I do not recommend to have local changes like this permanently because they might break things.
-Michael
> On 7 Jan 2021, at 14:35, Tapani Tarvainen <ipfire(a)tapanitarvainen.fi> wrote:
>
> Inasmuch as the need for this is likely to be rare and potentially at
> least slightly harmful to normal users, perhaps it would be sufficient
> to suggest in the documentation that people who need it simply add
> their preferred unknown-server-time-limit setting to a file in
> /etc/unbound/local.d?
>
> It would be an easy way to test it, too.
>
> Tapani
>
> On Thu, Jan 07, 2021 at 11:27:43AM +0000, Michael Tremer (michael.tremer(a)ipfire.org) wrote:
>>
>> Hello Jon,
>>
>> Yes, that could be true.
>>
>> Can someone reach out to that user and see if they can apply the change and confirm that this works?
>>
>> -Michael
>>
>>> On 6 Jan 2021, at 18:59, Jon Murphy <jcmurphy26(a)gmail.com> wrote:
>>>
>>>
>>>
>>>> On Jan 6, 2021, at 12:01 PM, Michael Tremer <michael.tremer(a)ipfire.org> wrote:
>>>>
>>>> Did anyone actually experience some problems here that this needs changing?
>>>
>>>
>>> Maybe here?
>>>
>>> https://community.ipfire.org/t/override-disable-dnssec-system/2717
>>>
>>>
next prev parent reply other threads:[~2021-01-07 14:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5BE69EAB-BD90-4999-97AE-8A89479AD080@gmail.com>
2021-01-07 11:27 ` Michael Tremer
2021-01-07 14:35 ` Tapani Tarvainen
2021-01-07 14:54 ` Michael Tremer [this message]
[not found] <20E5B302-A896-4BD2-BAD1-9D6A50831514@ipfire.org>
2021-01-09 15:04 ` Michael Tremer
2021-01-09 18:57 ` Paul Simmons
2021-01-10 14:07 ` Tapani Tarvainen
2021-01-12 5:07 ` Paul Simmons
2021-01-16 3:02 ` Paul Simmons
2021-01-16 8:13 ` Tapani Tarvainen
2021-01-19 6:22 ` Paul Simmons
2021-01-25 19:23 ` Michael Tremer
2021-01-25 20:29 ` Paul Simmons
2021-01-25 20:50 ` Michael Tremer
2021-01-11 11:10 ` Michael Tremer
2021-01-12 4:37 ` Paul Simmons
2021-01-06 10:17 Jonatan Schlag
2021-01-06 12:02 ` Paul Simmons
2021-01-06 15:14 ` Michael Tremer
2021-01-06 16:19 ` Tapani Tarvainen
2021-01-06 18:01 ` Michael Tremer
2021-01-08 8:25 ` Paul Simmons
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=A207910E-CB65-4552-8C51-F8E10190B4B1@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox