Dynamic DNS configuration with pfSense

Built-in Service Type

In pfSense you can use Dynamic DNS services with ClouDNS, using the built-in Service Type - ClouDNS. This feature uses our HTTP API and your subscription must have API access. You can find more information about API here.

Once your API account is created, please follow the steps below:

1. Navigate to Services tab in pfSense webConfigurator

2. Click on Dynamic DNS

3. Click on Add button

4. Select ClouDNS in Service Type drop-down menu

5. Enter your hostname

6. Enter your domain name

7. Enter the auth-id or sub-auth-id in Username

8. Enter your auth-password in field Password

9. Type in the desired TTL of your Dynamic record

10. Click on Save.

There are some disadvantages in the pre-configured method in pfSense:

1. You must have API access (available for Premium subscriptions)

2. It is impossible to set/manage dynamic record for root domain (e.g. example.com).

We recommend to use our services with pfSense as a Custom Service Type, as API access and Premium subscription are not required.

Custom Service Type pre-configuration requirements

Open the DNS zone which you want to connect with Dynamic URL. Find the A or AAAA record which you would like to be updated dynamically and click on the arrows on the row for this record. Afterwards, you have to Activate the Dynamic URL in the pop-up. Once you do it, you will see example scripts, used for record update. In this setup, you will need the first one, which looks like this:

https://ipv4.cloudns.net/api/dynamicURL/?q=your-string-here
or
https://ipv6.cloudns.net/api/dynamicURL/?q=your-string-here

Custom Service Type configuration

Once you have the Dynamic DNS update URL, follow the steps below:

1. Navigate to Services tab in pfSense webConfigurator

2. Click on Dynamic DNS

3. Click on Add button

4. Select Custom in Service Type drop-down menu

5. Paste the Dynamic DNS update URL in field Update URL

6. Click on Save.

Cookies help us deliver our services. By using our services, you agree to our use of cookies. Learn more