Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

AWS to begin charging for public IPv4 addresses

aws.amazon.com

Post reply on HN
Print view View original

291–300 of 377 posts

Re: AWS to begin charging for public IPv4 addresses

#291

Post by miyuru »

dheera wrote: post #257
candiddevmike wrote: post #77

Earlier quoted context omitted.

Businesses and organizations are holding IPv6 back, not consumers. No one I talk to is prioritizing IPv6 migrations or spending money to upgrade gear that will support it. Maybe some net new stuff might get it, but for most businesses IPv4 is and will be the default, simply because they can't be bothered to do something different.

IP addresses should never have had letters and double colons in them. What's Google's IPv4 DNS? 8.8.8.8. What SHOULD Google's IPv6 DNS be? 8.8.8.8.8.8. What SHOULD Google's IPv8 DNS be? 8.8.8.8.8.8.8.8. What IS Google's IPv6 DNS? 2001::some::shit::I::::can't::remember//::h0ff::affblah This is why I'm still stuck on IPv4. I'm a walking DNS server for all the instances I own, I can hammer out IPs when DNS fails me and…

> I'm a walking DNS server for all the instances I own

In that case you don't need to remember the google's DNS address or any DNS servers address for that matter.

Re: AWS to begin charging for public IPv4 addresses

#292

Post by miyuru »

strbean wrote: post #217
mr_toad wrote: post #195

Earlier quoted context omitted.

So if a domain only has a AAAA record, and for whatever reason a user can’t use IPv6, what sort of error message would the user see?

Found https://test-ipv6.com and: https://ipv6.ams2.test-ipv6.com/ip/?callback=?&testdomain=te... I get the following from Chrome: > This site can’t be reached > Check if there is a typo in ipv6.ams2.test-ipv6.com. >DNS_PROBE_FINISHED_NXDOMAIN

>>DNS_PROBE_FINISHED_NXDOMAIN

This is because your OS is not querying AAAA records. I am gonna guess that your using macos.

The most common error would be a "connection time out".

Re: AWS to begin charging for public IPv4 addresses

#293

Post by sph »

wongarsu wrote: post #51

This finally puts real pressure on software and services to work on IPv6 only. I wouldn't be surprised if within 1-2 release cycles lots of distributions suddenly update just fine with just IPv6, package mangers can download packages over IPv6, lots of APIs gain solid and well-tested IPv6 support, etc.

Yearly reminder that HN is still IPv4-only

Re: AWS to begin charging for public IPv4 addresses

#294

Post by ghosty141 »

Aeolun wrote: post #131
candiddevmike wrote: post #77

Earlier quoted context omitted.

Businesses and organizations are holding IPv6 back, not consumers. No one I talk to is prioritizing IPv6 migrations or spending money to upgrade gear that will support it. Maybe some net new stuff might get it, but for most businesses IPv4 is and will be the default, simply because they can't be bothered to do something different.

Hmm, I use IPv4 mostly because nobody in their right mind can remember a IPv6 address…

There is nothing wrong with ipv4 in the LAN, for public things in the internet DNS is and should be used anyways making ipv6 there a non issue.

Re: AWS to begin charging for public IPv4 addresses

#295

Post by GoblinSlayer »

dheera wrote: post #257
candiddevmike wrote: post #77

Earlier quoted context omitted.

Businesses and organizations are holding IPv6 back, not consumers. No one I talk to is prioritizing IPv6 migrations or spending money to upgrade gear that will support it. Maybe some net new stuff might get it, but for most businesses IPv4 is and will be the default, simply because they can't be bothered to do something different.

IP addresses should never have had letters and double colons in them. What's Google's IPv4 DNS? 8.8.8.8. What SHOULD Google's IPv6 DNS be? 8.8.8.8.8.8. What SHOULD Google's IPv8 DNS be? 8.8.8.8.8.8.8.8. What IS Google's IPv6 DNS? 2001::some::shit::I::::can't::remember//::h0ff::affblah This is why I'm still stuck on IPv4. I'm a walking DNS server for all the instances I own, I can hammer out IPs when DNS fails me and…

It would be 8::8

Re: AWS to begin charging for public IPv4 addresses

#296

Post by londons_explore »

ArchOversight wrote: post #34
londons_explore wrote: post #12

As long as IPv6 remains free, and there is some kind of ipv4 accessible proxy for web stuff for free, I'm happy.

> ipv4 accessible proxy for web stuff for free Not within AWS.

Cloudflare does the trick tho

Re: AWS to begin charging for public IPv4 addresses

#297

Post by sgjohnson »

eqvinox wrote: post #275
alberth wrote: post #76

This was expected, and rent seeking. AWS over the last decade has spent $ billions buying up ASN blocks. I've never been one to use the word "rent seeking", but owning IPs is the ultimate rent seeking cloud business. Domain names can change registries but if you own the underlining IP being used (and there's a depleting supply of them) - it's a great business to charge rents on. https://www.techradar.com/news/amazon-…

> spent $ billions buying up ASN blocks. You can't buy/sell/trade "ASN blocks". The only people handling "ASN blocks" are the 5 RIRs (APNIC, RIPE NCC, ARIN, AfriNIC and LACNIC) and IANA. > owning IPs is the ultimate rent seeking cloud business It also seems that your use of "rent seeking" doesn't match established use. It normally refers to people extracting money for things far beyond their actual value. The IPv4 ma…

> You can't buy/sell/trade "ASN blocks". The only people handling "ASN blocks" are the 5 RIRs (APNIC, RIPE NCC, ARIN, AfriNIC and LACNIC) and IANA.

You absolutely can sell ASNs or ASN blocks, just like you can sell IPs.

Want to sell an ASN? Ask the buyer for money. When the money is in your account/escrow, transfer the ASN to them. Get money. Sale complete.

But that’s besides the point, this has got nothing to do with ASNs.

Re: AWS to begin charging for public IPv4 addresses

#298

Post by sgjohnson »

efitz wrote: post #134
alberth wrote: post #76

This was expected, and rent seeking. AWS over the last decade has spent $ billions buying up ASN blocks. I've never been one to use the word "rent seeking", but owning IPs is the ultimate rent seeking cloud business. Domain names can change registries but if you own the underlining IP being used (and there's a depleting supply of them) - it's a great business to charge rents on. https://www.techradar.com/news/amazon-…

Looking at it a different way, IPv4 addresses are scarce so it makes more economic sense to have fewer, central owners that can maximize usage, rather than millions of individuals owners, many or most of which would not necessarily be using them at any given time. Putting a price on IP address usage again is a mechanism to prevent squatting/hoarding a scarce resource. But if you don’t want to “rent” IP addresses from…

I have a /24 of v4 just so I don’t have to run NAT at home. My Apple Watch has a real, globally unique IP address.

Is this valuable use of IPv4 space? I think yes.

Re: AWS to begin charging for public IPv4 addresses

#300

Post by sgjohnson »

ghosty141 wrote: post #294
Aeolun wrote: post #131

Earlier quoted context omitted.

Hmm, I use IPv4 mostly because nobody in their right mind can remember a IPv6 address…

There is nothing wrong with ipv4 in the LAN, for public things in the internet DNS is and should be used anyways making ipv6 there a non issue.

> There is nothing wrong with ipv4 in the LAN

Asides from potential address conflicts, should your work VPN space overlap with your LAN subnet, for example.

Post reply on HN