2024-04-24 09:09:56 +02:00
|
|
|
#!/usr/bin/env bash
|
|
|
|
set -x
|
|
|
|
|
|
|
|
# Require root or exit
|
|
|
|
if [ "$(id -u)" != "0" ]; then
|
|
|
|
echo "This script requires root." 1>&2
|
|
|
|
exit 1
|
|
|
|
fi
|
|
|
|
|
|
|
|
# In case I am behind the /etc/resolv.conf, it's immutable and read-only,
|
|
|
|
# which won't allow it to be rewritten.
|
2024-04-24 11:08:05 +02:00
|
|
|
chattr -V -i /etc/resolv.conf
|
|
|
|
chmod -v +w /etc/resolv.conf
|
2024-04-24 09:09:56 +02:00
|
|
|
# Or it's a symlink to e.g. /run/systemd/resolve/stub-resolv.conf
|
|
|
|
rm -v /etc/resolv.conf
|
|
|
|
|
|
|
|
# Actual resolv.conf creation. OK, this could read resolv.conf in this
|
|
|
|
# directory, but I like this being self-contained.
|
|
|
|
# tee -p = operate in a more appropriate MODE with pipes.
|
2024-08-10 10:32:22 +02:00
|
|
|
printf 'nameserver 127.0.0.53\nnameserver 127.0.0.1\nnameserver ::1\nsearch .\noptions timeout:1 attempts:5 rotate edns0 trust-ad\n' | tee -p /etc/resolv.conf
|
2024-04-24 09:09:56 +02:00
|
|
|
|
|
|
|
# Remove all other permissions than everyone reading resolv.conf
|
2024-04-24 11:08:05 +02:00
|
|
|
chmod -v a=r /etc/resolv.conf
|
2024-04-24 09:09:56 +02:00
|
|
|
# Make resolv.conf immutable again so it's pretty sure nothing else edits it.
|
2024-04-24 11:08:05 +02:00
|
|
|
chattr -V +i /etc/resolv.conf
|
2024-04-24 09:09:56 +02:00
|
|
|
|
|
|
|
# Let's just see it's ok
|
|
|
|
ls -l /etc/resolv.conf
|
|
|
|
cat /etc/resolv.conf
|
|
|
|
|
|
|
|
set +x
|