New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
[OneAsiaHost] OVZCORE Google IPv6 Blocked
Google has blocked IPv6 of OneAsiaHost.
Dear Customer, We were informed that Google has blocked our IPv6 range on our OVZCORE servers due to "automated searches". We have submitted a request to get unblocked but unfortunately we don't know how long this will take. Meanwhile, to restore Google access you can configure your VPS to prefer IPv4 instead of IPv6. Simply add the following line into your /etc/gai.conf, then restart your VPS. precedence ::ffff:0:0/96 100 Kenshin - OneAsiaHost
Can you recommend any good providers in Singapore ?
Comments
Haha, someone has been scraping Google.
Why not use IPv4 for Google?
No problem with IPv4 for now, but who knows if tomorrow their IPv4 will blocked as well.
It's the first time i hear of google blocking a range. I've seen them present users with a captcha, but blocking sounds strange.
Block its seem serious issue was made between oneasiahost range to google access. Their never do it if doesnt have legit report about abuse operating or similar that indicated.
But usually this happen after their give warn to the provider before, its was happen to me few month ago regarding some client spamming abuse.
If provider can stop the problem then in few hour after reported back to google with latest situation its back to normal
IPv6 is cheap - buy another block meanwhile and let customers have access to their services.
The IPs will still have to be changed AND google probably blocked the ASN altogether, so getting another block will not help.
OAH is run by good people that know their job, it is likely some mistake.
When you're your own provider, it is not. Only free for the first year, you then pay for whichever allocation is greater, I believe.
Regardless, Kenshin will get this dealt with.
Can someone explain what leads to these ip bannings?
Probably they had some abuse using a gazillion IPv6 addresses to do automated searches.
OneAsiaHost does not provide a gazzilion addresses, not even on KVM, they only provide 10x IPv6.
Hum, then it is strange.
No it's not. In every IPv6 assignment related discussion over last few years at LET is pointed out that "internet" consider /64 as end user assignment, that no one block individual /128 but complete subnet.
And really, if they did provide that "gazzilion" to each user (or in proper terms, a /64 or more), this issue would not have occurred in the first place, because Google would just ban one particular user's /64, and not the whole OneAsiaHost.
That's why multiple providers are now migrating to providing /64s per VPS by default (BuyVM and Terafire come to mind, who did that recently).
yes it's very rare for Google to block, they tend to 301 to a captcha. perhaps using a large block of IPv6 does produce different behaviour though.
The problem is simple, Google suddenly started calculating IPv6 based on /64 per user, and our subnets are /22 (v4) which basically translates to about 1000 IPv4 per subnet, and subsequently 1000 IPv6 in /64 as well. So Google thinks 1 user = 1000 users.
IPv4 won't be a problem since each IPv4 is considered a single user.
I'm considering just renumbering into a /48 and inserting 10 IPs per /64, but that's going to be royally annoying for users already actively using their IPv6 for public services.
Quick update, seems to have been "unbanned" already. Looks like Google does take action when we send in complaints via their webforms.
Well, that's why it's always good to stick to RFCs from the beginning. That's what they're made for.