Project

General

Profile

Actions
Copy link

Bug #4092

closed

enable DNSSEC on unbound resolver breaks ability to resolve www.google.com

Added by Vick Khera over 9 years ago. Updated over 9 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
DNS Resolver
Target version:
-
Start date:
12/10/2014
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.2
Affected Architecture:

Description

On the DNS Resolver main configuration page, if you enable DNSSEC, the resolver is no longer able to resolve www.google.com and returns SERVFAIL instead.

Actions
Copy link
 #1

Updated by Chris Buechler over 9 years ago

  • Status changed from New to Rejected

Definitely not true. Something in your case legitimately is breaking DNSSEC. Post some details to the forum or list and we can help track down what's happening there. Unbound behaves the way it should there in every circumstance I've seen. I've been running for quite some time with DNSSEC enabled using Unbound and have had 0 issues.

Actions
Copy link

Also available in: Atom PDF