返信元:
FirefoxのDNSキャッシュを消去しても、消えてない感じなんだけど、メモリも複数階層になってたりする？
hosts書き換え→Firefox再起動→再アクセスしたら反映されてる。
hosts書き換え→DNSキャッシュ消去→再アクセスしたら反映されてない。拡張機能のIPvFooの表示も反映されてないけど about:networking#dns は反映されてる。
検索
返信元:
Things moving quickly now. 😃
Don't know how, but somehow I just managed to do a short test stream on my self hosted #Owncast server.
After all the issues I had during the last days with my #RaspberryPi and my Internet Service Provider to get my server running , it was so invigorating to set up Owncast with such ease.
Thanks @[email protected] for the great software and the easy to follow documentation.
Didn't expect the installation being that easy. 👌
#selfhosting #streaming #fediverse
Today I found out that I can use a subdomain from my already existing online shop domain to #DNS forward to my #homeserver. I now have a nice looking web address for my #Owncast server and don't need to register a new domain. 🌐
After that I took care of gaining https and SSL. I followed Owncast's recommendation for Caddy, who provide a SSL reverse proxy with a free certificate from Let’s Encrypt.
At last I took care of the branding and individual look of the channel.
#selfhosting #Linux #FOSS
vmod-dynamic, our #varnishcache module for dynamic backends from #dns (A/CNAME and SRV records) has received some bug fixes and workarounds for issues in Varnish-Cache 7.5 and 7.6.
The new wait_timeout and wait_limits parameters are now supported.
See the changelog for details: https://github.com/nigoroll/libvmod-dynamic/blob/master/CHANGES.rst#76-branch
A release branch for 7.6 has been created: https://github.com/nigoroll/libvmod-dynamic/tree/7.6
We have new KSK for the root!
Today a mega ceremony was held where new HSMs were introduced and a new root key was generated in them. This key will be pre-publicated at the end of this year, and the rollover will be at the end of 2026. It'll be the third in the history of the DNS. The first was in 2010 and the second in 2017. #dns #dnssec
vmod-dynamic, our #varnishcache module for dynamic backends from #dns (A/CNAME and SRV records) has received some bug fixes and, in particular, workarounds specific to Varnish-Cache 7.4, for which a new https://github.com/nigoroll/libvmod-dynamic/tree/7.4 branch has been created.
返信元:
One of my domains transferred from #Google to #Squarespace, so it no longer shows up in domains.google, but it also doesn't show up in Squarespace, so the WHOIS is still mine, but I don't have access to DNS, etc., for it. This is great...
And the #Squarespace support page is in an endless login redirect loop, so I can't file a ticket about it. We're not off to a solid start.
#Google #GoogleDomains #DNS #domains
I've been writing several interdependent regex scripts to automate our #DNS, a strategy I'm sure I will most certainly not regret.
返信元:
It seems that most people who manage #bind with #Ansible have given up on the RFC recommendation for SOA serials YYYYMMDDxx and just use epoch time, which means that since it's a 32-bit unsigned value per RFC1035, there are going to be a lot of #DNS problems for domain names that are still operating in the year 2106.
In case anyone else needs it, here's a quick bash script I wrote to calculate the new serial for #bind zones. At the moment, it only supports one zone per file, but I can update it to grok more than one fairly easily if it would be helpful for anyone. In case the serial has been holding you up from automating your #dns entries:
https://mastodon.online/@vwbusguy/111014338230905573
It seems that most people who manage #bind with #Ansible have given up on the RFC recommendation for SOA serials YYYYMMDDxx and just use epoch time, which means that since it's a 32-bit unsigned value per RFC1035, there are going to be a lot of #DNS problems for domain names that are still operating in the year 2106.
あ、WebARENAで鯖立てた人向けなのですが、WebARENAのDNS、ちょっと挙動が怪しい（一部のtldを使用しているときに名前解決できない）ときがあるので、CloudflareかGoogleのパブリックDNSを使うのがおすすめです。
Ubuntu 22.04 LTSであれば、root権限で
↓
にした後、
Ubuntu 22.04 LTSであれば、root権限で
nano /etc/systemd/resolved.confなどでエディタを開き
#DNS=
↓
DNS=1.1.1.1 8.8.8.8
にした後、
systemctl restart systemd-resolved.serviceを実行するとよいです。