----- Original Message -----
From: Paul Goyette <paul@whooppee.com>
To: andrea <andrea.franceschini@linet.it>
Sent: Monday, April 12, 1999 3:45 PM
Subject: Re: DNS questions


> It all depends!
>
> Both syntax are correct.  It depends on whether you have an ORIGIN
> statement.  If you do, then that origin gets appended by default to your
> DNS names, so if you say
>
> ORIGIN yyy.xxx.194.in-addr.arpa.
> 65 IN PTR .......
>
> the 65 line is implicitly 65.yyy.xx.194.in-addr.arpa.

Ok, but what happens if  there isn't any  ORIGIN statement ?

And ,Let imagine that we have a full Class C Address-pool.
We assign this Pool to 2 different ISP (0-63) (64 - 127) the remains are
assigned to us (128 - 255).
Each ISP has his own NameServer.
when we need to translate an address from 129 to 254 we use our nameserver
and we can use something as follow in our
name server:

primary  yyy.xxx.194.in-addr.arpa.            yyy.xxx.194.dns

So our named  Daemon expect to find all reverse-mapping  for 194.xxx.yyy.0
subnet in  the file yyy.xxx.194.dns.

But what happens when is required to map an address outside our netmask (i.e
194.xxx.yyy.62 that is assigned to 1 ISP).?
Local named still belive to find the records in yyy.xxx.194.dns.
Now if i understand correctly me must add  the following lines to
yyy.xxx.194.dns file

0.yyy.xxx.194.in-addr.arpa    IN    NS     ns.firstisp.dns.
64.yyy.xxx.194.in-addr.arpa    IN    NS    ns.secondisp.dns.

And

At First ISP:
named.boot:

primary 0.yyy.xxx.in-addr.arpa            0.yyy.xxx.dns

0.yyy.xxx.in-addr.arpa:
1            IN         PTR            host1.firstisp.dns
...
63            IN        PTR            host63.firstisp.dns

At Second ISP:

named.boot:
primary 64.yyy.xxx.in-addr.arpa            64.yyy.xxx.dns

64.yyy.xxx.in-addr.arpa:
65            IN         PTR            host65.secondisp.dns
...
126            IN        PTR            host126.secondisp.dns


May this config work?
If not, what is the correct configuration? and where's wrong?
Thanks!