/etc/init.d/named always gets startet BEFORE net.ethX and thus port 53 only gets bound on 127.0.0.1 and not your ethX IP. Looks like /etc/runlevels/default/ is used alphabetically?! lrwxrwxrwx 1 root root 17 25. Jan 01:05 named -> /etc/init.d/named lrwxrwxrwx 1 root root 20 19. Okt 2006 net.eth0 -> /etc/init.d/net.eth0 /etc/init.d/named has this: depend() { need net use logger provide dns } but it does not work. It really sucks to have to start named manually after rebooting!
need net works perfectly fine and if net.lo satisfies net for you, then you need to configure your system more properly for your needs, depending on baselayout version you are using. If you need support with this, see http://www.gentoo.org/main/en/support.xml, please don't use bugzilla for such things.
Do I understand correctly, that net.eth0 should provide net and not net.lo? To reproduce, do: emerge '=net-dns/bind-9.4.1_p1' in /etc/named/bind.conf, add the IP of eth0 in the listen line: listen-on { 192.168.0.2; 127.0.0.1; }; rc-update add named default so we have: # rc-update show | grep net local | default nonetwork net.eth0 | default net.lo | boot netmount | default net.ppp0 | default Then, named won't listen on 192.168.0.2 after rebooting.
For starters, you failed to provide emerge --info, so there's noone to help you debug your issue with your configuration because we don't know your baselayout version. As noted above, if works perfectly fine both with baselayout-1 and baselayout-2. With baselayout-1, see /etc/conf.d/rc; with baselayout-2, add services to runlevels as required for your needs. Move support questions out of bugzilla, please, this is not a support forum.
I use baselayout-1, in /etc/conf.d/rc: RC_NET_STRICT_CHECKING="yes" fixes this. The issues occured, because I have multiple NICs. Sorry, I didn't know that and thought it was a bug in a startscript or something.
Cool... Thanks for confirming that it really works and closing.
