Desperate!!!

[Kevin Darcy]

If you just want to serve internal names, then you should set up your own root
nameserver internally so that named can "prime" properly. Setting up an
internal root zone isn't really a big deal. In fact, in some ways it's simpler
than setting up non-root zones, since the root zone has no parent in which to
create delegation records.

If you want to serve internal names always *and* serve external names whenever
you happen to be connected to the Internet, then that's a lot harder. The only
way I can think of to make that work is to have two nameserver configurations
(one of them strictly internal-root and one of them using the Internet roots)
and switch between them whenever you connect/disconnect. Note that you could
use the same zonefiles for your internal zones in both configurations. If
you're using an unregistered domain internally that happens to be taken by
someone else, however, then you'll be blind to the "real" names in that domain,
even when you are connected to the Internet.


- Kevin

Mees wrote:

> Jeffrey C. Albro <jeff at velvet.antistatic.com> schreef in berichtnieuws
> 92oedd$7q at pub3.rc.vix.com...
> >
> >
> > named "primes" itself by contacting the root nameservers to make sure it
> > has a connection.  I suspect that named is trying to contact the "D" root
> > nameserver when you start it up, and trying to contact an outside ip
> > address starts up the ISDN.
>
> Maybe, but I think that is a configuration fault? On an other server with
> SuSE LiNUX 6.1 and kernel 2.2.14 I have no problems with this and I am using
> the same version of named.
>
> >
> > Now, why are you trying to run named in the first place?  Are you only
> > trying to answer queries inside your own network?
>
> My goal is a caching name server plus I think its nice to use addresses like
> www.mynetwork.what instead of an IP-number and I understand this is the way
> to do so.
> >
> > -Jeff
>
> >
> > On Sun, 31 Dec 2000, Mees wrote:
> >
> > > Hello,
> > >
> > > I'm desperate...
> > > I've build a server with SuSE7.0 with a DNS-server.
> > > For whatever reason it is constantly dialing out on my ISDN line and i
> can't
> > > figure out what couses that.
> > >
> > > In my log file I get the followin message:
> > >
> > > kernel: isdn_net: ippp0: dial rejected: interface not in dialmode
> > > `auto',signalling dst_link_failure
> > >
> > > This after I set my ISDN device to manual dialing. Before it was:
> > >
> > > kernel: OPEN: 192.168.0.99 -> 128.8.10.90 UDP, port: 1024 -> 53
> > > Dec  4 01:31:24 fs1 kernel: ippp0: dialing 1 0302301333...
> > > Dec  4 01:31:31 fs1 kernel: isdn: HiSax,ch0 cause: E001B
> > > Dec  4 01:31:32 fs1 kernel: ippp0: dialing 2 0302301333...
> > > Dec  4 01:31:39 fs1 kernel: isdn: HiSax,ch0 cause: E001B
> > > Dec  4 01:31:40 fs1 kernel: isdn_net: local hangup ippp0
> > > Dec  4 01:31:40 fs1 kernel: ippp0: Chargesum is 0
> > > Dec  4 01:31:44 fs1 kernel: isdn_tx_timeout dev ippp0 dialstate 0
> > >
> > > The IP-adress in the first line is from:
> > >
> > > D.ROOT-SERVERS.NET.     6D IN A   128.8.10.90
> > >
> > > I first thought that it had something to do with my Sendmail
> configuration
> > > but disabling that had no result.
> > >
> > > Who can help me please with this problem?
> > >
> > > --
> > > Mees
> > > jw.mesenig at hccnet.nl
> >
> > --------------------------------------------------------------------------
> --
> > > -----------------
> > > Running SuSE 6.1 and kernel 2.2.14
> > >  12:42pm  up 5 days, 15:58,  1 user,  load average: 0.90, 0.48, 0.28
> >
> > --------------------------------------------------------------------------
> --
> > > -----------------
> > >
> > >   SuSE  _  __  ____  __
> > >  / / ()/ \/ / / /\ \/ /
> > > / /_/ / \  / / / / /\/
> > > \__/_/_//_/\__/ /_/\_\
> > >
> > >
> > >
> > >
> > >
> > >
> >
> >
> >
> >
> >