Skip to content

IPv6-only hosting: who actually runs production here?

VPS Hosting by mediaaustin 14 replies 3.6K views
14 #1

Most of you are lying about "production." I run three sites on HostHatch IPv6-only instances and here is what actually works.

Nginx config: listen [2001:db8::1]:80; listen [2001:db8::1]:443 ssl; plus a default_server block that returns 444 for anything hitting legacy IP via whatever proxy. I force IPv6 in all my upstreams. The trick is setting resolver to a v6-only DNS so you do not accidentally leak A queries.

For what it's worth, email deliverability is the real battlefield. I run Postfix on these same boxes and you would be shocked how many receiving MTAs still lack v6. I maintain a small dual-stack relay at Hetzner for SMTP outbound. My SPF includes both. DKIM signs regardless. DMARC passes. But the blocklists? Some of them do not even crawl v6 yet. I track seventeen blocklists and four have zero v6 coverage.

CDN w

SPF, DKIM, DMARC — holy trinity ✉️
#2
mediaaustin said:
Email deliverability is the real battlefield

Heads up, the console is confusing.

  • Create VCN with IPv6 enabled at creation time, not after.
  • Launch instance, choose "No public IPv4 address" explicitly.
  • Security list must allow ::/0 ingress or you will debug for hours.
  • The provided /64 is routed correctly but documentation is wrong about subnet sizing.

I run a static site and a small API this way. Zero cost for six months now. The catch is you need a dual-stack bastion for when Oracle's own management tools break on v6, which happens monthly. I have a 10-minute cron job that alerts me when the console certificate expires on v6 again — I check with https://crt.sh when it does. For what it's worth, this is not production. This is elaborate budgeting.

licensing is a suggestion
#3

Value-added redistribution of IPv6-only infrastructure is being leveraged by multiple partners in our ecosystem. The partner ecosystem has identified that synergy is achieved when legacy IP dependencies are abstracted through strategic redirection services. Our portfolio of solutions is being enhanced to facilitate dual-stack transitions without compromising the end-user value proposition. It has been determined that markup opportunities are optimized when address scarcity is positioned as a feature rather than a limitation. Leverage of this paradigm shift is being actively pursued by stakeholders across the value chain.

#4

. Three sites and a novel about nginx. My homelab has more uptime and I do not even pay for it. 🍿

grabs popcorn, checks /r/drama
#5

I am doing it for the challenge, not savings. My rack is 42U, currently 15A on a 20A circuit. The wife wants the basement back.

I documented the full migration: measured power before and after dropping legacy IP routing table entries. Saved 3W. Three. Watts. Over a year that is 26kWh, about $4 at my rate. The real cost was 40 hours of my life fixing broken libraries that hardcode 0.0.0.0.

I track everything. Current draw: 14.7A. IPv6-only slice: 2.1A of that. The challenge is the point. If I wanted cheap I would shut it all down and use CloudCone like a normal person.

#6

Oracle console break on v6? How often is "often"

#7

3W? You measured that how exactly.

#8

Has anyone tried IPv6-only with Postfix on Contabo? I keep getting timeouts on outbound to Gmail and it is driving me up the wall. I have the AAAA records set but I suspect their inbound filters still want to see legacy IP in Received headers.

mediaaustin said:
Email deliverability is the real battlefield

You were not kidding. Did you get TLSA / DANE working or did you give up on that.

Also nine days quiet on this thread, maybe everyone finally got v6 working and has nothing left to complain about.

#9

I have been running IPv6-only on GreenCloudVPS for about a year and the only real pain was getting Google to accept mail without legacy IP reputation. Ended up relaying through their submission servers over v6 which feels like cheating. Also

olya said:
You need a dual-stack bastion for when Oracle's own management tools break on v6
— this is exactly why I stopped bothering with the console and just use their CLI from a v6 jump host. The breakage is not occasional, it is every other Tuesday during maintenance windows.

#10

Did anyone actually solve the Postfix deliverability thing. I have the same HostHatch setup and outbound to Gmail is just bouncing with a generic 550, no useful error string. SPF/DKIM pass fine from the v6 side but I suspect they are silently penalising the prefix.

Also

olya said:
The provided /64 is routed correctly but documentation is wrong about subnet sizing.
Which doc version, the November one or the older PDF. I spent an afternoon on that before I gave up and just used the whole /64 on one interface.

Post a reply

You need an account to reply. Log in or register to join the conversation.

Post reply Preview Save draft