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

    DNS Resolver refreshing question

    Scheduled Pinned Locked Moved DHCP and DNS
    4 Posts 2 Posters 531 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.
    • T
      takeshi
      last edited by

      Hello,

      I’m new to this forum.
      If it’s not the appropriate place to this kind of question, please move/delete this thread.

      Yesterday I installed pfSense 2.4.2. The installation went smooth and it seems to work great so far.

      One concern I have is when I add new host overrides in DNS resolver, for example test.domain.com to 192.168.1.100, I can’t resolve test.domain.com until I restart the DNS resolver manually in the services page.

      The same scenario is with DNS forwarder, I am able to resolve new host overrides only after I restart dnsmasq manually in the services page.

      Is it normal? If yes, is it possible to restart the service automatically?

      Thanks.

      1 Reply Last reply Reply Quote 0
      • GertjanG
        Gertjan
        last edited by

        Hi,

        Just tested this with the Resolver (unbound) :  add a test.my-pfsense-domaine.tld with an IP 192.168.1.50 - "Save" and then "Apply Changes" (top of the screen).
        The logs showed that unbound restarted.
        When I pinged to "test", it resolved fine to 192.168.1.50.

        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
        • T
          takeshi
          last edited by

          @Gertjan:

          Hi,

          Just tested this with the Resolver (unbound) :  add a test.my-pfsense-domaine.tld with an IP 192.168.1.50 - "Save" and then "Apply Changes" (top of the screen).
          The logs showed that unbound restarted.
          When I pinged to "test", it resolved fine to 192.168.1.50.

          Thank you!

          It seems like I have some problem with my setup then.
          I have nothing in the logs when I add new hosts.

          I will try to reinstall pfSense later today.
          Maybe I messed something up.

          I wonder what prevent from unbound to restart.

          1 Reply Last reply Reply Quote 0
          • GertjanG
            Gertjan
            last edited by

            "Apply changes" will recreate a config file, needed for unbound, the Resolver.
            Then unboud will get restarted - there is nothing you should do, or shouldn't do, to make that happen.

            You're checking this log : Status => System Logs => System => DNS Resolver, right ?

            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
            • First post
              Last post
            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.