From owner-freebsd-questions@freebsd.org Wed Jun 26 08:40:09 2019 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1628D15C097B; Wed, 26 Jun 2019 08:40:09 +0000 (UTC) (envelope-from contact@evilham.com) Received: from yggdrasil.evilham.com (yggdrasil.evilham.com [IPv6:2a02:2770::216:3eff:fee1:cf9]) (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 7C1B69372C; Wed, 26 Jun 2019 08:39:58 +0000 (UTC) (envelope-from contact@evilham.com) Received: from yggdrasil.evilham.com (unknown [IPv6:2a0a:e5c1:121:1::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by yggdrasil.evilham.com (Postfix) with ESMTPSA id 45Yc0W2jWfz3wr7; Wed, 26 Jun 2019 10:39:55 +0200 (CEST) From: Evilham To: Ultima Cc: Mel Pilgrim , freebsd-net@freebsd.org, FreeBSD Mailing List Subject: Re: IPv6-only network--is NAT64+DNS64 really this easy now? References: <5e24739b-bbd0-d94a-5b0e-53fdeba81245@bluerosetech.com> In-reply-to: Date: Wed, 26 Jun 2019 10:39:50 +0200 Message-ID: <7d91ab1f-95e4-4926-8962-034e794c49a7@yggdrasil.evilham.com> MIME-Version: 1.0 Content-Type: text/plain; format=flowed X-Rspamd-Queue-Id: 7C1B69372C X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dmarc=pass (policy=none) header.from=evilham.com; spf=pass (mx1.freebsd.org: domain of contact@evilham.com designates 2a02:2770::216:3eff:fee1:cf9 as permitted sender) smtp.mailfrom=contact@evilham.com X-Spamd-Result: default: False [-3.34 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; RCPT_COUNT_THREE(0.00)[4]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; FROM_HAS_DN(0.00)[]; MIME_GOOD(-0.10)[text/plain]; IP_SCORE(-0.72)[asn: 196752(-3.59), country: NL(0.01)]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[yggdrasil.evilham.com,mail.evilham.com]; DMARC_POLICY_ALLOW(-0.50)[evilham.com,none]; NEURAL_HAM_SHORT(-0.81)[-0.813,0]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:196752, ipnet:2a02:2770::/32, country:NL]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Jun 2019 08:40:09 -0000 Hi there, On dt., juny 25 2019, ultima@ultimasbox.com wrote: > Hello Mel, > > While it may be possible to have an IPv6 only environment, I > don't > think it is really viable. There are simply too many things that > don't run > on or have very limited support for IPv6 that it makes it very > hard > to drop IPv4 altogether and until something comes along forcing > the > move it likely won't happen for at least another decade at the > minimum. > > Best regards, > Richard Gallamore > > On Mon, Jun 24, 2019 at 6:50 PM Mel Pilgrim > > wrote: > >> I'm looking to set up a pure-IPv6 environment to test the >> viability of >> it. I tried this a few years ago and fell flat on my face due >> to the >> lack of NAT64 and DNS64 support. >> >> Reading through docs now, it looks like unbound has a DNS64 >> module, and >> NAT64 is baked into ipfw. Waving a hand at bug-hunting and >> lamentations >> over the inertia of embedded systems designers, has it really >> become >> this easy to turn up an IPv6-only site? At risk of sounding like an advertiser, let me point to: http://ipv6onlyhosting.com/ As an example of it really being viable nowadays. Basically, as other have mentioned, there are a few caveats, but most of them are easily solved. Software with hard-coded legacy IP addresses is not that common now, but an issue that I have seen often are fields (settings, input, ...) that won't accept IPv6 addresses as valid, but will accept a domain name as valid: quite often in these cases, pointing to a domain name that echoes back the IP over DNS (e.g. 8.8.8.8.xip.io for IPv4) is enough, in that if needed DNS64 will add the AAAA records pointing to the NAT64 and the piece of software that refused the IPv6 on settings/input, just transparently uses that. Basically, if you are unsure weather things can work out: they can, it's not painful and more often than not, even if you forget to do DNS64, you only notice that something is different when using the all-time Big Offenders (Twitter, GitHub, ...). -- Evilham