[SUSPECT EMAIL: No Reputation] Re: unbound API and authenticated data

Modster, Anthony Anthony.Modster at Teledyne.com
Mon Aug 3 17:10:08 UTC 2020


Sorry I mist that, no problem for this item.

-----Original Message-----
From: Anand Buddhdev <anandb at ripe.net> 
Sent: Monday, August 3, 2020 2:55 AM
To: Modster, Anthony <Anthony.Modster at Teledyne.com>
Cc: unbound-users at lists.nlnetlabs.nl
Subject: Re: [SUSPECT EMAIL: No Reputation] Re: unbound API and authenticated data

---External Email---

Hello Anthony,

On 22 July, George very clearly wrote to you:

"However cloudflare.net is a DNSSEC signed domain, whereas google.com is not."

Your log file below also shows unbound resolving "www.google.com", getting an answer, and saying that it's not secure. All of this is consistent, because "google.com" is NOT a signed domain. So what's the problem?

Regards,
Anand

On 01/08/2020 01:59, Modster, Anthony via Unbound-users wrote:

> Hello George
> 
> I setup forwarding to 8.8.8.8.
> The unbound API still indicates the resolve is not secure.
> My root.key is from iana.
> 
> What should I check ?
> 
> test-unbound main start

[snip]

> libunboundclient:[31179]: ResolveURL IP address 74.125.138.104 (domain name=www.google.com).
> libunboundclient:[31179]: ResolveURL result is insecure (IP address 74.125.138.104, domain name=www.google.com).
> main resolve www.google.com 74.125.138.104 (cnt 1).
> UnboundStop stopping unbound (unbound pid 31193).
> test-unbound main end


More information about the Unbound-users mailing list