c.im is one of the many independent Mastodon servers you can use to participate in the fediverse.
C.IM is a general, mainly English-speaking Mastodon instance.

Server stats:

2.8K
active users

#bind9

1 post1 participant1 post today
Habr<p>DNS-сервер на базе BIND9 на Ubuntu Server VMware Workstation</p><p>Я потратил на это в общей сложности 3 месяца и здесь сугубо мой опыт вперемешку с информацией из интернета. Здесь будет рассмотрена настройка Bind9 для виртуальной машины Ubuntu Server. Делаю я это под своими IP. Установка BIND9 Установим пакеты BIND9 и необходимые инструменты: sudo apt install bind9 bind9utils bind9-doc -y</p><p><a href="https://habr.com/ru/articles/894524/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">habr.com/ru/articles/894524/</span><span class="invisible"></span></a></p><p><a href="https://zhub.link/tags/ubuntu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ubuntu</span></a> <a href="https://zhub.link/tags/ubuntu_server" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ubuntu_server</span></a> <a href="https://zhub.link/tags/bind" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>bind</span></a> <a href="https://zhub.link/tags/bind9" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>bind9</span></a> <a href="https://zhub.link/tags/dns" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>dns</span></a></p>
Ansgar Hegerfeld<p>Schöner DNS-Workaround, den ich bis jetzt noch nicht kannte/brauchte: Um die (z.B. aus versehen zu weit in die Zukunft gesetzte) serial number eines Eintrags zurückzusetzen, muss man einfach nur das 32-bit große Feld zum Überlauf und damit wieder auf 0 bringen. Anschließend kann man es neu auf den Wunschwert setzen 😅</p><p><a href="https://www.zytrax.com/books/dns/ch9/serial.html" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">zytrax.com/books/dns/ch9/seria</span><span class="invisible">l.html</span></a></p><p><a href="https://digitalcourage.social/tags/DNS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DNS</span></a> <a href="https://digitalcourage.social/tags/bind9" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>bind9</span></a></p>
Felix Palmen :freebsd: :c64:<p>Adventures getting <a href="https://mastodon.bsd.cafe/tags/Netflix" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Netflix</span></a> to work in a somewhat complex home <a href="https://mastodon.bsd.cafe/tags/network" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>network</span></a> 🤯</p><p>I decided to give their plan with ads a chance, sounding like a somewhat fair deal. First issue was, I couldn't even register. It only offered me US plans. Figured that's because my <a href="https://mastodon.bsd.cafe/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv6</span></a> connectivity is tunnelled through <a href="https://mastodon.bsd.cafe/tags/HE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HE</span></a> (for reasons, different story). Of course using an endpoint here in Germany, but nevertheless, Netflix seemed to think it's a US located address.</p><p>Running my own <a href="https://mastodon.bsd.cafe/tags/bind9" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>bind9</span></a> instance, I found a way to hide relevant AAAA records (netflix' own domain and also amazonws) by adding a view only operating on local loopback and filtering out ALL AAAA records, and then adding forward-only zones for these domains to this local view. Horrible, but works, now I could register, forcing <a href="https://mastodon.bsd.cafe/tags/IPv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv4</span></a>.</p><p>One particularly cheap "smart-tv" still couldn't connect to netflix, always showing me an error that I was using some "VPN". 🤨 No way to analyze what exactly was happening there, but I finally found a solution for that as well: I created an entirely new network segment (with its own <a href="https://mastodon.bsd.cafe/tags/vlan" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>vlan</span></a> on the switch). I don't offer IPv6 in this segment at all, and only allow it to access the internet as well as my local <a href="https://mastodon.bsd.cafe/tags/dns" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>dns</span></a> server. Putting all tv sets and my <a href="https://mastodon.bsd.cafe/tags/minidlna" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>minidlna</span></a> instance into this segment, everything finally works.</p><p>The nice thing is, I always wanted to isolate the tv sets anyways, and this is now finally done, they're unable to see the rest of my home network! 🥳 Still a bit sad I have to restrict them to IPv4 for now, just to work around netflix' geolocation stuff... 🫤</p>