101010.pl

ꙮ liilliil 🇫🇯🇱🇨🇱🇧Заметил, что <a href="https://mastodon.online/tags/cloudns" class="mention hashtag" rel="nofollow noopener" target="_blank">#cloudns</a> работает с зонами <a href="https://mastodon.online/tags/opennic" class="mention hashtag" rel="nofollow noopener" target="_blank">#opennic</a> Поэтому уберу-ка у себя с серверов <a href="https://mastodon.online/tags/bind9" class="mention hashtag" rel="nofollow noopener" target="_blank">#bind9</a> и воспользуюсь бесплатным их предложением, ибо всякие левые ебланы через меня стали всякие левые домены запрашивать

LeJaxWho's manage his <a href="https://mastodon.bsd.cafe/tags/DNS" class="mention hashtag" rel="nofollow noopener" target="_blank">#DNS</a> zone files with <a href="https://mastodon.bsd.cafe/tags/git" class="mention hashtag" rel="nofollow noopener" target="_blank">#git</a>? And How?I cannot find a clear solution.I use <a href="https://mastodon.bsd.cafe/tags/Bind9" class="mention hashtag" rel="nofollow noopener" target="_blank">#Bind9</a> and <a href="https://mastodon.bsd.cafe/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeBSD</a> <a href="https://mastodon.bsd.cafe/tags/Jails" class="mention hashtag" rel="nofollow noopener" target="_blank">#Jails</a> Any advice are welcome.Thanks

FellThings I learnt about DNS:1. You can't "redirect" an entire domain with CNAME, only subdomains, which is why my website has been broken.2. You can't specify an AAAA record and use a wildcard for the A record. You have to explicitly put both.If the IP changes, you have to change it everywhere. I wonder if there is a modern DNS server which lets you avoid this sort of data duplication. <a href="https://ma.fellr.net/tags/DNS" class="mention hashtag" rel="nofollow noopener" target="_blank">#DNS</a> <a href="https://ma.fellr.net/tags/Networking" class="mention hashtag" rel="nofollow noopener" target="_blank">#Networking</a> <a href="https://ma.fellr.net/tags/Admin" class="mention hashtag" rel="nofollow noopener" target="_blank">#Admin</a> <a href="https://ma.fellr.net/tags/SysAdmin" class="mention hashtag" rel="nofollow noopener" target="_blank">#SysAdmin</a> <a href="https://ma.fellr.net/tags/BIND9" class="mention hashtag" rel="nofollow noopener" target="_blank">#BIND9</a> <a href="https://ma.fellr.net/tags/BIND" class="mention hashtag" rel="nofollow noopener" target="_blank">#BIND</a>

WulfyWhat's the least <a href="https://infosec.exchange/tags/evil" class="mention hashtag" rel="nofollow noopener" target="_blank">#evil</a> <a href="https://infosec.exchange/tags/DNS" class="mention hashtag" rel="nofollow noopener" target="_blank">#DNS</a> provider?I've put some of my properties on <a href="https://infosec.exchange/tags/Cloudflare" class="mention hashtag" rel="nofollow noopener" target="_blank">#Cloudflare</a>, and I can still hear the boo's. <a href="https://infosec.exchange/tags/Google" class="mention hashtag" rel="nofollow noopener" target="_blank">#Google</a> cloud DNS and <a href="https://infosec.exchange/tags/AWS" class="mention hashtag" rel="nofollow noopener" target="_blank">#AWS</a> are no better.I can put <a href="https://infosec.exchange/tags/Bind9" class="mention hashtag" rel="nofollow noopener" target="_blank">#Bind9</a> on my own <a href="https://infosec.exchange/tags/FOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#FOSS</a> stacks, but I probably lack the uptime for reliability.I'm moving away from my CPanel provider into my own <a href="https://infosec.exchange/tags/Selfhosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#Selfhosting</a> on a <a href="https://infosec.exchange/tags/VPS" class="mention hashtag" rel="nofollow noopener" target="_blank">#VPS</a>.I'm thinking one NS on something reliable and one on my own stack.What does <a href="https://infosec.exchange/tags/masodon" class="mention hashtag" rel="nofollow noopener" target="_blank">#masodon</a> hivemind recommend?

Felix Palmen :freebsd: :c64:Adventures getting <a href="https://mastodon.bsd.cafe/tags/Netflix" class="mention hashtag" rel="nofollow noopener" target="_blank">#Netflix</a> to work in a somewhat complex home <a href="https://mastodon.bsd.cafe/tags/network" class="mention hashtag" rel="nofollow noopener" target="_blank">#network</a> 🤯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" target="_blank">#IPv6</a> connectivity is tunnelled through <a href="https://mastodon.bsd.cafe/tags/HE" class="mention hashtag" rel="nofollow noopener" target="_blank">#HE</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.Running my own <a href="https://mastodon.bsd.cafe/tags/bind9" class="mention hashtag" rel="nofollow noopener" target="_blank">#bind9</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" target="_blank">#IPv4</a>.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" target="_blank">#vlan</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" target="_blank">#dns</a> server. Putting all tv sets and my <a href="https://mastodon.bsd.cafe/tags/minidlna" class="mention hashtag" rel="nofollow noopener" target="_blank">#minidlna</a> instance into this segment, everything finally works.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... 🫤

Forst"Let me quickly try this one <a href="https://mastodon.social/tags/Bind9" class="mention hashtag" rel="nofollow noopener" target="_blank">#Bind9</a> thing in <a href="https://mastodon.social/tags/Docker" class="mention hashtag" rel="nofollow noopener" target="_blank">#Docker</a>", I thought. No arm64 image. Can't tell if my configuration is bad or if x86 emulation isn't working :/

