On 2018-09-19T11:22:16, frede...@ofb.net wrote:
> > > Well, prior to the recent BIND releease, the default had been "yes" -
> > > which means "no" for me.
> > ...
> > 2. I'm not sure what you mean by the yes-means-no syntax. The URL that you
> > provided seems pretty cut and dry.
> > ...
> > >
> > Well, prior to the recent BIND releease, the default had been "yes" -
> > which means "no" for me.
> ...
> 2. I'm not sure what you mean by the yes-means-no syntax. The URL that you
> provided seems pretty cut and dry.
> ...
> > dnssec-validation yes; #does validate (requires a
On 2018-09-13T12:31:28, frede...@ofb.net wrote:
> On Thu, Sep 13, 2018 at 06:49:45AM -0700, Pallissard, Matthew wrote:
> > > I had to add "dnssec-validation yes;" to /etc/named.conf. I have a
> >
> > Are you sure you didn't want these values?
> >
> > dnssec-enable no;
> > dnssec-validation no;
>
On Thu, Sep 13, 2018 at 06:49:45AM -0700, Pallissard, Matthew wrote:
> > I had to add "dnssec-validation yes;" to /etc/named.conf. I have a
>
> Are you sure you didn't want these values?
>
> dnssec-enable no;
> dnssec-validation no;
Well, prior to the recent BIND releease, the default had been
> I had to add "dnssec-validation yes;" to /etc/named.conf. I have a
Are you sure you didn't want these values?
dnssec-enable no;
dnssec-validation no;
Matt Pallissard
signature.asc
Description: PGP signature
Hello Arch General,
I hope this is the right mailing list; I'm a new subscriber.
After a recent upgrade I found that DNS broke in two different ways on
my computer,
1. BIND enabled DNSSEC by default, causing hostname resolution to stop
working (for some reason my home wireless router broke the
6 matches
Mail list logo
