Last active
October 17, 2021 21:30
-
-
Save penguinpowernz/9924335 to your computer and use it in GitHub Desktop.
BECAUSE FUCK resolvconf
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# THIS FILE MAY BE EDITED MANUALLY | |
nameserver 192.168.3.1 | |
nameserver 8.8.8.8 | |
# BECAUSE FUCK resolvconf |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#!/bin/bash | |
sudo apt-get purge resolvconf | |
sudo unlink /etc/resolv.conf | |
sudo touch /etc/resolv.conf | |
sudo cat > /etc/resolv.conf << EOF | |
# THIS FILE MAY BE EDITED MANUALLY | |
nameserver 192.168.3.1 | |
nameserver 8.8.8.8 | |
# BECAUSE FUCK resolvconf | |
EOF |
I still struggle to see why I need to enter my DNS server details each reboot just for the sake of it. I guess the first few times was OK, but after about the billionth time of not being able to resolve hostnames on boot, well it does enough to make me wanna kick the heck outta the computer. Surely there has to be an incentive for these numpties not to fix such a broken POS.
I just googled "fuck resolv.conf" and it brings you straight here. nice one.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Thank you kind Sir :)