• 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 4.7k 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.
  • D
    darcey @fireodo
    last edited by Jun 6, 2024, 9:04 AM

    @fireodo Thanks, I'd completely forgotten about this. It seems on my system, unbound and curl have updates available.
    Still I think I am going to leave it as is as things are running very smoothly for me of late.

    F 1 Reply Last reply Jun 6, 2024, 9:08 AM Reply Quote 0
    • F
      fireodo @darcey
      last edited by fireodo Jun 6, 2024, 9:08 AM Jun 6, 2024, 9:08 AM

      @darcey said in Problem with DNS resolver:

      Still I think I am going to leave it as is as things are running very smoothly for me of late.

      Never change a running system ... old wisdom šŸ˜€
      (curl has a security issue so I recommend to upgrade)

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

      1 Reply Last reply Reply Quote 1
      • U
        Unoptanio @fireodo
        last edited by Jun 6, 2024, 11:09 AM

        @fireodo

        After restart system

        1b69725c-d044-4d74-80fc-215d75b1fe68-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

        G F 2 Replies Last reply Jun 6, 2024, 11:15 AM Reply Quote 0
        • G
          Gertjan @Unoptanio
          last edited by Jun 6, 2024, 11:15 AM

          @Unoptanio

          That's unbound in permanent restart mode !
          You can stop that now, as the test succeeded.

          To stop the testing :
          Uncheck :

          1f41ac53-2bb6-431e-8c5a-dccf4c3d70f0-image.png

          Save, and Apply.

          ( I'm trying a new solution to a 10+ year old question )

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

          U 1 Reply Last reply Jun 6, 2024, 12:19 PM Reply Quote 1
          • F
            fireodo @Unoptanio
            last edited by fireodo Jun 6, 2024, 11:52 AM Jun 6, 2024, 11:33 AM

            @Unoptanio said in Problem with DNS resolver:

            After restart system

            😧

            Do you have the register dhcp-leases in dns resolver (as gertjan indicates) on?

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

            1 Reply Last reply Reply Quote 1
            • U
              Unoptanio @Gertjan
              last edited by Unoptanio Jun 6, 2024, 12:26 PM Jun 6, 2024, 12:19 PM

              @Gertjan

              Done now at 2.18pm

              edc6b2b9-d797-4981-9ba5-4c5a57581db5-image.png

              Now I try to disable DHCP Registration

              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, 12:22 PM

                Run pkg upgrade to check if there are any updated system packages available.

                We build newer versions of packages if they are available with fixes for specific issues that users may be hitting. They are then available to upgrade to but these are not expected or required upgrades.

                In the instance that upgrades are required for security issues we would usually either issues an announcement or a point release of pfSense depending on the severity.

                I would not expect the Unbound version to be the issue here. But it also doesn't hurt to update it and it's an easy test. šŸ˜‰

                Steve

                U 1 Reply Last reply Jun 6, 2024, 12:31 PM Reply Quote 1
                • U
                  Unoptanio @stephenw10
                  last edited by Unoptanio Jun 6, 2024, 12:32 PM Jun 6, 2024, 12:31 PM

                  @stephenw10 said in Problem with DNS resolver:

                  pkg upgrade

                  [2.7.2-RELEASE][admin@xxxxx]/root: pkg upgrade
                  Updating pfSense-core repository catalogue...
                  Fetching meta.conf:   0%
                  Fetching packagesite.pkg:   0%
                  pfSense-core repository is up to date.
                  Updating pfSense repository catalogue...
                  Fetching meta.conf:   0%
                  Fetching packagesite.pkg:   0%
                  pfSense repository is up to date.
                  All repositories are up to date.
                  Checking for upgrades (3 candidates): 100%      3 B   0.0kB/s    00:01
                  Processing candidates (3 candidates): 100%      3 B   0.0kB/s    00:01
                  The following 1 package(s) will be affected (of 0 checked):
                  
                  Installed packages to be UPGRADED:
                          curl: 8.4.0 -> 8.6.0 [pfSense]
                  
                  Number of packages to be upgraded: 1
                  
                  1 MiB to be downloaded.
                  
                  Proceed with this action? [y/N]:
                  
                  

                  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, 1:14 PM

                    Yup, you can upgrade curl. But not upgrading it should not be an issue.

                    U 1 Reply Last reply Jun 6, 2024, 4:02 PM Reply Quote 0
                    • 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.7.2, 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.7.2 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.7.2 CE
                                          Packages: Apcupsd Cron Iftop Iperf LCDproc Nmap pfBlockerNG RRD_Summary Shellcmd Snort Speedtest System_Patches.

                                          1 Reply Last reply Reply Quote 0
                                          47 out of 64
                                          • First post
                                            47/64
                                            Last post
                                          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
                                            This community forum collects and processes your personal information.
                                            consent.not_received