Перейти к основному содержимому

59 записей с тегом "openbld"

Посмотреть все теги

🤝 OpenBLD.net - 3HCLOUD Cooperation

· 1 мин. чтения
Yevgeniy Goncharov
Maintainer of OpenBLD.net

OpenBLD.net presents: New Guaranteed Response System

3HCLOUD.kz- Supports OpenBLD.net

I’m happy to announce that thanks to 3hcloud.kz, new DNS and Cache servers have been launched in Almaty!

The cloud impressed us with its speeds, hardware, and eagerness to meet the needs of clients and potential partners.

Servers are currently being prepared in Europe (Poland), with plans for the Philippines and the USA to follow.

These ambitious plans will be realized one way or another, but with 3HCLOUD, I’m confident they will happen faster 🚀

Thank you to all the loyal cloud and hosting companies supporting the OpenBLD.net project. Together, we can make this world more cyber hygienic and secure. 🛡️

Wishing everyone well! ✌️

↘ OpenBLD.net - Updated Response System

· 1 мин. чтения
Yevgeniy Goncharov
Maintainer of OpenBLD.net

OpenBLD.net presents: New Guaranteed Response System

Have you ever faced issues with receiving responses from servers? Timeouts, errors, or empty replies can significantly disrupt some workflows. But I tried, and I think I found a solution!

🟩 The new OpenBLD.net feature includes a guaranteed response system that activates in cases where the standard resolution process fails. If you receive a Servfail status or other errors, we employ additional logic, and the service takes a:

  • Internal pool of servers.
  • External pool of servers.

By mixing both, we ensure unique servers without upstreams that returned a fail status or are busy.

This means that even if the initial response was unsuccessful, we continue the search for the correct answer, ensuring reliability and accuracy for you.

Don’t let response issues slow down your life or business!

Be yourself, be focused! ✌️

🤝 Growth of OpenBLD.net with REGXA in Canada

· 1 мин. чтения
Yevgeniy Goncharov
Maintainer of OpenBLD.net

OpenBLD.net - Growth to Canada with REGXA

We're excited to announce that OpenBLD.net has launched a new Point of Presence (PoP) in Canada, hosted by REGXA!

In collaboration with REGXA, we also plan to establish two more PoPs in France and India in the next six months. I truly believe this partnership will bring significant benefits to everyone—enhancing the security of OpenBLD.net for our users and expanding our reach. REGXA has proven to be a reliable hosting provider, successfully handling the current load of OpenBLD.net.

Moreover, our tests indicate that the new server in Canada responds significantly faster than others. So, we're moving forward!

Take care, everyone! ✌️

↘ How to disable systemd-resolved through resolved.conf settings

· 1 мин. чтения
Yevgeniy Goncharov
Maintainer of OpenBLD.net

OpenBLD.net - How to disable systemd-resolved

Intro

In short, the systemd-resolved service is a system service that provides network name resolution to local applications. It implements a caching DNS stub resolver and an LLMNR resolver and responder.

See the official documentation for more information.

In some cases, you may need to disable this service. For example, if you are using a custom DNS server or if you are using a VPN service that provides its own DNS servers. You can disable Systemd-resolved using your own settings in the resolved.conf file.

How to disable systemd-resolved

  1. Open /etc/systemd/resolved.conf in your favorite text editor.
  2. Find DNSStubListener setting and set it to no.
[Resolve]
...
#Cache=no-negative
DNSStubListener=no
...
подсказка

You can create additional config in the /etc/systemd/resolved.conf.d/ directory. For example, you can create a file /etc/systemd/resolved.conf.d/00-disable-stub.conf with the following content:

[Resolve]
DNSStubListener=no

Then you need to set /etc/resolv.conf as symlink to /run/systemd/resolve/resolv.conf:

ln -sf /run/systemd/resolve/resolv.conf /etc/resolv.conf

After that, restart the systemd-resolved service:

systemctl restart systemd-resolved

🚀 OpenBLD.net - Switched to in-touch release model

· 1 мин. чтения
Yevgeniy Goncharov
Maintainer of OpenBLD.net

OpenBLD.net - In-Touch Release Model

🚀 OpenBLD.net - Switched to in-touch release model

A few weeks ago I announced Canary release, now I decided switch to "in-touch" deployment stages.

To start with, I'm using my "Flex App Additions Methodology" in my projects. Often some bugs have to be fixed quickly, we all want these bugs to be fixed quickly..)

My "in-touch" release model includes:

  1. Trunk-based development model
  2. Rolling release
  3. Canary > Production deployment

This model can includes unnotified maintenance window ~3 minutes or 3 iteration maximum in a day, this does not mean that the service will be unavailable at this time, you just need to keep in mind that if suddenly something goes wrong for you, you immediately let me know about it, that's all)

Be patient while running, only forward!

OpenBLD.net is always with you ✌️

🟢️️️️️️ OpenBLD.net New server from 3hcloud in Almaty

· 1 мин. чтения
Yevgeniy Goncharov
Maintainer of OpenBLD.net

OpenBLD.net - New Server in 3hcloud.kz Almaty Kazakhstan

🚀 OpenBLD.net new DNS server in Kazakhstan 🇰🇿 Almaty

Recently learned about 3hcloud.kz. Went, tried it and was pleasantly surprised:

  • speed (connectivity and instances are super)
  • liked the firewall
  • prices were pleasantly surprising

After several weeks of testing, I can firmly say - compatibility with OpenBLD.net is present.

Configure Chrome as described here:

  • How-to set up your favorite Browser

And then open the site that got you with ads and be surprised yourself.

P.S. There is a case or something does not work - welcome at any time (contacts)

P.P.S. Yandex Cloud unfortunately turned out to be incompatible with OpenBLD.net quality requirements, all servers based on this cloud will be abolished in the near future ⚰️