From: Paul Simmons <redneckmother@hughes.net>
To: development@lists.ipfire.org
Subject: Re: [PATCH] DNS: Fall back to permissive mode if recursor mode is unavailable
Date: Wed, 08 Mar 2017 10:19:41 -0600 [thread overview]
Message-ID: <1488989981.4066.7.camel@hughes.net> (raw)
In-Reply-To: <1488974994.24229.38.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1613 bytes --]
On Wed, 2017-03-08 at 12:09 +0000, Michael Tremer wrote:
> Hmm...
>
> That's interesting that only AAAA records fail. No idea why the
> system is
> resolving those any ways, but hey...
>
> So when you do
>
> dig @198.41.0.4 a.root-servers.net AAAA +dnssec
>
> does that work?
>
> What does
>
> dig @8.8.8.8 +sigchase +dnssec www.ipfire.org
>
> do?
>
> -Michael
>
> ---->% massive snippage here %<----
Sorry for the delay. I have to chase everyone off the network and
reboot with another disk (development image) to test, then have to
reboot with Core105 and DNSSEC disabled to resume email :).
Here are the results:
# dig @198.41.0.4 a.root-servers.net AAAA +dnssec
; <<>> DiG 9.11.0-P3 <<>> @198.41.0.4 a.root-servers.net AAAA +dnssec
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 65258
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: Message has 23 extra bytes at end
;; QUESTION SECTION:
;a.root-servers.net. IN AAAA
;; Query time: 1 msec
;; SERVER: 198.41.0.4#53(198.41.0.4)
;; WHEN: Wed Mar 08 09:56:11 CST 2017
;; MSG SIZE rcvd: 59
# dig @8.8.8.8 +sigchase +dnssec www.ipfire.org
;; Warning: Message parser reports malformed message packet.
;; NO ANSWERS: no more
We want to prove the non-existence of a type of rdata 1 or of the zone:
;; nothing in authority section : impossible to validate the non-existence : FAILED
;; Impossible to verify the Non-existence, the NSEC RRset can't be validated: FAILED
Thank you,
Paul
next prev parent reply other threads:[~2017-03-08 16:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1488903324.21248.2.camel@hughes.net>
2017-03-08 12:09 ` Michael Tremer
2017-03-08 16:19 ` Paul Simmons [this message]
[not found] <1490979195.2643.88.camel@ipfire.org>
2017-04-02 16:37 ` Paul Simmons
2017-04-02 18:03 ` Michael Tremer
2017-04-02 19:07 ` Paul Simmons
[not found] <1490455220.20288.4.camel@hughes.net>
2017-03-30 16:51 ` Michael Tremer
2017-03-30 18:21 ` Paul Simmons
2017-03-01 16:11 Michael Tremer
2017-03-01 16:17 ` Michael Tremer
2017-03-01 18:00 ` Paul Simmons
2017-03-03 20:54 ` Paul Simmons
2017-03-05 11:42 ` Michael Tremer
2017-03-06 18:18 ` Paul Simmons
2017-03-06 21:00 ` Michael Tremer
2017-03-06 21:47 ` Paul Simmons
2017-03-06 22:37 ` Michael Tremer
2017-03-06 23:29 ` Paul Simmons
2017-03-07 12:06 ` Michael Tremer
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=1488989981.4066.7.camel@hughes.net \
--to=redneckmother@hughes.net \
--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