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

    Internal hostnames doesn't work 2.3

    Scheduled Pinned Locked Moved DHCP and DNS
    4 Posts 3 Posters 1.3k 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.
    • N Offline
      notaduck
      last edited by

      So as so many other did when 2.3 was released I was also clapping my hands out of excitement for the new GUI.
      but after i updated from 2.2 to 2.3 then all of my internal hostnames there was controlled by pfSense's dns resolver stopped working?

      when i try to ssh and use a hostname then i get this respond

      ssh root@puppet.home
      ssh: Could not resolve hostname puppet.home: Name or service not known
      
      
      1 Reply Last reply Reply Quote 0
      • jimpJ Offline
        jimp Rebel Alliance Developer Netgate
        last edited by

        DNS Resolver or DNS Forwarder?
        Host overrides or are they coming from DHCP?

        Remember: Upvote with the ๐Ÿ‘ button for any user/post you find to be helpful, informative, or deserving of recognition!

        Need help fast? Netgate Global Support!

        Do not Chat/PM for help!

        1 Reply Last reply Reply Quote 0
        • A Offline
          AllGamer
          last edited by

          for reference (working for me)

          after upgrading from 2.2.6 to 2.3

          I had to enable DNS resolver to bring names from DHCP assigned dynamically, and DHCP reserved (sorry forgot the actual names used by pfsense)
          it was two separate check boxes.

          โ€“- Edit ---
          Found the correct names
          I had to enable:

          • Register DHCP leases in the DNS Resolver
          • Register DHCP static mappings in the DNS Resolver

          both inside DNS Resolver / General Settings

          1 Reply Last reply Reply Quote 0
          • N Offline
            notaduck
            last edited by

            Thanks! this did solve the problem

            @AllGamer:

            for reference (working for me)

            after upgrading from 2.2.6 to 2.3

            I had to enable DNS resolver to bring names from DHCP assigned dynamically, and DHCP reserved (sorry forgot the actual names used by pfsense)
            it was two separate check boxes.

            โ€“- Edit ---
            Found the correct names
            I had to enable:

            • Register DHCP leases in the DNS Resolver
            • Register DHCP static mappings in the DNS Resolver

            both inside DNS Resolver / General Settings

            1 Reply Last reply Reply Quote 0
            • First post
              Last post
            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.