[SOLVED] interface starts to late for service to bind?

[imbiea]

Well, I 'think' that is my problem.

I'm running a server in which many of my services are bound to my inside interface, and some are bound to my outside.


When my box boots, I find that my squid proxy does properly bind to the inside interface, however things like bind does start, but not bind to the outside interface.

If... I do a /etc/init.d/bind restart.... Then bingo, it then binds to the correct interface.

I'm 'guessing' that the interface isn't plumbed yet when bind starts, so it wont' bind to the interface.

Ideas?

[VinzC]

Do you know what BIND stands for?

If you want a reliable DNS caching system plus a DHCP server for your LAN, then there is dnsmasq. I was using BIND before, too. FYI I came across the article I mentioned after a critical failure was found in BIND and in proprietary derivatives, recently. Since then I replaced all occurrences of BIND with dnsmasq and I must say it has never failed as much as Bind did.

As an example, like you, I have more than one Ethernet interfaces and dnsmasq copes with them fairly well. No matter what interface starts after dnsmasq, the latter detects it and binds to its IP address if needed. It can also detect changes to the hosts file without restarting it -- the hosts file is used for static hosts like in BIND zone files but it's simpler.

If you're looking for a reliable DNS service, which can bear a high load, then there is djbdns, from the creator of the article above. However I've never tried it.

Hence my advice is: don't use BIND!
_________________
Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
1739!

[imbiea]

You didn't answer my question, and yes I know what BIND is... <duh...

Thanks for your wonderful insight into a Gentoo problem that affects more services than just bind.

btw... this issue also is a problem with ssh. Will you spout off about that too?

As I stated before, if you restart these services after the system boot, then it's fine, it's just that they don't start during boot.



I love it when people post to be annoying, but don't look at the real question.

[VinzC]

Well if you don't want to listen to advices, that's up to you. But I *know* for sure BIND is just a piece of crap [and it's probably the reason why you're experiencing this]. Now if all you want to do is make sure bind starts after a given script, you can always tweak its script. Are you runing baselayout 1* or 2*?

EDIT:

[VinzC]

One thing you might try is to set RC_NET_STRICT="yes" with baselayout-1* (IIRC) and set a timeout for all your interfaces in /etc/conf.d/net, like plug_timeout_<ifname>="15" or something. With baselayout-2* strict dependency checks are already set so all you need is to set a timeout value for your interfaces.
_________________
Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
1739!

[imbiea]

Ok, now we're getting somewhere.. Thank you.


emerge --info
sys-apps/baselayout: 1.12.11.1

However I did just set the RC_NET_STRICT_CHECKING="yes"

in my /etc/conf.d/rc and... bingo!!

Now all my services are behaving properly!!


And... On a second note...I'll look at Bernstein's DNS... you are not the first to mention it to me


Thanks a ton for the help. I'll get rid of BIND soon.. I promise. I've just been using it for 10 years.. so it's hard to get rid of.

Thanks!

[VinzC]

Depends on whether you need DNS for a large or home LAN but I now use dnsmasq for all networks I setup. I think for a network as large as 200 machines, dnsmasq will still do the trick.

I got rid of BIND after, say, 4 years of labour and services but it was no such big deal. Recovering hosts (A records) that didn't come from DHCP dynamic updates was trivial enough to put them into a hosts file, which is quite convenient to provide quick aliases and the like. I haven't had an opportunity to try anything for larger networks.
_________________
Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
1739!