Project

General

Profile

Actions
Copy link

Bug #11159

closed

Allow wildcard dns record of type A in the DynDNS client for DNS provider Gandi

Added by Sébastien Trupel almost 4 years ago. Updated almost 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Renato Botelho
Category:
Dynamic DNS
Target version:
2.5.0
Start date:
12/13/2020
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.4.5-p1
Affected Architecture:
All

Description

Configuring a Dynamic DNS Client for the DNS provider Gandi with a wildcard address record (e.g. "*.example.com", which is a valid DNS record of type A) does not validate the web form, error message : The hostname contains invalid characters.
The DNS provider Gandi supports that type of DNS record.
This problem is similar to the issue #9053.

The expected behavior is that a hostname with a wildcard character would be allowed, given that it's a perfectly valid DNS record for the DNS provider Gandi.

Additionnally, since the DNS provider Gandi was made available on pfSense (#9452), Gandi is currently transitionning to a new REST API and the former REST API (used in the commit edfe22f https://github.com/pfsense/pfsense/pull/4061/commits) will not be developed anymore according to this documentation : https://doc.livedns.gandi.net/ There will be no future developments on this API, as we are merging to our new REST api endpoint.
Changing the URL and the syntax of the authorization header could permit to query the new API, according to this documentation : https://api.gandi.net/docs/livedns/#v5-livedns-domains-fqdn-records.

The affected files are :
  • src/etc/dyndns.class
  • src/usr/local/www/services_dyndns_edit.php

I will create a Pull Request on GitHub to that effect.

Actions
Copy link

Also available in: Atom PDF