ifconfig_bge0_ipv6="inet6 accept_rtadv"
rtsold_enable="YES"
SirDice said:IPv6 SLAAC doesn't change the DNS settings as it doesn't receive any.
I've tried this on numerous occasions but neither my FreeBSD machines nor my Windows machines picked them up.kpa said:I'm not sure if you're correct here. It is possible to specify DNS forwarders in rtadvd.conf(5) and at least my laptop that is OS X 10.10 (Yosemite BETA) seems to be picking them up.
# Generated by resolvconf
search bbsyd.net
nameserver 2001:470:dd6c:0:b675:eff:fef9:fe9b
# chflags schg /etc/resolv.conf
. Of course that means it will not change, even when the DHCP data changes, but as long as you are aware of that, it works.[...]
ifconfig_bge0=" inet 192.168.1.2 netmask 255.255.255.0"
defaultrouter="192.168.1.1"
[...]
ipv6_network_interfaces="bge0"
ipv6_activate_all_interfaces="YES"
ifconfig_bge0_ipv6="inet6 accept_rtadv"
rtsold_enable="YES"
[...]
ifconfig_rl0="DHCP"
resolvconf assumes it has a job to do. In some situations resolvconf
needs to act as a deterrent to writing to /etc/resolv.conf. Where this
file cannot be made immutable or you just need to toggle this behaviour,
resolvconf can be disabled by adding resolvconf=NO to resolvconf.conf(5).
Resolvconf.conf does not fill it with its contents to make matter worse. A number of people have used cron to regularly copy resolv.conf to resolvconf.conf.It should be possible to keep resolvconf(8) from writing to /etc/resolv.conf entirely:
Code:resolvconf assumes it has a job to do. In some situations resolvconf needs to act as a deterrent to writing to /etc/resolv.conf. Where this file cannot be made immutable or you just need to toggle this behaviour, resolvconf can be disabled by adding resolvconf=NO to resolvconf.conf(5).
I meant copy resolvconf.conf to resolv.conf.Resolvconf.conf does not fill it with its contents to make matter worse. A number of people have used cron to regularly copy resolv.conf to resolvconf.conf.
You should never do that as both files serve completely different purposes. The file /etc/resolv.conf configures how your system resolves names into addresses and vice versa, i.e. what DNS server it uses for that purpose. The file /etc/resolvconf.conf however configures how the resolvconf(8) program, that accumulates information from various sources (i.e. DHCP) and then writes that information into /etc/resolv.conf operates.I meant copy resolvconf.conf to resolv.conf.
resolvconf=NO
The Handbook is pretty lacking in this area. It does not mention resolvconf(8) at all, and leaves the distinct impression that /etc/resolv.conf is rewritten by dhclient-script(8).You should never do that as both files serve completely different purposes. The file /etc/resolv.conf configures how your system resolves names into addresses and vice versa, i.e. what DNS server it uses for that purpose. The file /etc/resolvconf.conf however configures how the resolvconf(8) program, that accumulates information from various sources (i.e. DHCP) and then writes that information into /etc/resolv.conf operates.
Normally you don't need an /etc/resolvconf.conf file, as resolvconf(8) should do the right thing by default, therefore the file doesn't exist by default. If however your goal is to keep resolvconf(8) from ever touching your /etc/resolv.conf file, then you need to create the file /etc/resolvconf.conf with the following content:
Code:resolvconf=NO
dhclient
, then a simple /etc/dhclient.conf would do the trick: make DHCP client request only essential parameters, but don't request domain-name-servers option.interface "em0"
{
request subnet-mask, broadcast-address, routers;
}