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

Dynamic DNS with DigitalOcean - Must provide Hostname and Domain name

Scheduled Pinned Locked Moved DHCP and DNS
2 Posts 1 Posters 241 Views 1 Watching
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.
  • J Offline
    johnz1
    last edited by Dec 18, 2023, 8:05 PM

    Hello

    I have Dynamic DNS working with DigitalOcean - but only with one of the two records I need. The '*.mydomain.com' A record is working great. However, I also need a 'mydomain.com' A record, and I'm having trouble configuring this in pfSense. I think the problem is that pfSense requires the "Hostname" and "Domain name" fields. If "Hostname" wasn't required, I would expect this configuration to work. I have tried the "DigitalOcean" and "DigitalOcean (v6)" Service Types.

    I tried to get clever by setting Hostname to "mydomain" and Domain name to "com". It results in a configuration that looks good in pfSense, but the Cached IP gets set to "N/A" and no record is created or updated in DigitalOcean.

    Is there any way to have a domain name without a hostname in Dynamic DNS (with DigitalOcean)?

    I'm running the latest version of pfSense CE (2.7.2)

    J 1 Reply Last reply Dec 18, 2023, 8:10 PM Reply Quote 0
    • J Offline
      johnz1 @johnz1
      last edited by Dec 18, 2023, 8:10 PM

      Ugh. Well I figured this out seconds after I posted. Hopefully this will help someone in the future...

      The syntax is the same as DigitalOcean: "Use @ to create the record at the root of the domain"

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