From mboxrd@z Thu Jan  1 00:00:00 1970
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Core 125 - small bug post upgrade
Date: Mon, 19 Nov 2018 18:05:11 +0000
Message-ID: <b4c7c5a8428b7853872c23a8bc1bf5f9b7f32a73.camel@ipfire.org>
In-Reply-To: <H000006e00470d85.1542648864.mail.at4b.net@MHS>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============4101606248108863561=="
List-Id: <development.lists.ipfire.org>

--===============4101606248108863561==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hey,

thanks for testing.

Does this look like this?

  https://bugzilla.ipfire.org/show_bug.cgi?id=3D11917

-Michael

On Mon, 2018-11-19 at 12:34 -0500, Kienker, Fred wrote:
> IPFire core 124 connecting via DHCP on RED with DNS set via the web interfa=
ce
> page =E2=80=9CAssign DNS-Server=E2=80=9D.
> Post upgrade to core 125, after a restart, home page shows unbound in local
> recursor mode.
> Going to the =E2=80=9CAssign DNS-Server=E2=80=9D page, it displays the corr=
ect DNS server IP
> numbers.
> Clicking on the Save button corrects the problem and after unbound restarts,
> the correct DNS server IP=E2=80=99s are displayed on the home page.
> =20
> It=E2=80=99s a pretty minor issue, but the fix may elude many of the less e=
xperienced.
> Best regards,
> Fred Kienker
> =20


--===============4101606248108863561==--