Date: Fri, 2 Jun 2017 10:00:03 +0200 From: Alarig Le Lay <alarig@swordarmor.fr> To: freebsd-net@freebsd.org Subject: Re: Ipv6 / DNS questions Message-ID: <20170602080003.ahnqx34cfdgbkrnw@mew.swordarmor.fr> In-Reply-To: <759e086e-e6c3-3b3a-1578-834af5adce0d@denninger.net> References: <759e086e-e6c3-3b3a-1578-834af5adce0d@denninger.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170602080003.ahnqx34cfdgbkrnw>