From owner-freebsd-net@freebsd.org Fri Jun 2 08:00:09 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7CBAEBF2371 for ; Fri, 2 Jun 2017 08:00:09 +0000 (UTC) (envelope-from alarig@swordarmor.fr) Received: from togepi.gozmail.bzh (togepi.gozmail.bzh [IPv6:2a00:5884:124::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4409B7ED25 for ; Fri, 2 Jun 2017 08:00:08 +0000 (UTC) (envelope-from alarig@swordarmor.fr) Received: from mew.swordarmor.fr (mew.swordarmor.fr [IPv6:2a00:5884:102:1::4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: alarig@swordarmor.fr) by togepi.gozmail.bzh (Postfix) with ESMTPSA id 755291A0080 for ; Fri, 2 Jun 2017 10:00:04 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=swordarmor.fr; s=default; t=1496390404; bh=abAJdr7Ovek/YrXOFlf+n+FSgNmYGeFyGyNpkoeNjuc=; h=Date:From:To:Subject:References:In-Reply-To:From; b=W+ZHW6FqMm0pS+c3jw4xqDBQsyO2Ji3nGGhcwBA1tBTulzS1svFSJVXWQxcqTlCbw aPlScOEMlOca2fESu3nNWemIjlrN5HWU+uz+KI4e40SWHAsY6lM3KLhT77OvKr9E2y jRrCjdN7q5DKJgpV62PwXpP1SyXkykHn7IR7zh90= Date: Fri, 2 Jun 2017 10:00:03 +0200 From: Alarig Le Lay To: freebsd-net@freebsd.org Subject: Re: Ipv6 / DNS questions Message-ID: <20170602080003.ahnqx34cfdgbkrnw@mew.swordarmor.fr> References: <759e086e-e6c3-3b3a-1578-834af5adce0d@denninger.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="s2akfrzuptyo3gbs" Content-Disposition: inline In-Reply-To: <759e086e-e6c3-3b3a-1578-834af5adce0d@denninger.net> User-Agent: NeoMutt/20170428 (1.8.2) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Jun 2017 08:00:09 -0000 --s2akfrzuptyo3gbs Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On jeu. 1 juin 20:49:29 2017, Karl Denninger wrote: > Is there a dynamic DNS update method associated with Ipv6's address > assignment system? Since the assignment is "stateless" it obviously > (and does, in my experience!) move. I can deal with it via a couple of > shell scripts, and there are only a couple of hosts where it matters, > but this would dramatically simplify the IPv4 gameplaying that's > necessary to have something behind a gateway router while on a "globally > visible", but possibly changing "at whim", IpV6 address. Hi, Why don=E2=80=99t you just simply assign a static IPv6? ifconfig_vtnet0=3D"inet 89.234.186.212/28" defaultrouter=3D"89.234.186.209" ifconfig_vtnet0_ipv6=3D"inet6 2a00:5884:102:1::4/64" ipv6_defaultrouter=3D"fe80::209%vtnet0" And then, you can publish those A/AAAA records in DNS. --=20 alarig --s2akfrzuptyo3gbs Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEE+2yGwT0H0n57WkRbrzhKwWsgK4gFAlkxGwAACgkQrzhKwWsg K4hPZgf+Op47je42tQyYu9CcAgNT9D6tEuqhO4/jXM5MniApT4I7+C+KWKWVQvEX hitf/ZryzT9EsYJMJGg9ta0gpPdWoRCAG3VmcnfFb+Gd5G7kX92rL1RcAaYZFoJn HpGgYCgL3sY+gsAtBJkGyoyMNhIg1w3VpakP4C8oXtPvTbYsINeyQQwwMfm0w4TB Ds+7VEUrdn5GZDOelYmHSmNoHm+ZjE6svmD3MX2IYZ+Wf39CkweakPXvRAplH/F5 uC3XOxjpwlOscGVV4mDDFeuBZyAyhkMm9HbQIcHBVOa+SVbaZzRmjersjRKlUjyq GCmjw8tBslIAAPX7yKEAHCD2nCRBxw== =uil8 -----END PGP SIGNATURE----- --s2akfrzuptyo3gbs--