this happens on live ISO image, and also persists after installation. dhcp's DNS only propagates if you manually set or configure it. Network manager works out of the box.



on a separate note, "ping" command only shows responses when you run it with 'sudo'
That means your router is not providing dns or it doesn't really provide a dhcp service, but is providing you with a lan ip, or its dns servers are down.
NetMan... may be using internal IBM/RH dns ... who knows.

What is your /etc/resolv.conf like and /etc/hosts
Choose a couple of servers from https://servers.opennic.org/ --> hit OK on the top center
near you

enter them in /etc/resolv.conf like this:

nameserver 195.10.195.195

See if you can ping obarun
% sudo ping -c 3 forum.obarun.org
as i have stated, manually adding a valid DNS works. my router works fine as far as providing DNS to other linux distributions(arch and non arch) and windows. its only Obarun's dhcpd not able to provide DNS out-of-the-box.

no nameserver is provided in /etc/resolv.conf
negative wroteon a separate note, "ping" command only shows responses when you run it with 'sudo'
This is because ping does not have access to the required network capabilities unless run as root by default. You can make ping usable by normal users by running:
% sudo setcap cap_net_raw+ep /bin/ping
negative wroteas i have stated, manually adding a valid DNS works. my router works fine as far as providing DNS to other linux distributions(arch and non arch) and windows. its only Obarun's dhcpd not able to provide DNS out-of-the-box.

no nameserver is provided in /etc/resolv.conf
Instead of arch/non-arch you should be specifying systemd/non-systemd/non-elogind
then wonder why they route your dns somewhere where you can't control

In EU at least ISPs have been sentenced by law to keep logs of dns requests for all their "legal users".

Beware of who you trust and whether you are controlling your data or trust some multinational corp. to control you.
arch, archlabs, artix (runit, s6), void (runit), ubuntu, debian, devuan, endeavour (name any other distro including redhat and suse)... this things you are mentioning are irrelevant to my issue.
every single one of them builds dhcpcd with elogind/systemd (libelogind/libsystemd) and artix doesn't use eudev anymore, I don't know what void does.

Other than this I stopped using dhcpcd due to its autoconfiguring too much and having to fight it not to use router's default DNS servers.

Are you turning ipv6 off during boot, I noticed you use legacy interface names. If so, your router may be only providing ipv6 dns and you have blocked them at the boot-loader?

Just guessing, it is the only thing I can do with so much info.

The proper way to report problems with a service in Obarun is to provide the output of 
% sudo 66-inservice -g -d 30 dhcpcd
30 is for the last 30 lines of log, but if dhcpcd is having problems they will show there.
at the end of your /etc/dhcpcd.conf put 
static domain_name_servers=8.8.8.8 # or whatever about DNS ip
https://wiki.archlinux.org/title/Dhcpcd# DHCP_static_route(s)
eric wroteat the end of your /etc/dhcpcd.conf put 
static domain_name_servers=8.8.8.8 # or whatever about DNS ip
https://wiki.archlinux.org/title/Dhcpcd# DHCP_static_route(s)
thanks for the reply, eric.

as i have stated earlier, manually adding DNS does make dhcp work. BUT i do not remember ever needing to do this when i have just started using Obarun months ago. the last time i used obarun was when the 'banned_user' was still around...


connmand works out-of-the box, and so does networkmanager. both are able to set the default DNS provided by my service provider without issue using the same link/router.

dhcpcd, which is the default for the live ISO, should also "just work"
SOLVED: /etc/dhcpcd.conf is missing at least this line:
option domain_name_servers
dunno if this was intentional, (if it was i sure do wanna know why, seems like a hassle thing without it)

latest upstream changes to dhcpcd probably now requires a sane default configuration file
https://roy.marples.name/git/dhcpcd/blob/HEAD:/src/dhcpcd.conf
5 days later
eversince i started using obarun, i had to fix issues myself, especially with regards to the defaults used by obarun. issues like dbus thing, mounting usb storage in filemanagers like thunar and pcmanfm, and this time configuration lacking in the default dhcpcd.conf. they always blame it on "user error" despite like this time, its a default config issue.

i thought the "banned_user" leaving was a good sign for me to return, turns out its not. i had more interactions with him, some bad some good, than anyone else here.
huh.. turns out i cannot close this thread.. just please close if issue will not be addressed.

thanks!
4 months later
UPDATE:

this issue only happens when using the Minimal iso since by default it uses dhcpcd,while JWM uses connman. the dhcpc default has to be modified as stated above to avoid problems on some systems/hardware configurations when using the minimal iso.

Powered by Obarun