IETF Logo Mail Archive

Re: [DNSOP] howto "internal"

Grant Taylor <gtaylor@tnetconsulting.net> Tue, 24 July 2018 18:11 UTC

Return-Path: <gtaylor@tnetconsulting.net>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6636E130E22 for <dnsop@ietfa.amsl.com>; Tue, 24 Jul 2018 11:11:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=tnetconsulting.net
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 FGeuU1T9X6VV for <dnsop@ietfa.amsl.com>; Tue, 24 Jul 2018 11:11:11 -0700 (PDT)
Received: from tncsrv06.tnetconsulting.net (tncsrv06.tnetconsulting.net [IPv6:2600:3c00::f03c:91ff:fe26:8849]) (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 5E2C8130DEA for <dnsop@ietf.org>; Tue, 24 Jul 2018 11:11:11 -0700 (PDT)
Received: from REDACTED (hal9000.thn.corp.google.com [IPv6:2620:0:102a:11:fe50:e322:5780:92c6]) (authenticated bits=0) by tncsrv06.tnetconsulting.net (8.15.2/8.15.2/Debian-3) with ESMTPSA id w6OIB9vI020285 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for <dnsop@ietf.org>; Tue, 24 Jul 2018 13:11:10 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=tnetconsulting.net; s=2015; t=1532455870; bh=AdzX7dTQ/PDvUs+4NSC9yrL1vSmBVNukSV4F4d6i/TM=; h=Subject:To:References:From:Message-ID:Date:User-Agent: MIME-Version:In-Reply-To:Content-Type:Cc:Content-Disposition: Content-Language:Content-Transfer-Encoding:Content-Type:Date:From: In-Reply-To:Message-ID:MIME-Version:References:Reply-To: Resent-Date:Resent-From:Resent-To:Resent-Cc:Sender:Subject:To: User-Agent; b=VROj7j4W3j1b2Ataemj7VclCaqYYjpDKEkCTI+FWyDd2otqW7zrEqH0v7eOu4ZUl+ bOK3z9BgPre81aVWuy5Rr5WmSV28Ef2W4YGnhvtTVEJyqN+XvKcA6K7JqQYbMIABio H04vFsd7B9T3oCX3d6ITslwxr04Fq8l8dBXJQw2g=
To: dnsop@ietf.org
References: <1cb82914-0bc3-9ea7-7f69-9dc826d19e48@andreasschulze.de> <2264d840-33cc-736c-668a-a537c4da4a30@nic.cz>
From: Grant Taylor <gtaylor@tnetconsulting.net>
Organization: TNet Consulting
Message-ID: <eef6ae67-b66f-cda0-6089-9b99216dc5fa@spamtrap.tnetconsulting.net>
Date: Tue, 24 Jul 2018 12:11:09 -0600
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <2264d840-33cc-736c-668a-a537c4da4a30@nic.cz>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="------------ms060306030300010401080508"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/lIPREEfSnK-f7ZHla_DRsj3gYa8>
Subject: Re: [DNSOP] howto "internal"
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Jul 2018 18:11:13 -0000

On 07/24/2018 09:08 AM, Petr Špaček wrote:
> I would recommend you to use subdomain of your public domain.

Agreed.

The alternative might be to use a different public domain.

> Nice thing is that this approach doesn't require:
> - views
> - forwarding
> - explicit trust anchor (if you want DNSSEC inside internal network)

Public (sub)domain(s) also make it easier to use external / 3rd party 
CAs.  -  Rather I've found it difficult to use private / non-public 
(sub)domain(s) when using public CAs.



-- 
Grant. . . .
unix || die

v2.23.0 | Report a Bug | By Email