• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login
Netgate Discussion Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login

Problem with DNS resolver

Scheduled Pinned Locked Moved General pfSense Questions
64 Posts 7 Posters 5.9k Views
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • U
    Unoptanio @stephenw10
    last edited by Jun 6, 2024, 4:02 PM

    @stephenw10

    disabled DHCP Registration

    Rebooted the system and the problem recurred. unbound DNS Does not resolve

    pfSensePlus24.03 2U BareMetal Asrock Industrial IMB-X1314MicroATX
    CPU: i7-13700@5.2GHz, RAM:32GB ECC, n°2 Samsung 870EVO SATA 2.5” SSD 1TB (ZFS) Raid1
    n°3 Intel i225-LM 2500/1000/100Mbps, n°1 NIC Intel i350-T4V2 10/100/1000 Mbps 4*GLAN, n°1 Intel X520-DA2

    1 Reply Last reply Reply Quote 0
    • S
      stephenw10 Netgate Administrator
      last edited by Jun 6, 2024, 4:03 PM

      And it's still just continually restarting?

      Is there anything in the main system log that's looping? Something else could be restarting Unbound.

      U 1 Reply Last reply Jun 6, 2024, 4:04 PM Reply Quote 0
      • U
        Unoptanio @stephenw10
        last edited by Unoptanio Jun 6, 2024, 4:08 PM Jun 6, 2024, 4:04 PM

        @stephenw10
        924aee13-1129-4e65-9f38-85d5bfc5097e-image.png

        I stopped the service and restarted it and it worked right away.

        But in the service list it always showed it running green even when it's not working
        91c7f419-6668-4f6b-a69d-b932b45d6d27-image.png

        pfSensePlus24.03 2U BareMetal Asrock Industrial IMB-X1314MicroATX
        CPU: i7-13700@5.2GHz, RAM:32GB ECC, n°2 Samsung 870EVO SATA 2.5” SSD 1TB (ZFS) Raid1
        n°3 Intel i225-LM 2500/1000/100Mbps, n°1 NIC Intel i350-T4V2 10/100/1000 Mbps 4*GLAN, n°1 Intel X520-DA2

        J 1 Reply Last reply Jun 6, 2024, 5:07 PM Reply Quote 0
        • S
          stephenw10 Netgate Administrator
          last edited by Jun 6, 2024, 4:13 PM

          And in the main system log?

          1 Reply Last reply Reply Quote 0
          • J
            johnpoz LAYER 8 Global Moderator @Unoptanio
            last edited by Jun 6, 2024, 5:07 PM

            @Unoptanio why/how can you have both unbound 1.18 and 1.19.1 on the same system both starting?

            Did you upgrade pfsense? That is a pretty fast upgrade

            both.jpg

            LIke 1 minute?

            An intelligent man is sometimes forced to be drunk to spend time with his fools
            If you get confused: Listen to the Music Play
            Please don't Chat/PM me for help, unless mod related
            SG-4860 24.11 | Lab VMs 2.8, 24.11

            U 1 Reply Last reply Jun 7, 2024, 7:13 AM Reply Quote 1
            • S
              stephenw10 Netgate Administrator
              last edited by Jun 6, 2024, 5:39 PM

              Huh, nice catch! Well that seems suspicious!

              U 1 Reply Last reply Jun 7, 2024, 6:47 AM Reply Quote 0
              • U
                Unoptanio @stephenw10
                last edited by Unoptanio Jun 7, 2024, 7:17 AM Jun 7, 2024, 6:47 AM

                @stephenw10

                Latest updates on the situation:

                This morning I restarted pfsense at 06:30AM

                After the first restart, the unbound DNS in the service list is displayed with a working green icon.
                But it's not actually working.
                I did a manual restart of the service and it started working.
                This problem occurs every time I restart pfsense.

                Below is a log made at 08:45 AM showing the two startups of the service just described

                e0975d48-da29-47cf-825b-e40e1eb8c879-image.png

                Status/System Logs/System/DNS Resolver

                Jun 7 07:00:02	filterdns	37407	Adding Action: pf table: Block_Facebook host: gateway.facebook.com
                Jun 7 07:00:02	filterdns	37407	Adding Action: pf table: Block_Facebook host: cdn.fbsbx.com
                Jun 7 07:00:02	filterdns	37407	Adding Action: pf table: Block_Facebook host: scontent.xx.fbcdn.net
                Jun 7 07:00:02	filterdns	37407	Adding Action: pf table: Block_Facebook host: lookaside.facebook.com
                Jun 7 07:00:02	filterdns	37407	Adding Action: pf table: Block_Facebook host: graph.facebook.com
                Jun 7 07:00:02	filterdns	37407	Adding Action: pf table: Block_Facebook host: web.facebook.com
                Jun 7 07:00:02	filterdns	37407	merge_config: configuration reload
                Jun 7 07:00:02	filterdns	37407	failed to resolve host chat-dll.google.com will retry later again.
                Jun 7 07:00:02	filterdns	37407	failed to resolve host mobile-webview.google.com will retry later again.
                Jun 7 06:55:05	filterdns	37407	failed to resolve host chat-dll.google.com will retry later again.
                Jun 7 06:55:02	filterdns	37407	failed to resolve host mobile-webview.google.com will retry later again.
                Jun 7 06:51:28	unbound	17795	[17795:0] info: start of service (unbound 1.19.1).
                Jun 7 06:51:28	unbound	17795	[17795:0] notice: init module 0: iterator
                Jun 7 06:50:02	filterdns	37407	failed to resolve host chat-dll.google.com will retry later again.
                Jun 7 06:50:02	filterdns	37407	failed to resolve host mobile-webview.google.com will retry later again.
                Jun 7 06:45:03	filterdns	37407	failed to resolve host mobile-webview.google.com will retry later again.
                Jun 7 06:45:03	filterdns	37407	failed to resolve host chat-dll.google.com will retry later again.
                Jun 7 06:45:03	filterdns	37407	Adding Action: pf table: Gmail_Fqdn_list host: mtalk.google.com
                Jun 7 06:45:03	filterdns	37407	Adding Action: pf table: Gmail_Fqdn_list host: chat-dll.google.com
                Jun 7 06:45:03	filterdns	37407	Adding Action: pf table: Gmail_Fqdn_list host: mobile-webview.google.com
                Jun 7 06:45:03	filterdns	37407	Adding Action: pf table: Gmail_Fqdn_list host: accounts.google.com
                Jun 7 06:45:03	filterdns	37407	Adding Action: pf table: Gmail_Fqdn_list host: inbox.google.com
                Jun 7 06:45:03	filterdns	37407	Adding Action: pf table: Gmail_Fqdn_list host: mail.google.com
                Jun 7 06:45:03	filterdns	37407	Adding Action: pf table: Block_YouTube host: s.youtube.com
                Jun 7 06:45:03	filterdns	37407	Adding Action: pf table: Block_YouTube host: redirector.googlevideo.com
                Jun 7 06:45:03	filterdns	37407	Adding Action: pf table: Block_YouTube host: yt3.ggpht.com
                Jun 7 06:45:03	filterdns	37407	Adding Action: pf table: Block_YouTube host: youtubei.googleapis.com
                Jun 7 06:45:03	filterdns	37407	Adding Action: pf table: Block_YouTube host: www.youtube.com
                Jun 7 06:45:03	filterdns	37407	Adding Action: pf table: Block_YouTube host: i.ytimg.com
                Jun 7 06:45:03	filterdns	37407	Adding Action: pf table: Block_WhatsApp host: chat.cdn.whatsapp.net
                Jun 7 06:45:03	filterdns	37407	Adding Action: pf table: Block_WhatsApp host: web.whatsapp.com
                Jun 7 06:45:03	filterdns	37407	Adding Action: pf table: Block_WhatsApp host: g.whatsapp.net
                Jun 7 06:45:03	filterdns	37407	Adding Action: pf table: Block_WhatsApp host: static.whatsapp.net
                Jun 7 06:45:03	filterdns	37407	Adding Action: pf table: Block_WhatsApp host: dit.whatsapp.net
                Jun 7 06:45:03	filterdns	37407	Adding Action: pf table: Block_WhatsApp host: c.whatsapp.net
                Jun 7 06:45:03	filterdns	37407	Adding Action: pf table: Block_Instagram host: gateway.instagram.com
                Jun 7 06:45:03	filterdns	37407	Adding Action: pf table: Block_Instagram host: graph.instagram.com
                Jun 7 06:45:03	filterdns	37407	Adding Action: pf table: Block_Instagram host: i.instagram.com
                Jun 7 06:45:03	filterdns	37407	Adding Action: pf table: Block_Facebook host: edge-mqtt.facebook.com
                Jun 7 06:45:03	filterdns	37407	Adding Action: pf table: Block_Facebook host: static.xx.fbcdn.net
                Jun 7 06:45:03	filterdns	37407	Adding Action: pf table: Block_Facebook host: m.facebook.com
                Jun 7 06:45:03	filterdns	37407	Adding Action: pf table: Block_Facebook host: portal.fb.com
                Jun 7 06:45:03	filterdns	37407	Adding Action: pf table: Block_Facebook host: snaptu-z.facebook.com
                Jun 7 06:45:03	filterdns	37407	Adding Action: pf table: Block_Facebook host: www.facebook.com
                Jun 7 06:45:03	filterdns	37407	Adding Action: pf table: Block_Facebook host: gateway.facebook.com
                Jun 7 06:45:03	filterdns	37407	Adding Action: pf table: Block_Facebook host: cdn.fbsbx.com
                Jun 7 06:45:03	filterdns	37407	Adding Action: pf table: Block_Facebook host: scontent.xx.fbcdn.net
                Jun 7 06:45:03	filterdns	37407	Adding Action: pf table: Block_Facebook host: lookaside.facebook.com
                Jun 7 06:45:03	filterdns	37407	Adding Action: pf table: Block_Facebook host: graph.facebook.com
                Jun 7 06:45:03	filterdns	37407	Adding Action: pf table: Block_Facebook host: web.facebook.com
                Jun 7 06:45:03	filterdns	37407	merge_config: configuration reload
                Jun 7 06:41:46	filterdns	37407	failed to resolve host mobile-webview.google.com will retry later again.
                Jun 7 06:41:46	filterdns	37407	failed to resolve host chat-dll.google.com will retry later again.
                Jun 7 06:36:46	filterdns	37407	failed to resolve host chat-dll.google.com will retry later again.
                Jun 7 06:36:46	filterdns	37407	failed to resolve host mobile-webview.google.com will retry later again.
                Jun 7 06:31:47	filterdns	37407	failed to resolve host chat-dll.google.com will retry later again.
                Jun 7 06:31:47	filterdns	37407	failed to resolve host mobile-webview.google.com will retry later again.
                Jun 7 06:31:47	filterdns	37407	Adding Action: pf table: Gmail_Fqdn_list host: mtalk.google.com
                Jun 7 06:31:47	filterdns	37407	Adding Action: pf table: Gmail_Fqdn_list host: chat-dll.google.com
                Jun 7 06:31:47	filterdns	37407	Adding Action: pf table: Gmail_Fqdn_list host: mobile-webview.google.com
                Jun 7 06:31:47	filterdns	37407	Adding Action: pf table: Gmail_Fqdn_list host: accounts.google.com
                Jun 7 06:31:47	filterdns	37407	Adding Action: pf table: Gmail_Fqdn_list host: inbox.google.com
                Jun 7 06:31:47	filterdns	37407	Adding Action: pf table: Gmail_Fqdn_list host: mail.google.com
                Jun 7 06:31:47	filterdns	37407	Adding Action: pf table: Block_YouTube host: s.youtube.com
                Jun 7 06:31:47	filterdns	37407	Adding Action: pf table: Block_YouTube host: redirector.googlevideo.com
                Jun 7 06:31:47	filterdns	37407	Adding Action: pf table: Block_YouTube host: yt3.ggpht.com
                Jun 7 06:31:47	filterdns	37407	Adding Action: pf table: Block_YouTube host: youtubei.googleapis.com
                Jun 7 06:31:47	filterdns	37407	Adding Action: pf table: Block_YouTube host: www.youtube.com
                Jun 7 06:31:47	filterdns	37407	Adding Action: pf table: Block_YouTube host: i.ytimg.com
                Jun 7 06:31:47	filterdns	37407	Adding Action: pf table: Block_WhatsApp host: chat.cdn.whatsapp.net
                Jun 7 06:31:47	filterdns	37407	Adding Action: pf table: Block_WhatsApp host: web.whatsapp.com
                Jun 7 06:31:47	filterdns	37407	Adding Action: pf table: Block_WhatsApp host: g.whatsapp.net
                Jun 7 06:31:47	filterdns	37407	Adding Action: pf table: Block_WhatsApp host: static.whatsapp.net
                Jun 7 06:31:47	filterdns	37407	Adding Action: pf table: Block_WhatsApp host: dit.whatsapp.net
                Jun 7 06:31:47	filterdns	37407	Adding Action: pf table: Block_WhatsApp host: c.whatsapp.net
                Jun 7 06:31:47	filterdns	37407	Adding Action: pf table: Block_Instagram host: gateway.instagram.com
                Jun 7 06:31:47	filterdns	37407	Adding Action: pf table: Block_Instagram host: graph.instagram.com
                Jun 7 06:31:47	filterdns	37407	Adding Action: pf table: Block_Instagram host: i.instagram.com
                Jun 7 06:31:47	filterdns	37407	Adding Action: pf table: Block_Facebook host: edge-mqtt.facebook.com
                Jun 7 06:31:47	filterdns	37407	Adding Action: pf table: Block_Facebook host: static.xx.fbcdn.net
                Jun 7 06:31:47	filterdns	37407	Adding Action: pf table: Block_Facebook host: m.facebook.com
                Jun 7 06:31:47	filterdns	37407	Adding Action: pf table: Block_Facebook host: portal.fb.com
                Jun 7 06:31:47	filterdns	37407	Adding Action: pf table: Block_Facebook host: snaptu-z.facebook.com
                Jun 7 06:31:47	filterdns	37407	Adding Action: pf table: Block_Facebook host: www.facebook.com
                Jun 7 06:31:47	filterdns	37407	Adding Action: pf table: Block_Facebook host: gateway.facebook.com
                Jun 7 06:31:47	filterdns	37407	Adding Action: pf table: Block_Facebook host: cdn.fbsbx.com
                Jun 7 06:31:47	filterdns	37407	Adding Action: pf table: Block_Facebook host: scontent.xx.fbcdn.net
                Jun 7 06:31:47	filterdns	37407	Adding Action: pf table: Block_Facebook host: lookaside.facebook.com
                Jun 7 06:31:47	filterdns	37407	Adding Action: pf table: Block_Facebook host: graph.facebook.com
                Jun 7 06:31:47	filterdns	37407	Adding Action: pf table: Block_Facebook host: web.facebook.com
                Jun 7 06:31:47	filterdns	37407	merge_config: configuration reload
                Jun 7 06:31:27	filterdns	37407	failed to resolve host chat-dll.google.com will retry later again.
                Jun 7 06:31:27	filterdns	37407	Adding Action: pf table: Gmail_Fqdn_list host: mtalk.google.com
                Jun 7 06:31:27	filterdns	37407	Adding Action: pf table: Gmail_Fqdn_list host: chat-dll.google.com
                Jun 7 06:31:27	filterdns	37407	Adding Action: pf table: Gmail_Fqdn_list host: mobile-webview.google.com
                Jun 7 06:31:27	filterdns	37407	Adding Action: pf table: Gmail_Fqdn_list host: accounts.google.com
                Jun 7 06:31:27	filterdns	37407	Adding Action: pf table: Gmail_Fqdn_list host: inbox.google.com
                Jun 7 06:31:27	filterdns	37407	Adding Action: pf table: Gmail_Fqdn_list host: mail.google.com
                Jun 7 06:31:27	filterdns	37407	Adding Action: pf table: Block_YouTube host: s.youtube.com
                Jun 7 06:31:27	filterdns	37407	Adding Action: pf table: Block_YouTube host: redirector.googlevideo.com
                Jun 7 06:31:27	filterdns	37407	Adding Action: pf table: Block_YouTube host: yt3.ggpht.com
                Jun 7 06:31:27	filterdns	37407	Adding Action: pf table: Block_YouTube host: youtubei.googleapis.com
                Jun 7 06:31:27	filterdns	37407	Adding Action: pf table: Block_YouTube host: www.youtube.com
                Jun 7 06:31:27	filterdns	37407	Adding Action: pf table: Block_YouTube host: i.ytimg.com
                Jun 7 06:31:27	filterdns	37407	Adding Action: pf table: Block_WhatsApp host: chat.cdn.whatsapp.net
                Jun 7 06:31:27	filterdns	37407	Adding Action: pf table: Block_WhatsApp host: web.whatsapp.com
                Jun 7 06:31:27	filterdns	37407	Adding Action: pf table: Block_WhatsApp host: g.whatsapp.net
                Jun 7 06:31:27	filterdns	37407	Adding Action: pf table: Block_WhatsApp host: static.whatsapp.net
                Jun 7 06:31:27	filterdns	37407	Adding Action: pf table: Block_WhatsApp host: dit.whatsapp.net
                Jun 7 06:31:27	filterdns	37407	Adding Action: pf table: Block_WhatsApp host: c.whatsapp.net
                Jun 7 06:31:27	filterdns	37407	Adding Action: pf table: Block_Instagram host: gateway.instagram.com
                Jun 7 06:31:27	filterdns	37407	Adding Action: pf table: Block_Instagram host: graph.instagram.com
                Jun 7 06:31:27	filterdns	37407	Adding Action: pf table: Block_Instagram host: i.instagram.com
                Jun 7 06:31:27	filterdns	37407	Adding Action: pf table: Block_Facebook host: edge-mqtt.facebook.com
                Jun 7 06:31:27	filterdns	37407	Adding Action: pf table: Block_Facebook host: static.xx.fbcdn.net
                Jun 7 06:31:27	filterdns	37407	Adding Action: pf table: Block_Facebook host: m.facebook.com
                Jun 7 06:31:27	filterdns	37407	Adding Action: pf table: Block_Facebook host: portal.fb.com
                Jun 7 06:31:27	filterdns	37407	Adding Action: pf table: Block_Facebook host: snaptu-z.facebook.com
                Jun 7 06:31:27	filterdns	37407	Adding Action: pf table: Block_Facebook host: www.facebook.com
                Jun 7 06:31:27	filterdns	37407	Adding Action: pf table: Block_Facebook host: gateway.facebook.com
                Jun 7 06:31:27	filterdns	37407	Adding Action: pf table: Block_Facebook host: cdn.fbsbx.com
                Jun 7 06:31:27	filterdns	37407	Adding Action: pf table: Block_Facebook host: scontent.xx.fbcdn.net
                Jun 7 06:31:27	filterdns	37407	Adding Action: pf table: Block_Facebook host: lookaside.facebook.com
                Jun 7 06:31:27	filterdns	37407	Adding Action: pf table: Block_Facebook host: graph.facebook.com
                Jun 7 06:31:27	filterdns	37407	Adding Action: pf table: Block_Facebook host: web.facebook.com
                Jun 7 06:31:27	filterdns	37407	merge_config: configuration reload
                Jun 7 06:31:25	filterdns	37407	failed to resolve host chat-dll.google.com will retry later again.
                Jun 7 06:31:24	filterdns	37407	failed to resolve host mobile-webview.google.com will retry later again.
                Jun 7 06:31:24	filterdns	37146	Adding host mtalk.google.com
                Jun 7 06:31:24	filterdns	37146	Adding Action: pf table: Gmail_Fqdn_list host: mtalk.google.com
                Jun 7 06:31:24	filterdns	37146	Adding host chat-dll.google.com
                Jun 7 06:31:24	filterdns	37146	Adding Action: pf table: Gmail_Fqdn_list host: chat-dll.google.com
                Jun 7 06:31:24	filterdns	37146	Adding host mobile-webview.google.com
                Jun 7 06:31:24	filterdns	37146	Adding Action: pf table: Gmail_Fqdn_list host: mobile-webview.google.com
                Jun 7 06:31:24	filterdns	37146	Adding host accounts.google.com
                Jun 7 06:31:24	filterdns	37146	Adding Action: pf table: Gmail_Fqdn_list host: accounts.google.com
                Jun 7 06:31:24	filterdns	37146	Adding host inbox.google.com
                Jun 7 06:31:24	filterdns	37146	Adding Action: pf table: Gmail_Fqdn_list host: inbox.google.com
                Jun 7 06:31:24	filterdns	37146	Adding host mail.google.com
                Jun 7 06:31:24	filterdns	37146	Adding Action: pf table: Gmail_Fqdn_list host: mail.google.com
                Jun 7 06:31:24	filterdns	37146	Adding host s.youtube.com
                Jun 7 06:31:24	filterdns	37146	Adding Action: pf table: Block_YouTube host: s.youtube.com
                Jun 7 06:31:24	filterdns	37146	Adding host redirector.googlevideo.com
                Jun 7 06:31:24	filterdns	37146	Adding Action: pf table: Block_YouTube host: redirector.googlevideo.com
                Jun 7 06:31:24	filterdns	37146	Adding host yt3.ggpht.com
                Jun 7 06:31:24	filterdns	37146	Adding Action: pf table: Block_YouTube host: yt3.ggpht.com
                Jun 7 06:31:24	filterdns	37146	Adding host youtubei.googleapis.com
                Jun 7 06:31:24	filterdns	37146	Adding Action: pf table: Block_YouTube host: youtubei.googleapis.com
                Jun 7 06:31:24	filterdns	37146	Adding host www.youtube.com
                Jun 7 06:31:24	filterdns	37146	Adding Action: pf table: Block_YouTube host: www.youtube.com
                Jun 7 06:31:24	filterdns	37146	Adding host i.ytimg.com
                Jun 7 06:31:24	filterdns	37146	Adding Action: pf table: Block_YouTube host: i.ytimg.com
                Jun 7 06:31:24	filterdns	37146	Adding host chat.cdn.whatsapp.net
                Jun 7 06:31:24	filterdns	37146	Adding Action: pf table: Block_WhatsApp host: chat.cdn.whatsapp.net
                Jun 7 06:31:24	filterdns	37146	Adding host web.whatsapp.com
                Jun 7 06:31:24	filterdns	37146	Adding Action: pf table: Block_WhatsApp host: web.whatsapp.com
                Jun 7 06:31:24	filterdns	37146	Adding host g.whatsapp.net
                Jun 7 06:31:24	filterdns	37146	Adding Action: pf table: Block_WhatsApp host: g.whatsapp.net
                Jun 7 06:31:24	filterdns	37146	Adding host static.whatsapp.net
                Jun 7 06:31:24	filterdns	37146	Adding Action: pf table: Block_WhatsApp host: static.whatsapp.net
                Jun 7 06:31:24	filterdns	37146	Adding host dit.whatsapp.net
                Jun 7 06:31:24	filterdns	37146	Adding Action: pf table: Block_WhatsApp host: dit.whatsapp.net
                Jun 7 06:31:24	filterdns	37146	Adding host c.whatsapp.net
                Jun 7 06:31:24	filterdns	37146	Adding Action: pf table: Block_WhatsApp host: c.whatsapp.net
                Jun 7 06:31:24	filterdns	37146	Adding host gateway.instagram.com
                Jun 7 06:31:24	filterdns	37146	Adding Action: pf table: Block_Instagram host: gateway.instagram.com
                Jun 7 06:31:24	filterdns	37146	Adding host graph.instagram.com
                Jun 7 06:31:24	filterdns	37146	Adding Action: pf table: Block_Instagram host: graph.instagram.com
                Jun 7 06:31:24	filterdns	37146	Adding host i.instagram.com
                Jun 7 06:31:24	filterdns	37146	Adding Action: pf table: Block_Instagram host: i.instagram.com
                Jun 7 06:31:24	filterdns	37146	Adding host edge-mqtt.facebook.com
                Jun 7 06:31:24	filterdns	37146	Adding Action: pf table: Block_Facebook host: edge-mqtt.facebook.com
                Jun 7 06:31:24	filterdns	37146	Adding host static.xx.fbcdn.net
                Jun 7 06:31:24	filterdns	37146	Adding Action: pf table: Block_Facebook host: static.xx.fbcdn.net
                Jun 7 06:31:24	filterdns	37146	Adding host m.facebook.com
                Jun 7 06:31:24	filterdns	37146	Adding Action: pf table: Block_Facebook host: m.facebook.com
                Jun 7 06:31:24	filterdns	37146	Adding host portal.fb.com
                Jun 7 06:31:24	filterdns	37146	Adding Action: pf table: Block_Facebook host: portal.fb.com
                Jun 7 06:31:24	filterdns	37146	Adding host snaptu-z.facebook.com
                Jun 7 06:31:24	filterdns	37146	Adding Action: pf table: Block_Facebook host: snaptu-z.facebook.com
                Jun 7 06:31:24	filterdns	37146	Adding host www.facebook.com
                Jun 7 06:31:24	filterdns	37146	Adding Action: pf table: Block_Facebook host: www.facebook.com
                Jun 7 06:31:24	filterdns	37146	Adding host gateway.facebook.com
                Jun 7 06:31:24	filterdns	37146	Adding Action: pf table: Block_Facebook host: gateway.facebook.com
                Jun 7 06:31:24	filterdns	37146	Adding host cdn.fbsbx.com
                Jun 7 06:31:24	filterdns	37146	Adding Action: pf table: Block_Facebook host: cdn.fbsbx.com
                Jun 7 06:31:24	filterdns	37146	Adding host scontent.xx.fbcdn.net
                Jun 7 06:31:24	filterdns	37146	Adding Action: pf table: Block_Facebook host: scontent.xx.fbcdn.net
                Jun 7 06:31:24	filterdns	37146	Adding host lookaside.facebook.com
                Jun 7 06:31:24	filterdns	37146	Adding Action: pf table: Block_Facebook host: lookaside.facebook.com
                Jun 7 06:31:24	filterdns	37146	Adding host graph.facebook.com
                Jun 7 06:31:24	filterdns	37146	Adding Action: pf table: Block_Facebook host: graph.facebook.com
                Jun 7 06:31:24	filterdns	37146	Adding host web.facebook.com
                Jun 7 06:31:24	filterdns	37146	Adding Action: pf table: Block_Facebook host: web.facebook.com
                Jun 7 06:31:03	unbound	81793	[81793:0] info: start of service (unbound 1.19.1).
                Jun 7 06:31:03	unbound	81793	[81793:0] notice: init module 0: iterator
                

                In particular line:

                Jun 7 06:31:24 filterdns 37146 Adding Action: pf table: Block_Facebook host: web.facebook.com
                Jun 7 06:31:03 unbound 81793 [81793:0] info: start of service (unbound 1.19.1).
                Jun 7 06:31:03 unbound 81793 [81793:0] notice: init module 0: iterator
                Jun 7 06:25:03 filterdns 29751 failed to resolve host mobile-webview.google.com will retry later again.

                .....
                .....
                Jun 7 06:51:28 unbound 17795 [17795:0] info: start of service (unbound 1.19.1).
                Jun 7 06:51:28 unbound 17795 [17795:0] notice: init module 0: iterator

                Using the "pkg search unbound" command we discovered that my pfsense 2.7.2 had DNS unbound version 1.18.0_1.

                Using the command "pkg install unbound-1.19.1" I installed the new update to version 1.19.1

                I did a system reboot.

                Throughout yesterday the log showed the two versions but I think it's normal, there are times that demonstrate the relevant version at that moment.

                Using the command "cat /var/log/resolver.log | grep 'start'" I can see that only version 1.19.1 appears in today's logs

                I had also disabled DHCP Registration in Unbound DNS because it caused the service to continually restart.

                The situation has improved, there are no longer continuous restarts of the unbound DNS service and we also have the latest version 1.19.1.
                What can I do to resolve the problem that after the first start of pfsense the unbound DNS does not work (even if in the list of services the unbound DNS appears with a working green check box icon) and I have to restart the service manually?

                pfSensePlus24.03 2U BareMetal Asrock Industrial IMB-X1314MicroATX
                CPU: i7-13700@5.2GHz, RAM:32GB ECC, n°2 Samsung 870EVO SATA 2.5” SSD 1TB (ZFS) Raid1
                n°3 Intel i225-LM 2500/1000/100Mbps, n°1 NIC Intel i350-T4V2 10/100/1000 Mbps 4*GLAN, n°1 Intel X520-DA2

                G 1 Reply Last reply Jun 7, 2024, 7:53 AM Reply Quote 0
                • U
                  Unoptanio @johnpoz
                  last edited by Unoptanio Jun 7, 2024, 7:21 AM Jun 7, 2024, 7:13 AM

                  @johnpoz

                  Yesterday..... using the "pkg search unbound" command we discovered that my pfsense 2.7.2 had DNS unbound version 1.18.0_1.

                  Using the command "pkg install unbound-1.19.1" I installed the new update to version 1.19.1

                  I did a system reboot.

                  Throughout yesterday the log showed the two versions but I think it's normal, there are times that demonstrate the relevant version at that moment.

                  Using the command "cat /var/log/resolver.log | grep 'start'" I can see that only version 1.19.1 appears in today's logs

                  I had also disabled DHCP Registration in Unbound DNS because it caused the service to continually restart.

                  Thanks to you I discovered another interesting command "pkg upgrade" which checks if there are updates on all packages

                  The situation has improved, there are no longer continuous restarts of the unbound DNS service and we also have the latest version 1.19.1.
                  What can I do to resolve the problem that after the first start of pfsense the unbound DNS does not work (even if in the list of services the unbound DNS appears with a working green check box icon) and I have to restart the service manually?

                  pfSensePlus24.03 2U BareMetal Asrock Industrial IMB-X1314MicroATX
                  CPU: i7-13700@5.2GHz, RAM:32GB ECC, n°2 Samsung 870EVO SATA 2.5” SSD 1TB (ZFS) Raid1
                  n°3 Intel i225-LM 2500/1000/100Mbps, n°1 NIC Intel i350-T4V2 10/100/1000 Mbps 4*GLAN, n°1 Intel X520-DA2

                  F 1 Reply Last reply Jun 7, 2024, 7:19 AM Reply Quote 0
                  • F
                    fireodo @Unoptanio
                    last edited by Jun 7, 2024, 7:19 AM

                    @Unoptanio said in Problem with DNS resolver:

                    I had also disabled DHCP Registration in Unbound DNS because it caused the service to continually restart.

                    So this was the real culprit ...

                    The situation has improved, there are no longer continuous restarts of the unbound DNS service and we also have the latest version 1.19.1.
                    What can I do to resolve the problem that after the first start of pfsense the unbound DNS does not work (even if in the list of services the unbound DNS appears with a working green check box icon) and I have to restart the service manually?

                    Maybe enable verbose logging to see if there is a hint in the log what is causing unbound not to start properly ...

                    Kettop Mi4300YL CPU: i5-4300Y @ 1.60GHz RAM: 8GB Ethernet Ports: 4
                    SSD: SanDisk pSSD-S2 16GB (ZFS) WiFi: WLE200NX
                    pfsense 2.8.0 CE
                    Packages: Apcupsd, Cron, Iftop, Iperf, LCDproc, Nmap, pfBlockerNG, RRD_Summary, Shellcmd, Snort, Speedtest, System_Patches.

                    U 1 Reply Last reply Jun 7, 2024, 7:25 AM Reply Quote 0
                    • U
                      Unoptanio @fireodo
                      last edited by Jun 7, 2024, 7:25 AM

                      @fireodo

                      Where do you enable verbose logging?

                      pfSensePlus24.03 2U BareMetal Asrock Industrial IMB-X1314MicroATX
                      CPU: i7-13700@5.2GHz, RAM:32GB ECC, n°2 Samsung 870EVO SATA 2.5” SSD 1TB (ZFS) Raid1
                      n°3 Intel i225-LM 2500/1000/100Mbps, n°1 NIC Intel i350-T4V2 10/100/1000 Mbps 4*GLAN, n°1 Intel X520-DA2

                      F 1 Reply Last reply Jun 7, 2024, 7:29 AM Reply Quote 0
                      • F
                        fireodo @Unoptanio
                        last edited by Jun 7, 2024, 7:29 AM

                        @Unoptanio said in Problem with DNS resolver:

                        Where do you enable verbose logging?

                        services_unbound_advanced.php

                        scroll down - "log level"

                        Kettop Mi4300YL CPU: i5-4300Y @ 1.60GHz RAM: 8GB Ethernet Ports: 4
                        SSD: SanDisk pSSD-S2 16GB (ZFS) WiFi: WLE200NX
                        pfsense 2.8.0 CE
                        Packages: Apcupsd, Cron, Iftop, Iperf, LCDproc, Nmap, pfBlockerNG, RRD_Summary, Shellcmd, Snort, Speedtest, System_Patches.

                        1 Reply Last reply Reply Quote 0
                        • G
                          Gertjan @Unoptanio
                          last edited by Gertjan Jun 7, 2024, 7:57 AM Jun 7, 2024, 7:53 AM

                          Don't worry about this one. The domain "mobile-webview.google.com" doesn't exist ....
                          I've tried several revolvers world wide : not found.

                          @Unoptanio said in Problem with DNS resolver:

                          Jun 7 06:25:03 filterdns 29751 failed to resolve host mobile-webview.google.com will retry later again.

                          You've set yourself "mobile-webview.google.com" as filterdns is trying its out most best to resolve it.
                          Not very useful.

                          This line can create 'huge' problems with DNS :

                          @Unoptanio said in Problem with DNS resolver:

                          Jun 7 07:00:02 filterdns 37407 Adding Action: pf table: Block_Facebook host: web.facebook.com

                          Read this : Aliases.

                          This is a typical case of :

                          3718bf87-260b-428b-a9e8-81af105f861f-image.png

                          Where "not useful" is an understatement.
                          When a typical *.facebook.com host name is resolved, it will return many, like a lot, of IP addresses.
                          The filterdns process is executed every xx seconds or so to update the relation 'host name' => IPs. If the list with IP changes, and it will change constantly, the firewall is reload, .... and process (like unbound) get restarted.
                          Do you see where this is going ?

                          Remove all your references to google or facebook in your aliases tables. If you need to filter these, use pfBlockerng.
                          Your unbound will say thank you to you.

                          No "help me" PM's please. Use the forum, the community will thank you.
                          Edit : and where are the logs ??

                          1 Reply Last reply Reply Quote 0
                          • P
                            Popolou @Unoptanio
                            last edited by Jun 7, 2024, 10:06 AM

                            @Unoptanio said in Problem with DNS resolver:

                            1b9a831c-3bf7-48a4-8971-994119916046-image.png

                            Disable unbound listening on the WAN and see if it stays up.

                            U 1 Reply Last reply Jun 7, 2024, 12:48 PM Reply Quote 1
                            • S
                              stephenw10 Netgate Administrator
                              last edited by Jun 7, 2024, 12:24 PM

                              Yeah the first thing I would do is remove those two failing hosts that don't exist.

                              Jun 7 06:41:46	filterdns	37407	failed to resolve host mobile-webview.google.com will retry later again.
                              Jun 7 06:41:46	filterdns	37407	failed to resolve host chat-dll.google.com will retry later again.
                              
                              U 2 Replies Last reply Jun 7, 2024, 12:49 PM Reply Quote 1
                              • U
                                Unoptanio @Popolou
                                last edited by Jun 7, 2024, 12:48 PM

                                @Popolou
                                Done

                                pfSensePlus24.03 2U BareMetal Asrock Industrial IMB-X1314MicroATX
                                CPU: i7-13700@5.2GHz, RAM:32GB ECC, n°2 Samsung 870EVO SATA 2.5” SSD 1TB (ZFS) Raid1
                                n°3 Intel i225-LM 2500/1000/100Mbps, n°1 NIC Intel i350-T4V2 10/100/1000 Mbps 4*GLAN, n°1 Intel X520-DA2

                                1 Reply Last reply Reply Quote 0
                                • U
                                  Unoptanio @stephenw10
                                  last edited by Jun 7, 2024, 12:49 PM

                                  @stephenw10
                                  Done

                                  pfSensePlus24.03 2U BareMetal Asrock Industrial IMB-X1314MicroATX
                                  CPU: i7-13700@5.2GHz, RAM:32GB ECC, n°2 Samsung 870EVO SATA 2.5” SSD 1TB (ZFS) Raid1
                                  n°3 Intel i225-LM 2500/1000/100Mbps, n°1 NIC Intel i350-T4V2 10/100/1000 Mbps 4*GLAN, n°1 Intel X520-DA2

                                  1 Reply Last reply Reply Quote 1
                                  • U
                                    Unoptanio @stephenw10
                                    last edited by Unoptanio Jun 8, 2024, 7:11 AM Jun 8, 2024, 5:16 AM

                                    @stephenw10

                                    Ok!. It seems like everything is working fine now.
                                    I restarted the PC at 7:00 am.
                                    After the reboot everything works fine.
                                    Unbound DNS works.

                                    In summary: steps to solve the problem

                                    1. Disabled DHCP Registration in DNS Unbound (caused continuous restarts of the service)
                                    2. Disable unbound listening on the WAN (caused the service to be restarted twice)
                                    3. It is recommended to install the latest version of the Unbound DNS service

                                    4432076f-ac73-46c7-8081-cb3e0ecc06f5-image.png

                                    7fb3aa30-4148-424f-8cae-591e286786c0-image.png

                                    pfSensePlus24.03 2U BareMetal Asrock Industrial IMB-X1314MicroATX
                                    CPU: i7-13700@5.2GHz, RAM:32GB ECC, n°2 Samsung 870EVO SATA 2.5” SSD 1TB (ZFS) Raid1
                                    n°3 Intel i225-LM 2500/1000/100Mbps, n°1 NIC Intel i350-T4V2 10/100/1000 Mbps 4*GLAN, n°1 Intel X520-DA2

                                    D J 2 Replies Last reply Jun 8, 2024, 8:27 AM Reply Quote 2
                                    • D
                                      darcey @Unoptanio
                                      last edited by Jun 8, 2024, 8:27 AM

                                      @Unoptanio said in Problem with DNS resolver:

                                      In summary: steps to solve the problem

                                      Disabled DHCP Registration in DNS Unbound (caused continuous restarts of the service)
                                      Disable unbound listening on the WAN (caused the service to be restarted twice)
                                      It is recommended to install the latest version of the Unbound DNS service
                                      

                                      Good to hear you've sorted it.
                                      Having unbound serve dns records for DHCP leases is known to cause restarts. I think many here disable it and create static leases for those hosts they do want to resolve.
                                      I found explicitly selecting listening interfaces often caused problems with unbound not starting. I set it to 'all', relied on firewall default blocking to prevent access where it wasn't desired, no more unbound start-up issues.
                                      I doubt the upgrade contributed to fixing the issues you were seeing. I reckon it came down solely to the listening interfaces selection!

                                      1 Reply Last reply Reply Quote 1
                                      • J
                                        johnpoz LAYER 8 Global Moderator @Unoptanio
                                        last edited by Jun 8, 2024, 10:30 AM

                                        @Unoptanio said in Problem with DNS resolver:

                                        It is recommended to install the latest version of the Unbound DNS service

                                        this should be taken care of by just upgrading pfsense - still not understanding how you had both on the system??

                                        An intelligent man is sometimes forced to be drunk to spend time with his fools
                                        If you get confused: Listen to the Music Play
                                        Please don't Chat/PM me for help, unless mod related
                                        SG-4860 24.11 | Lab VMs 2.8, 24.11

                                        U 1 Reply Last reply Jun 8, 2024, 10:53 AM Reply Quote 0
                                        • U
                                          Unoptanio @johnpoz
                                          last edited by Unoptanio Jun 8, 2024, 10:55 AM Jun 8, 2024, 10:53 AM

                                          @johnpoz

                                          Initially I only had version 1.18.0_1 of the unbound DNS.
                                          After updating to version 1.19.1, despite restarting the PC, the two versions were the same. The next day only version 1.19.1 remained.
                                          In the meantime, other PC reboots were made

                                          But isn't it just the log of versions at various times?

                                          d7d77d0d-9ea6-42c4-baac-a071ef807ac5-image.png

                                          pfSensePlus24.03 2U BareMetal Asrock Industrial IMB-X1314MicroATX
                                          CPU: i7-13700@5.2GHz, RAM:32GB ECC, n°2 Samsung 870EVO SATA 2.5” SSD 1TB (ZFS) Raid1
                                          n°3 Intel i225-LM 2500/1000/100Mbps, n°1 NIC Intel i350-T4V2 10/100/1000 Mbps 4*GLAN, n°1 Intel X520-DA2

                                          J 1 Reply Last reply Jun 8, 2024, 10:55 AM Reply Quote 0
                                          46 out of 64
                                          • First post
                                            46/64
                                            Last post
                                          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
                                            This community forum collects and processes your personal information.
                                            consent.not_received