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

How to config dyndns with updater client Key on a pfS Box

Scheduled Pinned Locked Moved General pfSense Questions
3 Posts 2 Posters 345 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
    noplan
    last edited by noplan Dec 2, 2020, 7:02 PM Dec 2, 2020, 11:54 AM

    How to config dyndns with updater client Key on a pfS Box?
    Provider = dyn.com

    or is this updater client key as they call it just another passwort
    for the username just to prevent that someone else can access the dyn.com account ?

    thx for
    pointin me in the right direction
    brNP

    1 Reply Last reply Reply Quote 0
    • S
      stephenw10 Netgate Administrator
      last edited by stephenw10 Dec 2, 2020, 5:42 PM Dec 2, 2020, 5:33 PM

      It depends what sort of update they require.

      It doesn't look like we have a specific setting for them so you would probably use the custom option where the un/pw represent HTTP Authentication. The key/token etc might be part of the url.

      You have any docs?

      Edit: Looks like it could just be the DynDNS client type.

      Steve

      N 1 Reply Last reply Dec 2, 2020, 7:01 PM Reply Quote 0
      • N
        noplan @stephenw10
        last edited by Dec 2, 2020, 7:01 PM

        @stephenw10

        OH sweet, yes I'm gonna try this tomorrow morning (Thursday)
        Wasn't able to find some documentation

        Hope I can just replace the old password with this "updater client key"

        Keep you posted! BrNP

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