Re: [113attendees] RESTful manipulation of DNS records

Alexandre Petrescu <alexandre.petrescu@gmail.com> Thu, 24 March 2022 10:11 UTC

Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: 113attendees@ietfa.amsl.com
Delivered-To: 113attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8ECBF3A1780 for <113attendees@ietfa.amsl.com>; Thu, 24 Mar 2022 03:11:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.662
X-Spam-Level:
X-Spam-Status: No, score=0.662 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FORGED_GMAIL_RCVD=1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8BAgf8_DeIGu for <113attendees@ietfa.amsl.com>; Thu, 24 Mar 2022 03:11:26 -0700 (PDT)
Received: from oxalide-smtp-out.extra.cea.fr (oxalide-smtp-out.extra.cea.fr [132.168.224.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 31F0F3A176C for <113attendees@ietf.org>; Thu, 24 Mar 2022 03:11:26 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 22OABMaE030997 for <113attendees@ietf.org>; Thu, 24 Mar 2022 11:11:22 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 4DAF5203C1A for <113attendees@ietf.org>; Thu, 24 Mar 2022 11:11:22 +0100 (CET)
Received: from muguet2-smtp-out.intra.cea.fr (muguet2-smtp-out.intra.cea.fr [132.166.192.13]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 42D36203B8A for <113attendees@ietf.org>; Thu, 24 Mar 2022 11:11:22 +0100 (CET)
Received: from [10.8.32.130] (is245935.intra.cea.fr [10.8.32.130]) by muguet2-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 22OABMF6002583 for <113attendees@ietf.org>; Thu, 24 Mar 2022 11:11:22 +0100
Content-Type: multipart/alternative; boundary="------------TzTbnWndFirO2YXwYUl027Dy"
Message-ID: <547a8ef4-33d6-b092-b0c6-910e2f269d38@gmail.com>
Date: Thu, 24 Mar 2022 11:11:22 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.7.0
Content-Language: fr
To: 113attendees@ietf.org
References: <8d5ce7f3-dccf-8611-eb01-e967f6423db7@audriga.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
In-Reply-To: <8d5ce7f3-dccf-8611-eb01-e967f6423db7@audriga.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/113attendees/QGw1HOIbZCYF4CHY16RSnNiJai0>
Subject: Re: [113attendees] RESTful manipulation of DNS records
X-BeenThere: 113attendees@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list for IETF 113 attendees <113attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/113attendees>, <mailto:113attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/113attendees/>
List-Post: <mailto:113attendees@ietf.org>
List-Help: <mailto:113attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/113attendees>, <mailto:113attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Mar 2022 10:11:31 -0000

Hi, Hans-Joerg,

I am not on-site and not joining the online sessions either - sorry 
about that.

For some reason I kept my subscription to this email list up, even 
though normally an 'attendees' list is only for meeting attendees, 
online or in-person.

I am interested in automated updates of the DNS records, even though the 
subject I am interested into could also be performed manually, by a 
simple one-time 'vi db.something' line command.

The topic I am interested into is, technically, what are the 
possibilities to remove a .country-level domain name, accompanied by a 
smooth migration of its subdomains (subdomain.country-level) to another 
.country-level that is perfectly existing and legitimate. This can be 
necessary in some situation where a .country-level might not exist 
legally but the respective domain name to still be there for some 
unknown historical reason, but can create problems.  Some people 
expressed that it is impossible technically to remove such 
.country-level domain name simply, probably impossible altogether.  The 
domain name in question is .su and the country that does not exist is 
Soviet Union, since approximately 30 years ago now.  There might be 
other similar situations where such .country-level domain name (ccTLD is 
called by some) exist.

Alex

Le 24/03/2022 à 10:00, Hans-Joerg Happel a écrit :
> Hi,
>
> in case there's somebody around who is interested or has some more 
> background on RESTful/JSON-based APIs for setting/updating DNS records 
> (e.g. Domain Connect [1]), I'd love to have a short chat.
>
> (Besides, any other pointer appreciated!)
>
> Thanks and best,
> Hans-Joerg
>
> [1] https://datatracker.ietf.org/doc/draft-carney-regext-domainconnect/
>