Petr Menšík :fedora:<a href="https://mastodon.gougere.fr/@bortzmeyer" class="u-url mention" rel="nofollow noopener" target="_blank">@bortzmeyer</a> <a href="https://social.sdf.org/@draeath" class="u-url mention" rel="nofollow noopener" target="_blank">@draeath</a> <a href="https://qoto.org/@Shamar" class="u-url mention" rel="nofollow noopener" target="_blank">@Shamar</a> it depends. No stable <a href="https://fosstodon.org/tags/bind9" class="mention hashtag" rel="nofollow noopener" target="_blank">#bind9</a> release can forward over DoT (yet). None of them can forward over <a href="https://fosstodon.org/tags/DoH" class="mention hashtag" rel="nofollow noopener" target="_blank">#DoH</a> even on the latest commit afaik.

Petr Menšík :fedora:<a href="https://social.sdf.org/@draeath" class="u-url mention" rel="nofollow noopener" target="_blank">@draeath</a> <a href="https://qoto.org/@Shamar" class="u-url mention" rel="nofollow noopener" target="_blank">@Shamar</a> no, both <a href="https://fosstodon.org/tags/bind9" class="mention hashtag" rel="nofollow noopener" target="_blank">#bind9</a> and <a href="https://fosstodon.org/tags/unbound" class="mention hashtag" rel="nofollow noopener" target="_blank">#unbound</a> implement only server side. They can accept queries over DoH, but cannot forward them to DoH remote server. I am not sure about Knot, but might have the same problem. Forwarding over DoH is rare ability. Dnsdist is one of few capable of it.

IT NewsDoing DNS and DHCP for your LAN the old way—the way that works - Enlarge / All shall tremble before your fully functional forward and re... - <a href="https://arstechnica.com/?p=2001156" rel="nofollow noopener" translate="no" target="_blank">https://arstechnica.com/?p=2001156</a> <a href="https://schleuss.online/tags/domainnamesystem" class="mention hashtag" rel="nofollow noopener" target="_blank">#domainnamesystem</a> <a href="https://schleuss.online/tags/weekendprojects" class="mention hashtag" rel="nofollow noopener" target="_blank">#weekendprojects</a> <a href="https://schleuss.online/tags/itprojects" class="mention hashtag" rel="nofollow noopener" target="_blank">#itprojects</a> <a href="https://schleuss.online/tags/features" class="mention hashtag" rel="nofollow noopener" target="_blank">#features</a> <a href="https://schleuss.online/tags/projects" class="mention hashtag" rel="nofollow noopener" target="_blank">#projects</a> <a href="https://schleuss.online/tags/feature" class="mention hashtag" rel="nofollow noopener" target="_blank">#feature</a> <a href="https://schleuss.online/tags/homelab" class="mention hashtag" rel="nofollow noopener" target="_blank">#homelab</a> <a href="https://schleuss.online/tags/biz" class="mention hashtag" rel="nofollow noopener" target="_blank">#biz</a>⁢ <a href="https://schleuss.online/tags/bind9" class="mention hashtag" rel="nofollow noopener" target="_blank">#bind9</a> <a href="https://schleuss.online/tags/dhcpd" class="mention hashtag" rel="nofollow noopener" target="_blank">#dhcpd</a> <a href="https://schleuss.online/tags/bind" class="mention hashtag" rel="nofollow noopener" target="_blank">#bind</a> <a href="https://schleuss.online/tags/dns" class="mention hashtag" rel="nofollow noopener" target="_blank">#dns</a>

Petr Menšík :fedora:<a href="https://infosec.place/users/JerryMouse" class="u-url mention" rel="nofollow noopener" target="_blank">@JerryMouse@infosec.place</a> <a href="https://infosec.exchange/@JerryMouse" class="u-url mention" rel="nofollow noopener" target="_blank">@JerryMouse@infosec.exchange</a> <a href="https://infosec.exchange/@mypdns" class="u-url mention" rel="nofollow noopener" target="_blank">@mypdns</a> <a href="https://mastodon.social/@Alonely0" class="u-url mention" rel="nofollow noopener" target="_blank">@Alonely0</a> <a href="https://mastodon.social/@floppy_bv" class="u-url mention" rel="nofollow noopener" target="_blank">@floppy_bv</a> no, I mean <a href="https://fosstodon.org/tags/IXFR" class="mention hashtag" rel="nofollow noopener" target="_blank">#IXFR</a>. That is incremental zone transfer. <a href="https://fosstodon.org/tags/Bind9" class="mention hashtag" rel="nofollow noopener" target="_blank">#Bind9</a> can do it, not sure <a href="https://fosstodon.org/tags/Unbound" class="mention hashtag" rel="nofollow noopener" target="_blank">#Unbound</a> has that too. Allows to just receiving changes compared to previous version, but need to store journal containing each change at primary and secondary server. Using AXFR is similar to downloading hosts file over http. I think PiHole uses own modified dnsmasq build, which provides webui integration.

VftdanHow to completely disable DNSSEC in bind9 for exactly one zone?<a href="https://mastodon.ml/tags/dns" class="mention hashtag" rel="nofollow noopener" target="_blank">#dns</a> <a href="https://mastodon.ml/tags/bind9" class="mention hashtag" rel="nofollow noopener" target="_blank">#bind9</a> <a href="https://mastodon.ml/tags/named" class="mention hashtag" rel="nofollow noopener" target="_blank">#named</a>

Recent searches

Search options

Administered by:

Server stats:

#bind9