pfSense Gold Subscription

Author Topic: DNS Resolver  (Read 67691 times)

0 Members and 1 Guest are viewing this topic.

Offline dstroot

  • Jr. Member
  • **
  • Posts: 80
  • Karma: +3/-0
    • View Profile
Re: DNS Resolver
« Reply #60 on: November 18, 2014, 09:57:56 pm »
So it caches either way?

So what is the use case for the forwarder option?  To force something like OpenDNS?  Because it sounds as if the non-forwarder behavior is the most accurate option, no?  (maybe slower?).

Offline phil.davis

  • Hero Member
  • *****
  • Posts: 4612
  • Karma: +550/-3
    • View Profile
    • International Nepal Fellowship
Re: DNS Resolver
« Reply #61 on: November 18, 2014, 10:05:24 pm »
For example, I subscribe to the DynDNS "Internet Guide" service (it is cheap for 10 public IPs). So it can filter name responses for categories of sites (porn, violent...). That does a good job of keeping staff away from that sort of content.
So I want the pfSense DNS to just forward to DynDNS servers, because I really do want a changed (filtered) view of what the real root servers have.
As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

Offline phil.davis

  • Hero Member
  • *****
  • Posts: 4612
  • Karma: +550/-3
    • View Profile
    • International Nepal Fellowship
Re: DNS Resolver
« Reply #62 on: November 19, 2014, 03:48:41 am »
DNS Forwarder Host Overrides - the aliases (if any) of the main host override display on the main screen, in addition to the main override entry itself.
DNS Resolver Host Overrides - the aliases (if any) of the main host override do not display on the main screen. Only the main override entry itself is displayed.
It is not effecting what is stored in the actual config. When you edit a DNS Resolver Host Override the aliases are there.

Does anybody care?
Leave it as it is?
As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

Offline cmb

  • Hero Member
  • *****
  • Posts: 11230
  • Karma: +893/-7
    • View Profile
    • Chris Buechler
Re: DNS Resolver
« Reply #63 on: November 19, 2014, 11:13:37 am »
It'd be nice to have that back if you'd like to put in a pull request Phil. If not, it's not a big deal.

Online mais_um

  • Full Member
  • ***
  • Posts: 238
  • Karma: +4/-0
    • View Profile
Re: DNS Resolver
« Reply #64 on: November 19, 2014, 11:45:29 am »
Hi

Is asking to match if the aliases appears like expanded p2 in IPsec, more or less?

Thanks

Edit: Can't start Resolver with DHCP Registration (Register DHCP leases in the DNS Resolver) checked.

Resolver log:
Code: [Select]
Nov 19 18:13:32 unbound: [86446:0] notice: Restart of unbound 1.4.22.
Nov 19 18:13:32 unbound: [86446:0] fatal error: Could not read config file: /unbound.conf
Nov 19 18:14:04 unbound: [40605:0] notice: init module 0: iterator
Nov 19 18:14:04 unbound: [40605:0] info: start of service (unbound 1.4.22).
Nov 19 18:14:04 unbound: [40605:0] info: service stopped (unbound 1.4.22).
Nov 19 18:14:04 unbound: [40605:0] info: server stats for thread 0: 0 queries, 0 answers from cache, 0 recursions, 0 prefetch
Nov 19 18:14:04 unbound: [40605:0] info: server stats for thread 0: requestlist max 0 avg 0 exceeded 0 jostled 0
Nov 19 18:14:04 unbound: [40605:0] info: server stats for thread 1: 0 queries, 0 answers from cache, 0 recursions, 0 prefetch
Nov 19 18:14:04 unbound: [40605:0] info: server stats for thread 1: requestlist max 0 avg 0 exceeded 0 jostled 0

System -> General  log:
Code: [Select]
dhcpleases: Could not deliver signal HUP to process because its pidfile (/var/run/unbound.pid) does not exist, No such process.
« Last Edit: November 19, 2014, 12:27:14 pm by mais_um »
pfSense:
ASRock -> Wolfdale1333-D667 (2GB TeamElite Ram)
Marvell 88SA8040 Sata to CF(Sandisk 4GB) Controller
NIC's: RTL8100E (Internal ) and Intel® PRO/1000 PT Dual (Intel 82571GB)

