From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Testing core141
Date: Fri, 07 Feb 2020 21:26:13 +0000 [thread overview]
Message-ID: <DFF9CDCB-17B8-4F73-AC2E-B92A837F7683@ipfire.org> (raw)
In-Reply-To: <000801d5ddfc$af86ecd0$0e94c670$@net>
[-- Attachment #1: Type: text/plain, Size: 370 bytes --]
Broken in what way?
> On 7 Feb 2020, at 21:22, Mentalic <mentalic(a)cox.net> wrote:
>
> Loaded core141/831ff0fd from iso . Had DNS over TLS working until I loaded backup from my core139 system. Tried it twice same results where after backup restore DNS is broken no matter how I try the various configuration options on DNS page.
>
>
> Regards
> Wayne
next parent reply other threads:[~2020-02-07 21:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000801d5ddfc$af86ecd0$0e94c670$@net>
2020-02-07 21:26 ` Michael Tremer [this message]
2020-02-07 22:14 ` Mentalic
2020-02-08 11:19 ` Michael Tremer
2020-02-08 20:47 ` Mentalic
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=DFF9CDCB-17B8-4F73-AC2E-B92A837F7683@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