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

    DNS doesn't work for local devices.

    Scheduled Pinned Locked Moved DHCP and DNS
    10 Posts 3 Posters 707 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
      doni49
      last edited by doni49

      The only way I'm able to browse to any of the devices on my network is to use the IP Address. For example, when I want to browse to Home Assistant, I have to enter 10.20.0.2:8123. If I enter http://homeassistant.local:8123, it just times out.
      DHCP Lease for Home Assistant

      Here are screenshots of my DNS settings.
      DNS Resolver General Settings

      DNS Resolver Advanced Settings

      V 1 Reply Last reply Reply Quote 0
      • V
        viragomann @doni49
        last edited by

        @doni49
        The point is if your client device resolves the host name properly.

        So run nslookup or dig against homeassistant.local to verify its DNS resolution.

        If you get the correct IP your browser might most probably use DoH. Then you need to disable it in the browser or take steps to avoid this on pfSense.

        D 2 Replies Last reply Reply Quote 0
        • D
          doni49 @viragomann
          last edited by doni49

          @viragomann

          nslookup can't find it either.

          C:\Users\LiveI>nslookup
          Default Server: pfSense.home.arpa
          Address: 10.1.1.1

          homeassistant.local
          Server: pfSense.home.arpa
          Address: 10.1.1.1

          *** pfSense.home.arpa can't find homeassistant.local: Non-existent domain

          V johnpozJ 2 Replies Last reply Reply Quote 0
          • V
            viragomann @doni49
            last edited by

            @doni49
            I see. So its on your DNS.

            You're awaiting that the DHCP does the DNS entry.
            Do you use KEA by an chance?
            DNS entries are not supported by KEA yet. You can switch to ISC DHCP or add a DNS host override manually.

            1 Reply Last reply Reply Quote 0
            • johnpozJ
              johnpoz LAYER 8 Global Moderator @doni49
              last edited by

              @doni49 why would you think your fqdn for you homeassistant is homeassistant.local?

              pfsense is clearly using home.arpa as it domain. So create a record for your homeassistant.home.arpa in host overrides, or setup a reservation for it so it always gets the same IP. And or register dhcp, but that last option is going to cause unbound to restart all the time.

              .local is used my mdns, for that to resolver client would have to send out a mdns query to the local network, your homeA would have to be on the same local network and would have to respond itself - hey yeah that is my name.

              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

              1 Reply Last reply Reply Quote 0
              • D
                doni49 @viragomann
                last edited by

                @viragomann

                Ok. That's unexpected. I went to Diagnostics > DNS Resolver, entered homeassistant (without .local) in the field and submitted.

                It found it. So I tried browsing to homeassistant:8123. That put me through fine.

                johnpozJ 1 Reply Last reply Reply Quote 0
                • johnpozJ
                  johnpoz LAYER 8 Global Moderator @doni49
                  last edited by

                  @doni49 that would be your seach suffix most like auto doing query for the domain your machine is using, ie what pfsense handed out via dhcp which would be home.arpa

                  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

                  D 1 Reply Last reply Reply Quote 0
                  • D
                    doni49 @johnpoz
                    last edited by

                    Ok. Thanks. Every time I think I'm figuring things out, I find more to learn. :)

                    johnpozJ 1 Reply Last reply Reply Quote 0
                    • johnpozJ
                      johnpoz LAYER 8 Global Moderator @doni49
                      last edited by johnpoz

                      @doni49 said in DNS doesn't work for local devices.:

                      Every time I think I'm figuring things out, I find more to learn. :)

                      Yup that how it works ;) heheh welcome to life..

                      I learn something new multiple times a day ;)

                      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

                      D 1 Reply Last reply Reply Quote 1
                      • D
                        doni49 @johnpoz
                        last edited by

                        @johnpoz

                        Yep -- definitely not a complaint. I enjoy learning it all. In all the examples I've seen, .local was used after the hostname. The use of mDNS was never mentioned so I assumed .local was part of the base DNS configuration.

                        I started reading up on mDNS a few weeks ago -- I guess I haven't made it that far yet.

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