Project

General

Profile

Actions
Copy link

Bug #4747

closed

DNS Resolver - Insufficient sanity checking for DNS Query Forwarding

Added by Kill Bill almost 9 years ago. Updated about 8 years ago.

Status:
Resolved
Priority:
Low
Assignee:
Chris Buechler
Category:
DNS Resolver
Target version:
2.3
Start date:
06/05/2015
Due date:
% Done:

0%

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

Description

When you don't specify any DNS servers, you can still tick the "DNS Query Forwarding" and save the configuration, resulting in broken DNS not resolving anything at all.

$ grep forward /var/unbound/unbound.conf
forward-zone:
        forward-addr: 127.0.0.1
Actions
Copy link
 #1

Updated by Chris Buechler almost 9 years ago

  • Status changed from New to Confirmed
  • Priority changed from Normal to Low
  • Target version changed from 2.2.3 to 2.3
  • Affected Version changed from 2.2 to All

same is true of dnsmasq. It's not as simple as just checking for user-defined DNS servers, as those with dynamic WANs often don't specify any.

Actions
Copy link
 #2

Updated by Jim Thompson over 8 years ago

  • Assignee set to Chris Buechler
Actions
Copy link
 #3

Updated by Jim Thompson about 8 years ago

  • Assignee changed from Chris Buechler to Renato Botelho
Actions
Copy link
 #4

Updated by Chris Buechler about 8 years ago

  • Status changed from Confirmed to Resolved
  • Assignee changed from Renato Botelho to Chris Buechler

fixed

Actions
Copy link

Also available in: Atom PDF