Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Jim Gettys <jg@freedesktop.org>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Wondering what dns lookups should be returning on local files...
Date: Mon, 24 Mar 2014 17:12:27 +0100	[thread overview]
Message-ID: <87r45r7ez8.fsf@toke.dk> (raw)
In-Reply-To: <CAGhGL2CVr7XCBCanw0Y6fuVf7F33Pj4RwiObQeAtZHRM5=8kBQ@mail.gmail.com> (Jim Gettys's message of "Mon, 24 Mar 2014 10:56:31 -0400")

[-- Attachment #1: Type: text/plain, Size: 893 bytes --]

Jim Gettys <jg@freedesktop.org> writes:

> It looks like it tried to validate "home" (though this may be an artifact of
> chome), and returned:
>
>        *     home              
>              Secured by DNSSEC 
>
>     *
>     Nonexistence of the domain name home
>
>     was validated by DNSSEC.
>
>     The parent domain is secured by DNSSEC, thus it was possible to successfully
>     verify nonexistence of this domain name.
>
> So this may be perfectly fine and expected; could be a google chome ism, or is
> just an artifact of the validator plug-in.

My guess would be that it validates (from the root servers) that there's
no TLD called 'home'. You could try creating a folder /com and opening
a file from there, and see if it tells you that 'com' exists.

I think I would consider it a bug in the validator that it doesn't
exclude file:// URLs :)

-Toke

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 489 bytes --]

  reply	other threads:[~2014-03-24 16:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-24 14:56 Jim Gettys
2014-03-24 16:12 ` Toke Høiland-Jørgensen [this message]
2014-03-24 16:28 ` Valdis.Kletnieks

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

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r45r7ez8.fsf@toke.dk \
    --to=toke@toke.dk \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=jg@freedesktop.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