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

    No hostname shown with custom dynamic dns

    Scheduled Pinned Locked Moved DHCP and DNS
    7 Posts 6 Posters 1.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.
    • _
      _igor_
      last edited by

      I'm using aidns.net as custom dynamic dns service. Now i see that no hostname is shown, but update occurs (IP showing green). The host is reachable via the dynamic dns-name.

      Logs don't show anything, except of the successful extraction of IP and successful update.

      Any hint on how to get the hostname shown?

      PS: full install of pfsense 2.2 amd64 on pc hardware.

      1 Reply Last reply Reply Quote 0
      • _
        _igor_
        last edited by

        It seems to me a bug…

        No entry for hostname available, that should be fixed.

        I added the hostname directly into the config.xml, it works now right.

        1 Reply Last reply Reply Quote 0
        • I
          ILLCOMM
          last edited by

          same issue.

          1 Reply Last reply Reply Quote 0
          • D
            doktornotor Banned
            last edited by

            No such thing has ever been shown with custom DNS type.

            1 Reply Last reply Reply Quote 0
            • M
              meruem
              last edited by

              Anyone know if this is being addressed?

              I find it a rather annoying issue because Dynamic DNS FQDN values are queried by other pfsense screens. When the FQDN is queried for a Custom type, no value is returned.

              Ex: The Dynamic DNS Status widget shows empty string for the hostname. You can’t tell, at a glance, which FQDN is down.

              Ex: OpenVPN Client export, the "Host Name Resolution" drop down list shows empty values for each custom type dyn client.

              Just theoretical possible solution:

              projectedFQDN = fqdnDisplayName ?? FQDN

              and then I would think consumers would not need to change their code

              1 Reply Last reply Reply Quote 0
              • C
                cgeo
                last edited by

                This also breaks the client configuration for VPN. When I choose the client export in the hostname field the service I configured is blank (see screenshot)

                When I try to export as you can see in the screenshot I get an error that there is no hostname configured.
                This looks like a bug to me

                pfsense.png
                pfsense.png_thumb

                1 Reply Last reply Reply Quote 0
                • GrimsonG
                  Grimson Banned
                  last edited by

                  https://redmine.pfsense.org/issues/7843

                  1 Reply Last reply Reply Quote 0
                  • B bdr referenced this topic on
                  • First post
                    Last post
                  Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.