forwarding queries to another server (huh?)

[Tomas B. Winkler]

Your remark is true, but what I've probably havn't stressed enough that
what I need is a SEPARATE named to be in charge of test  domain. I cannot
temper with the main domain name servers. 

Tomas Winkler
The System Group
CSE HUJI

On Mon, 19 Mar 2001, Kevin Darcy wrote:

> 
> Tomas B.Winkler wrote:
> 
> > Hi
> > I have a similar problem I have an existing domain, let say foo.bar.org
> > and I would like to span on it a sub-domain let say test.foo.bar.org
> > It wouldn't be so hard but I need a separated named to be a master dns.
> 
> Huh? Are you under the impression that a nameserver can be master for only
> one zone? Untrue: a single nameserver can be master for large numbers of
> zones -- some folks are running thousands of zones from a single
> nameserver instance. So there's no reason why your nameserver couldn't be
> master for both "foo.bar.org" and "test.foo.bar.org".
> 
> But, before you go ahead and configure that, ask yourself whether it's
> necessary to delegate a subzone for the test.foo.bar.org subdomain at
> all. You could just add the test.foo.bar.org names to the foo.bar.org
> zone. Zones and subdomains are not synonymous, although it is true all
> zones -- other than the root zone, of course -- are distinct subdomains of
> some parent domain.
> 
> > The problem is the computer which runs named has not canonical name in
> > the test.foo.bar.org domain so the entry is ignored
> > The db file looks
> >
> > $TTL  86400
> > @      IN SOA test.foo.bar.org. tomasw.foo.bar.org. (
> >                                       42            ; serial
> > (d. adams)
> >                                       3H              ; refresh
> >                                       15M             ; retry
> >                                       1W              ; expiry
> >                                     1D )            ; minimum
> >
> >       1D IN NS        mycomp.foo.bar.org.
> >
> > localhost             1D IN A         127.0.0.1
> > mycomp.foo.bar.org.   1D IN A         xx.xx.xx.xx
> > test.foo.bar.org.     1D IN CNAME     mycomp.foo.bar.org.
> > zzz.test.foo.bar.org. 1D IN CNAME     mycomp.foo.bar.org.
> 
> Okay, now you've really lost me. Is this the zone file for foo.bar.org or
> test.foo.bar.org? You didn't say. If it's the foo.bar.org zone file, then
> the "test.foo.bar.org" entries in it should work fine *without* the need
> for any subzone delegation, as discussed above. On the other hand, if it's
> the test.foo.bar.org zonefile, then it's pretty hopeless: not only does
> the "test.foo.bar.org" CNAME conflict with the "test.foo.bar.org" SOA and
> NS records, but the "mycomp.foo.bar.org" entry doesn't belong in the zone
> file at all.
> 
> By the way, regardless of how the zone is loaded, you shouldn't be using
> an alias in the MNAME field ("test.foo.bar.org") of your SOA RR. You
> should be using the canonical name ("mycomp.foo.bar.org") instead.
> 
> 
> - Kevin
> 
> > On Mon, 19 Mar 2001, Pumpkinhead wrote:
> >
> > > Hi,
> > >
> > > I have an internal domain, say foo.bar.com.I have a name server
> > > behaving properly for it.Call it nsfoo.
> > >
> > > Now I have set up a test environment domain, say test.bar.com.Note
> > > that it's not a subdomain of the first.
> > >
> > > I want a name server (nstest) on test.bar.com to handle its own
> > > queries.That is, when nsfoo receives those queries it makes nstest
> > > deal with them.
> > >
> > > In named.conf on nsfoo I have the following entry:
> > >
> > > zone "test.bar.com" {
> > >     type forward;
> > >     forward only;
> > >     forwarders{
> > >             172.xxx.xxx.xxx;
> > >     };
> > > };
> > >
> > > But alas it doesn't work.Do I need to configure my forward RR's ?
> > >
> > > Thanks in advance,
> > >
> > > Peter
> > >
> > >
> 
> 
> 
> 
>