Offline phil.davis

  • Hero Member
  • *****
  • Posts: 4612
  • Karma: +550/-3
    • View Profile
    • International Nepal Fellowship
Re: DNS Resolver
« Reply #65 on: November 19, 2014, 11:23:08 pm »
It'd be nice to have that back if you'd like to put in a pull request Phil. If not, it's not a big deal.
Yes, I will have a look. It should be just a copy-paste-search-replace operation to put the same functionality into the Resolver host override aliases case.
and yes, it was that easy, pull request: https://github.com/pfsense/pfsense/pull/1344
« Last Edit: November 20, 2014, 12:04:24 am by phil.davis »
As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

Offline stewgoin

  • Newbie
  • *
  • Posts: 4
  • Karma: +0/-0
    • View Profile
Re: DNS Resolver
« Reply #66 on: November 20, 2014, 05:55:48 am »
Edit: Can't start Resolver with DHCP Registration (Register DHCP leases in the DNS Resolver) checked.

I'm seeing the same behavior this morning after updating to the latest snapshot. I turned off the DHCP registration stuff in DNS Resolver and it starts up just fine.

Online mais_um

  • Full Member
  • ***
  • Posts: 238
  • Karma: +4/-0
    • View Profile
Re: DNS Resolver
« Reply #67 on: November 20, 2014, 06:33:40 am »
Hi

Thu Nov 20 00:23:34 CST 2014 build i can enable DHCP Registration.
pfSense:
ASRock -> Wolfdale1333-D667 (2GB TeamElite Ram)
Marvell 88SA8040 Sata to CF(Sandisk 4GB) Controller
NIC's: RTL8100E (Internal ) and Intel® PRO/1000 PT Dual (Intel 82571GB)

Offline hiwi

  • Newbie
  • *
  • Posts: 9
  • Karma: +0/-0
    • View Profile
Re: DNS Resolver
« Reply #68 on: November 21, 2014, 04:40:34 am »
Today with build Fri Nov 21 01:58:53 CST 2014 I'm getting again 'fatal error: Could not read config file: /unbound.conf' with DHCP Registration checked.

Offline cmb

  • Hero Member
  • *****
  • Posts: 11230
  • Karma: +893/-7
    • View Profile
    • Chris Buechler
Re: DNS Resolver
« Reply #69 on: November 21, 2014, 01:08:30 pm »
Today with build Fri Nov 21 01:58:53 CST 2014 I'm getting again 'fatal error: Could not read config file: /unbound.conf' with DHCP Registration checked.

Can't seem to replicate that. How is your Unbound configured?

Offline hiwi

  • Newbie
  • *
  • Posts: 9
  • Karma: +0/-0
    • View Profile
Re: DNS Resolver
« Reply #70 on: November 21, 2014, 01:56:13 pm »
Today with build Fri Nov 21 01:58:53 CST 2014 I'm getting again 'fatal error: Could not read config file: /unbound.conf' with DHCP Registration checked.

Can't seem to replicate that. How is your Unbound configured?

What information do you need?

Offline Hugovsky

  • Full Member
  • ***
  • Posts: 264
  • Karma: +6/-0
    • View Profile
Re: DNS Resolver
« Reply #71 on: November 21, 2014, 01:57:07 pm »
To me, it gives the error attached if I try to start resolver with "Register DHCP leases in the DNS Resolver" set.

2.2-BETA (amd64)
built on Fri Nov 21 08:16:06 CST 2014
FreeBSD 10.1-RELEASE

Offline hiwi

  • Newbie
  • *
  • Posts: 9
  • Karma: +0/-0
    • View Profile
Re: DNS Resolver
« Reply #72 on: November 21, 2014, 03:10:44 pm »
Today with build Fri Nov 21 01:58:53 CST 2014 I'm getting again 'fatal error: Could not read config file: /unbound.conf' with DHCP Registration checked.

Can't seem to replicate that. How is your Unbound configured?

With version '2.2-BETA (amd64) built on Fri Nov 21 08:16:06 CST 2014' unbound started directly after upgrade. After another reboot it didn't start with DHCP Registration ('Register DHCP leases in the DNS Resolver') on.

Offline cmb

  • Hero Member
  • *****
  • Posts: 11230
  • Karma: +893/-7
    • View Profile
    • Chris Buechler
