Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 25239 - dhcpd gets started before named at boot, thus hostnames in dhcpd.conf won't resolve
Summary: dhcpd gets started before named at boot, thus hostnames in dhcpd.conf won't r...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Server (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-07-25 02:49 UTC by pasi.valminen
Modified: 2003-07-25 13:27 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description pasi.valminen 2003-07-25 02:49:32 UTC
Init (or rc) scripts in a boot level are started in order ls prints them in case
there are no deps. Thus net-misc/dhcp-3.0_p2 init script (dhcp) gets started
before net-dns/bind-9.2.2-r2 init script (named). If you have both services on
the same box, hostnames in dhcpd.conf won't resolve.

Reproducible: Always
Steps to Reproduce:
1. emerge dhcp
2. emerge bind
3. put dhcp and named in default runlevel
4. use hostnames in dhcpd.conf
5. reboot

Actual Results:  
Intranet hostnames did not resolve since dhcp was started before named. 

Expected Results:  
Hostnames should have been resolved and correct gw and ns ip addresses should
have been sent to clients via dhcp. 

Addind "after named" in /etc/init.d/dhcp depend section fixes it but ppl use
djbdns etc as well and i don't know if this works for them. 

fixed depend:
depend() {
    need net
    after named
}
Comment 1 Heinrich Wendel (RETIRED) gentoo-dev 2003-07-25 13:27:13 UTC
thx, added :)