Going to leave this here in case it helps anyone. Turns out all the options in /etc/dhcpcd.conf were commented out. No idea how that happened.



-----------------

So I recently had some big issues with booting which were fixed by someone from the IRC channel and everything was fine. However, I've been away for a week or so and now I am back, things got weird again. I can get an IP address from DHCP but domains are failing to resolve for some reason. I can't modify /etc/resolv.conf, it keeps getting changed back. I tried rebooting but the problem persists. I also noted that sshd took a long time to come up on the reboot which is often a sign of DNS issues.

# 66-info -T net
net
Initialized: yes| Current: yes
Contains: | Enabled: yes
ââ(688,Enabled,classic) dhcpcd-log
ââ(685,Enabled,classic) sshd-log
ââ(687,Enabled,classic) sshd
ââ(686,Enabled,classic) dhcpcd

# ping google.com
ping: google.com: System error
Having 66-info working on your system that means you still have to upgrade since month/s ago, basically going from 66.0.1 or 0.2.0 to 66.0.2.1
https://web.obarun.org/index.php?id=116

There was a help bulletin which you will find in the news section of the site.
Basically upgrade, destroy trees and remake them. Not knowing which version of the 66 software you have it is hard to assume things.
s6 software has also been upgraded since then and s6 and 66 have to be in sync with each other to work right.
I suggest you do an upgrade of the system and follow the guide.
66-info -T is now 66-intree and 66-info -S is now 66-inservice, the output is very different.
My solution in fixing resolv.conf so it is not changed is # chattr +i /etc/resolv.conf the only way to edit it after this is to use the command # chattr -i /etc/resolv.conf
This is not a pro solution, and it produces an error on dhcp everytime they try to alter it to the router's default, but it works.

Powered by Obarun