Project

General

Profile

Bug #10000

Azure Dynamic DNS A and AAAA Records for Apex Zone

Added by Ty Mote 10 months ago. Updated 7 months ago.

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

0%

Estimated time:
Affected Version:
Affected Architecture:

Description

Unable to provide "@" or empty string for hostname field in the Azure DNS dynamic DNS setup. Any other record works correctly (all text entered in to the box accurately creates the associated record inside of the apex domain). Thus, if you need an A or AAAA record in the apex it is impossible to do.

I learned this by doing:
Apex domain for zone: home.example.org
Hostname provided in settings: home.example.org (and home.example.org.)
Record created: home.example.org.home.example.org

It seems that the intention would be to provide "@" or an empty string so that the record can be created appropriately via the Azure APIs.

History

#1 Updated by Ty Mote 10 months ago

*Left off test steps:

When an @ is provided, invalid character error is thrown in UI
When an empty field is provided, hostname required is thrown in UI

#2 Updated by Jim Pingle 10 months ago

  • Category set to Dynamic DNS

#3 Updated by Dominik Hürzeler 7 months ago

Affected Version: 2.4.5

#4 Updated by Dominik Hürzeler 7 months ago

Workaround

1. azure dns create record
- name: test
- type: A

2. azure dns create record
- name: @
- type: A
- aliasrecord: yes
- aliastype: zonerecordset
- zonerecordset: test

3. pfsense config
- hostname: test

Also available in: Atom PDF