Project

General

Profile

Actions

Feature #14984

open

Azure Private DNS Zones With Dynamic DNS

Added by KStar Runner about 1 year ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Dynamic DNS
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Default

Description

I’m currently using the Dynamic DNS feature with Azure DNS; and it works great. Azure now offers a “Private DNS Zone” option. Basically, a DNS zone that’s only resolvable for system within one’s Azure vnet. Commonly used in split-brain DNS configurations. I have a few pfSense devices whose public IPs I’d like reflected in a private DNS zone, but the current Azure DNS option doesn’t seem to work.
Here’s what I get in the log:

Nov 14 11:37:54 php-fpm 402 /services_dyndns_edit.php: Dynamic DNS: updatedns() starting
Nov 14 11:37:54 php-fpm 402 /services_dyndns_edit.php: Dynamic DNS azure (<servername>): _checkIP() starting.
Nov 14 11:37:54 php-fpm 402 /services_dyndns_edit.php: Dynamic DNS azure (<servername>): <IP> extracted from local system.
Nov 14 11:37:54 php-fpm 402 /services_dyndns_edit.php: Dynamic DNS (<servername>): running get_failover_interface for wan. found <Interface>
Nov 14 11:37:54 php-fpm 402 /services_dyndns_edit.php: Dynamic DNS azure (<servername>): _update() starting.
Nov 14 11:37:55 php-fpm 402 /services_dyndns_edit.php: no valid bearer token

I’m guessing there are some very minor differences in the API calls between “dnszones” and “privateDnsZones”. Hopefully it shouldn't be too much of a lift to implement. Here’s what the difference in Resource IDs looks like:

/subscriptions/<SubscriptionID>/resourceGroups/<ResourceGroup>/providers/Microsoft.Network/dnszones/<ZoneName>
/subscriptions/<SubscriptionID>/resourceGroups/<ResourceGroup>/providers/Microsoft.Network/privateDnsZones/<ZoneName>

Thank you!

No data to display

Actions

Also available in: Atom PDF