|
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
|
Re: [PLUG] Bind - Question again
|
On Tue, 17 Sep 2002, gabriel rosenkoetter wrote:
> On Tue, Sep 17, 2002 at 10:44:50AM -0400, Doug Crompton wrote:
> > PPP starts in run levels 2-5 with a respawned startup script in inittab.
> > It does not seem to start until late in the boot process however. After
> > most everything else is loaded. My default boot is run level 3. I init to
> > 5 manually as needed.
>
> When you say "it does not seem to start", do you actually mean that
> it doesn't *connect* until late in the boot process? init(8)
> shouldn't (and probably doesn't) let pppd hang the boot process
> while it dials and connects...
>
Yes it does not start until late in the boot process but it does not hang
anything.
> Doesn't pppd have an after-connect script of some sort? Couldn't you
> have that run your down-and-up of BIND automatically?
>
yes it does and that would probably work. ip-up and ip-down scripts.
> Also, as someone else already suggested, if you're only running a
> *caching* name server (rather than one that other people are
> supposed to be able to query), then you only actually need to have
> BIND listen on lo, and you should put nameserver 127.0.0.1 as the
> first nameserver line in your /etc/resolv.conf.
>
I namesever for about 12 low usage domains. So I do need to have outside
(internet) namserving capablility.
> > I am not sure how to make the order change (as someone suggessted) given
> > that this is run from inittab. This is not a big deal since I can make a
> > work-around by stopping and starting named after the ppp connection is
> > established. There has to ber a better way though. I would think that bind
> > could listen on ports that come up after it is running and not have to be
> > restarted. I kind of think it is a bind issue.
>
> "Port" doesn't really have any meaning here. BIND is capable of
> listening on "any IP address" (and probably does by default on your
> system), but that's not going to fix your problem. PPP is weird in
> that it adds an *interface* to your system after boot. That generates
> a whole separate set of structures in your kernel's IP stack which
> simply aren't there when BIND boots. There's no *way* for BIND to
> know about interfaces that don't exist when it starts up.
>
Well bind does have a listen-on statement which allows you to specify IP
addresses to listen on. It appears though that it will not listen on an
address that the system does not have established as an interface. I have
two ethernet cards installed - 192.168 and block of eight in real space I
use connected to another network here. I can specify listen-on's for those
ports and 127.0.0.1 but it will not listen on the PPP (yet to be assigned)
static IP address.
Maybe I am configuring something wrong. Since I will always have a PPP
static IP should I set that somewhere as my IP address before it gets
established by PPP. The static IP is obviously set in my PPP options.
Doug
> --
> gabriel rosenkoetter
> gr@eclipsed.net
>
****************************
* Doug Crompton *
* Richboro, PA 18954 *
* 215-431-6307 *
* *
* doug@crompton.com *
* wa3dsp@wa3dsp.ampr.org *
* http://www.crompton.com *
****************************
_________________________________________________________________________
Philadelphia Linux Users Group -- http://www.phillylinux.org
Announcements - http://lists.netisland.net/mailman/listinfo/plug-announce
General Discussion -- http://lists.netisland.net/mailman/listinfo/plug
|
|