On Tue, 2018-12-04 at 00:51 +, John Horne wrote:
>
> For many years we have modified the '/etc/named.conf' file to include local
> settings. The disadvantage with this is of course that when bind is updated,
> it creates an '/etc/named.conf.rpmnew' file. We then have to determine what
> is new,
On 04/12/18 09:41, John Horne wrote:
> On Tue, 2018-12-04 at 08:19 +, J Martin Rushton via CentOS wrote:
>> The '/etc/named.conf.rpmnew' file supplied is a bare minimum to
>> "configure the ... server as a caching only nameserver (as a localhost
>> DNS resolver only)". As soon as you start add
On Tue, 2018-12-04 at 08:19 +, J Martin Rushton via CentOS wrote:
> The '/etc/named.conf.rpmnew' file supplied is a bare minimum to
> "configure the ... server as a caching only nameserver (as a localhost
> DNS resolver only)". As soon as you start adding any structure to it
> things change, n
The '/etc/named.conf.rpmnew' file supplied is a bare minimum to
"configure the ... server as a caching only nameserver (as a localhost
DNS resolver only)". As soon as you start adding any structure to it
things change, not just are added to. See
'/usr/share/doc/bind-*/sample/etc/named.conf' for e
Hello,
For many years we have modified the '/etc/named.conf' file to include local
settings. The disadvantage with this is of course that when bind is updated, it
creates an '/etc/named.conf.rpmnew' file. We then have to determine what is
new, and apply the relevant changes to our modified named.c
5 matches
Mail list logo
