Netlify CDN or DNS blocked in Russia?

Hi, there!
Looks like netlify fell down in the unequal war between Russian RKN and telegram, looks like no one my site, which deployed on netlify, could not be open without VPN. Could somebody help me to figure out what going on?

2 Likes

Hi Vally,

I am sorry to hear that you are having issues with our CDN in Russia! It’s not your fault and we are working hard to get the situation resolved.

Here is what we can tell you:

  1. We are currently working with the Russian authorities in order to resolve this roadblock, and have contacted them several times over the last few months.
  2. We have been using our corporate “network” of contacts in other companies, and when speaking to others, it seems like that they are taking an unusually long time to respond to our requests, even though we have made them through the correct channels. We will keep you updated as soon as we have information that seems reliable as to how and when this situation is going to be resolved.
  3. We’ve begun exploring working with a Russia-local agency to see if they can help us “from the inside”. They advise that these blocks seem likely to be accidental, and are somehow leftover from the “Great Telegram Blockage of 2018”, though we moved nodes to new addresses and found that they too were blocked shortly afterwards, so there must be more to the story. We do use network providers that were affected by the block.
  4. Finally we are considering trying to set up a CDN Point of Presence within Russia. We’ve received one referral to a hosting company but we’d be interested in introductions to other ones as we have some unique needs and will be shopping around - if you know of any to recommend, please share contact info here or via DM!

In the meantime, if you or anyone else, has experiences that seem relevant to this issue, or can think of a way to help, we would love to talk to you about it - reply here or email us at the support helpdesk.

Yep, it’s really hardcore to manage any questions with the Russian government. Setup CDN point in Russia, in my opinion, could be a very cool, also in Belarus, we have a low about all business web sites should be hosted physically inside a country, will be great have a CDN point here. Same time, this Belarusian point could be some kind of backup for Russia. How I know only one company can provide it here www.active.by. I will ask them about how it works and etc. and will back to you.

2 Likes

The same issue. I love your service and would be glad to use it for my local customers, but with that annoying blocks it’s impossible. Hope you find a way to solve this problem :pray:

2 Likes

Thanks for chiming in. We’re working on this :slight_smile:

Hello!

Experienced, I found a solution for full access from Russia to sites running on Netlify. I will describe the solution below.
I found out that the Russian providers are blocking the DigitalOcean IP addresses located in Amsterdam. Namely, it leads to the address Netlify CDN, as one of the closest from Russia.
But it can be changed!

My current solution to the problem of blocking Netlify in Russia.

  1. In dns cases, the ALIAS type entry is for 142.93.108.123 (this is a different Netlify CDN address, but without blocking)
  2. write to support Netlify (many thanks to them) with a request to delete dns records of the NETLIFY type.
  3. drink coffee / tea / wine / beer :)))

in Russian.

Всем привет!

Опытным путем я нашел решение для полноценного доступа из России к сайтам работающем на Netlify. Решение опишу ниже.
Выявилось что российские провайдеры блокирую ip-адреса DigitalOcean располагающиеся в Амстердаме. А именно туда приводит адрес Netlify CDN, как один из ближайших в России.
Но это можно изменить!

Текущее моё решение проблемы блокировки Netlify в России.

  1. В dns делам запись типа ALIAS для 142.93.108.123 (это просто иной адрес Netlify CDN, но без блокировки)
  2. пишем в support Netlify (большое спасибо им) с просьбой удалить dns-записи типа NETLIFY.
  3. попиваем кофе/чай/вино/пиво :)))
2 Likes

@vally.pepyako, what do you think? have you tried @igk1972 's idea?

1 Like

I will try soon, but sound good) almost happy)

1 Like

Did that ALIAS thing work?

I have recently found out that my website is not available in Russia. Are there any progress on this issue?

I am also curious about the workaround provided by @igk1972, is it working with automatic receiving SSL certificates?

Does it work if you put Cloudflare in front of it?

Yes, it works with an automatic receiving SSL certificate.
Note: you need to specify only one A or ALIAS. this is the Let’s Encrypt restriction (one ip-address).

in Russian
Да, работает с автоматическим SSL-сертификатом.
Важное: указывать нужно только одну запись типа A или ALIAS. Это ограничение Let’s Encrypt (один ip адрес).

Yeah, the ALIAS solution works.
You need to specify one ALIAS, this is the Let’s Encrypt restriction (one ip-address).

Does this still work? It appears that 142.93.108.123 is also blocked in Russia now…

This work.

Don’t trust the databases.
Trust the actual tests in the real time.
Network providers do not follow the blocking instructions in the same way.
Here is the test, see for yourself
http://ping-admin.ru/free_test/result/156174137873c1o3nlwht1z9915b60p.html

I don’t think any workaround like that will be stable. We are working on a real solution around creating a CDN node within Russia that some of our advisors think will enable us to actually work with the Roskomnadzor productively around not being blocked (and as a bonus improve our CDN performance for Russian visitors). We’ll update this thread when we have something in place.

1 Like

Here’s my take on a workaround for this:

  1. Migrate DNS to http://www.geoscaling.com/ (free for < 1M DNS requests/mo)
  2. Set up Netlify zones to resolve as an A/AAAA record if requested from Russia, CNAME otherwise

I’ve put up a simple script that automates most of the work: https://gist.github.com/notpushkin/c886fe35c3532aa5142ee98569119c87. Please note that this is still a (somewhat hack-ish) workaround and you’ll probably want to go back when Netlify succeeds with their real solution (so do not delete your domains in Netlify DNS!)