man resolv.conf
which will showcase resolver(5) (the resolv.conf is an alias).mount /dev/gpt/rootfs /mnt/ufs
tar zxf /mnt/repo/iso/BSD/FreeBSD-11.1-RELEASE-amd64-bootonly.iso -C /mnt/ufs
ifconfig_em0="DHCP"
dhclient
is started during boot, but /etc/resolv.conf does not get populated, so when logging on ping 8.8.8.8
works, but ping google.com
doesn't....
The /etc/rc.conf includes
soCode:ifconfig_em0="DHCP"
dhclient
is started during boot, but ...
When in doubt use the manual pages. So in this caseman resolv.conf
which will showcase resolver(5) (the resolv.conf is an alias).
But that also brings us to yet another way to populate this file: resolvconf(8). Leading up the (IMO funny) manual page resolvconf.conf(5).
So yeah... this file can be managed by several processes, where dhclient is simply the most obvious one.
Try ifconfig_em0="SYNCDHCP" instead of ifconfig_em0="DHCP".