Re: DNS Resolver
« Reply #73 on: November 21, 2014, 03:42:54 pm »
What's in your resolver log? Re: config, how are all the settings under Services>DNS Resolver configured?

Offline hiwi

  • Newbie
  • *
  • Posts: 9
  • Karma: +0/-0
    • View Profile
Re: DNS Resolver
« Reply #74 on: November 21, 2014, 04:18:55 pm »
resolver.log

Code: [Select]
Nov 21 23:04:26 unbound: [6842:0] fatal error: Could not read config file: /unbound.conf
Nov 21 23:04:26 unbound: [6842:0] info: ignored infra-lame-ttl: 900 (option removed, use infra-host-ttl)
Nov 21 23:04:26 unbound: [6842:0] notice: Restart of unbound 1.4.22.
Nov 21 23:04:26 unbound: [6842:0] debug: cache memory msg=66072 rrset=66072 infra=2600 val=66280
Nov 21 23:04:26 unbound: [6842:0] info: mesh has 0 recursion states (0 with reply, 0 detached), 0 waiting replies, 0 recursion replies sent, 0 replies dropped, 0 states jostled out
Nov 21 23:04:26 unbound: [6842:0] info: server stats for thread 1: requestlist max 0 avg 0 exceeded 0 jostled 0
Nov 21 23:04:26 unbound: [6842:0] info: server stats for thread 1: 0 queries, 0 answers from cache, 0 recursions, 0 prefetch
Nov 21 23:04:26 unbound: [6842:0] debug: cache memory msg=66072 rrset=66072 infra=2600 val=66280
Nov 21 23:04:26 unbound: [6842:0] info: mesh has 0 recursion states (0 with reply, 0 detached), 0 waiting replies, 0 recursion replies sent, 0 replies dropped, 0 states jostled out
Nov 21 23:04:26 unbound: [6842:0] info: server stats for thread 0: requestlist max 0 avg 0 exceeded 0 jostled 0
Nov 21 23:04:26 unbound: [6842:0] info: server stats for thread 0: 0 queries, 0 answers from cache, 0 recursions, 0 prefetch
Nov 21 23:04:26 unbound: [6842:0] info: service stopped (unbound 1.4.22).
Nov 21 23:04:26 unbound: [6842:0] debug: caught signal SIGHUP
Nov 21 23:04:26 unbound: [6842:1] debug: cache memory msg=66072 rrset=66072 infra=2600 val=66280
Nov 21 23:04:26 unbound: [6842:0] info: start of service (unbound 1.4.22).
Nov 21 23:04:26 unbound: [6842:0] debug: cache memory msg=66072 rrset=66072 infra=2600 val=66280
Nov 21 23:04:26 unbound: [6842:0] debug: target fetch policy for level 4 is 0
Nov 21 23:04:26 unbound: [6842:0] debug: target fetch policy for level 3 is 0
Nov 21 23:04:26 unbound: [6842:0] debug: target fetch policy for level 2 is 1
Nov 21 23:04:26 unbound: [6842:0] debug: target fetch policy for level 1 is 2
Nov 21 23:04:26 unbound: [6842:0] debug: target fetch policy for level 0 is 3
Nov 21 23:04:26 unbound: [6842:0] notice: init module 1: iterator
Nov 21 23:04:26 unbound: [6842:0] notice: init module 0: validator
Nov 21 23:04:26 unbound: [6842:0] debug: module config: "validator iterator"
Nov 21 23:04:26 unbound: [6842:0] debug: duplicate acl address ignored.
Nov 21 23:04:26 unbound: [6842:0] debug: drop user privileges, run as unbound
Nov 21 23:04:26 unbound: [6842:0] debug: chroot to /var/unbound
Nov 21 23:04:26 unbound: [6842:0] debug: chdir to /var/unbound
Nov 21 23:04:25 unbound: [87880:0] debug: switching log to stderr
Nov 21 23:04:25 unbound: [87880:0] debug: cache memory msg=66072 rrset=66072 infra=288782 val=149925
Nov 21 23:04:25 unbound: [87880:0] info: 1.000000 2.000000 7
Nov 21 23:04:25 unbound: [87880:0] info: 0.524288 1.000000 21
Nov 21 23:04:25 unbound: [87880:0] info: 0.262144 0.524288 62
Nov 21 23:04:25 unbound: [87880:0] info: 0.131072 0.262144 100
Nov 21 23:04:25 unbound: [87880:0] info: 0.065536 0.131072 50
Nov 21 23:04:25 unbound: [87880:0] info: 0.032768 0.065536 83
Nov 21 23:04:25 unbound: [87880:0] info: 0.016384 0.032768 176
Nov 21 23:04:25 unbound: [87880:0] info: 0.008192 0.016384 27
Nov 21 23:04:25 unbound: [87880:0] info: 0.004096 0.008192 1
Nov 21 23:04:25 unbound: [87880:0] info: 0.000000 0.000001 37
Nov 21 23:04:25 unbound: [87880:0] info: lower(secs) upper(secs) recursions
Nov 21 23:04:25 unbound: [87880:0] info: [25%]=0.0234589 median[50%]=0.0489546 [75%]=0.195297
Nov 21 23:04:25 unbound: [87880:0] info: histogram of recursion processing times
Nov 21 23:04:25 unbound: [87880:0] info: average recursion processing time 0.139959 sec
Nov 21 23:04:25 unbound: [87880:0] info: mesh has 0 recursion states (0 with reply, 0 detached), 0 waiting replies, 564 recursion replies sent, 0 replies dropped, 0 states jostled out
Nov 21 23:04:25 unbound: [87880:0] info: server stats for thread 1: requestlist max 14 avg 0.603774 exceeded 0 jostled 0
Nov 21 23:04:25 unbound: [87880:0] info: server stats for thread 1: 1688 queries, 1124 answers from cache, 564 recursions, 178 prefetch
Nov 21 23:04:25 unbound: [87880:0] debug: cache memory msg=66072 rrset=66072 infra=288782 val=149925
Nov 21 23:04:25 unbound: [87880:0] info: 1.000000 2.000000 1
Nov 21 23:04:25 unbound: [87880:0] info: 0.524288 1.000000 14
Nov 21 23:04:25 unbound: [87880:0] info: 0.262144 0.524288 30
Nov 21 23:04:25 unbound: [87880:0] info: 0.131072 0.262144 42
Nov 21 23:04:25 unbound: [87880:0] info: 0.065536 0.131072 28
Nov 21 23:04:25 unbound: [87880:0] info: 0.032768 0.065536 39
Nov 21 23:04:25 unbound: [87880:0] info: 0.016384 0.032768 52
Nov 21 23:04:25 unbound: [87880:0] info: 0.008192 0.016384 13
Nov 21 23:04:25 unbound: [87880:0] info: 0.004096 0.008192 1
Nov 21 23:04:25 unbound: [87880:0] info: 0.000000 0.000001 18
Nov 21 23:04:25 unbound: [87880:0] info: lower(secs) upper(secs) recursions
Nov 21 23:04:25 unbound: [87880:0] info: [25%]=0.0250486 median[50%]=0.0621752 [75%]=0.216893
Nov 21 23:04:25 unbound: [87880:0] info: histogram of recursion processing times
Nov 21 23:04:25 unbound: [87880:0] info: average recursion processing time 0.147787 sec
Nov 21 23:04:25 unbound: [87880:0] info: mesh has 0 recursion states (0 with reply, 0 detached), 0 waiting replies, 238 recursion replies sent, 0 replies dropped, 0 states jostled out
Nov 21 23:04:25 unbound: [87880:0] info: server stats for thread 0: requestlist max 40 avg 3.168 exceeded 0 jostled 0
Nov 21 23:04:25 unbound: [87880:0] info: server stats for thread 0: 548 queries, 310 answers from cache, 238 recursions, 12 prefetch
Nov 21 23:04:25 unbound: [87880:0] info: service stopped (unbound 1.4.22).
Nov 21 23:04:25 unbound: [87880:0] debug: caught signal SIGTERM
Nov 21 23:04:23 unbound: [87880:1] debug: cache memory msg=418824 rrset=714129 infra=288782 val=149925
Nov 21 23:04:23 unbound: [87880:1] info: validator operate: query cl4appf.com. A IN
Nov 21 23:04:23 unbound: [87880:1] debug: validator[module 0] operate: extstate:module_wait_module event:module_event_moddone
Nov 21 23:04:23 unbound: [87880:1] info: finishing processing for cl4appf.com. A IN
Nov 21 23:04:23 unbound: [87880:1] info: query response was ANSWER
Nov 21 23:04:23 unbound: [87880:1] info: reply from <cl4appf.com.> 78.140.168.56#53
Nov 21 23:04:23 unbound: [87880:1] info: response for cl4appf.com. A IN
Nov 21 23:04:23 unbound: [87880:1] info: sanitize: storing potential poison RRset: ns2.dcrmt.net. A IN
Nov 21 23:04:23 unbound: [87880:1] info: sanitize: storing potential poison RRset: ns1.dcrmt.net. A IN
Nov 21 23:04:23 unbound: [87880:1] info: iterator operate: query cl4appf.com. A IN
Nov 21 23:04:23 unbound: [87880:1] debug: iterator[module 1] operate: extstate:module_wait_reply event:module_event_reply
Nov 21 23:04:23 unbound: [87880:1] debug: cache memory msg=418824 rrset=714129 infra=288782 val=149925
Nov 21 23:04:23 unbound: [87880:1] info: Verified that unsigned response is INSECURE
Nov 21 23:04:23 unbound: [87880:1] info: validator operate: query cl4appf.com. AAAA IN
Nov 21 23:04:23 unbound: [87880:1] debug: validator[module 0] operate: extstate:module_wait_subquery event:module_event_pass
Nov 21 23:04:23 unbound: [87880:1] info: NSEC3s for the referral proved no DS.
Nov 21 23:04:23 unbound: [87880:1] info: validator operate: query cl4appf.com. DS IN
Nov 21 23:04:23 unbound: [87880:1] debug: validator[module 0] operate: extstate:module_wait_module event:module_event_moddone
Nov 21 23:04:23 unbound: [87880:1] info: finishing processing for cl4appf.com. DS IN
Nov 21 23:04:23 unbound: [87880:1] info: query response was nodata ANSWER
Nov 21 23:04:23 unbound: [87880:1] info: reply from <com.> 2001:503:a83e::2:30#53
Nov 21 23:04:23 unbound: [87880:1] info: response for cl4appf.com. DS IN
Nov 21 23:04:23 unbound: [87880:1] info: iterator operate: query cl4appf.com. DS IN
Nov 21 23:04:23 unbound: [87880:1] debug: iterator[module 1] operate: extstate:module_wait_reply event:module_event_reply
Nov 21 23:04:23 unbound: [87880:1] debug: cache memory msg=418824 rrset=714129 infra=288782 val=149925
Nov 21 23:04:23 unbound: [87880:1] debug: sending to target: <com.> 2001:503:a83e::2:30#53
Nov 21 23:04:23 unbound: [87880:1] info: sending query: cl4appf.com. DS IN
Nov 21 23:04:23 unbound: [87880:1] info: processQueryTargets: cl4appf.com. DS IN
Nov 21 23:04:23 unbound: [87880:1] info: resolving (init part 3): cl4appf.com. DS IN
Nov 21 23:04:23 unbound: [87880:1] info: resolving (init part 2): cl4appf.com. DS IN
Nov 21 23:04:23 unbound: [87880:1] info: resolving cl4appf.com. DS IN
Nov 21 23:04:23 unbound: [87880:1] debug: iterator[module 1] operate: extstate:module_state_initial event:module_event_pass
Nov 21 23:04:23 unbound: [87880:1] info: validator operate: query cl4appf.com. DS IN

system.log

Code: [Select]
Nov 21 23:04:26 zh01-rt02 dhcpleases: Could not deliver signal HUP to process because its pidfile (/var/run/unbound.pid) does not exist, No such process.
Nov 21 23:04:27 zh01-rt02 dhcpleases: Could not deliver signal HUP to process because its pidfile (/var/run/unbound.pid) does not exist, No such process.
Nov 21 23:04:29 zh01-rt02 dhcpleases: Could not deliver signal HUP to process because its pidfile (/var/run/unbound.pid) does not exist, No such process.
Nov 21 23:04:29 zh01-rt02 dhcpleases: kqueue error: unkown
Nov 21 23:04:29 zh01-rt02 dhcpleases: Could not deliver signal HUP to process because its pidfile (/var/run/unbound.pid) does not exist, No such process.

Image with options is attached.