Re: Update to Linux 4.10.1-1 Broke Bind9 /etc/named.conf never reached on startup

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: arch-general@xxxxxxxxxxxxx
Subject: Re: Update to Linux 4.10.1-1 Broke Bind9 /etc/named.conf never reached on startup
From: Doug Newgard <scimmia@xxxxxxxxxxxxxx>
Date: Sun, 12 Mar 2017 09:41:34 -0500
In-reply-to: <24e69e2c-ad5f-960a-89ab-2c3272c8832f@suddenlinkmail.com>
Reply-to: General Discussion about Arch Linux <arch-general@xxxxxxxxxxxxx>

On Sun, 12 Mar 2017 09:36:48 -0500
"David C. Rankin" <drankinatty@xxxxxxxxxxxxxxxxxx> wrote:

>   Should I open a bug, and if so, which package do I open it under?

There already is one, has been for a couple of days

References:
- Update to Linux 4.10.1-1 Broke Bind9 /etc/named.conf never reached on startup
  - From: David C. Rankin
- Re: Update to Linux 4.10.1-1 Broke Bind9 /etc/named.conf never reached on startup
  - From: David C. Rankin
- Re: Update to Linux 4.10.1-1 Broke Bind9 /etc/named.conf never reached on startup
  - From: David C. Rankin

Prev by Date: Re: Update to Linux 4.10.1-1 Broke Bind9 /etc/named.conf never reached on startup
Next by Date: Re: Update to Linux 4.10.1-1 Broke Bind9 /etc/named.conf never reached on startup
Previous by thread: Re: Update to Linux 4.10.1-1 Broke Bind9 /etc/named.conf never reached on startup
Next by thread: Re: Update to Linux 4.10.1-1 Broke Bind9 /etc/named.conf never reached on startup
Index(es):
- Date
- Thread

[Index of Archives] [Linux Wireless] [Linux Kernel] [ATH6KL] [Linux Bluetooth] [Linux Netdev] [Kernel Newbies] [Share Photos] [IDE] [Security] [Git] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Linux ATA RAID] [Samba] [Device Mapper]

Powered by Linux