two masters - diff. information - forward

[Mathias Körber]

> Hi all,
>=20
> we plan to have two masters for one zone,but holding different=20
> information.
> One (A) should be in the DMZ of our network resolving adresses located
> there. The other (B) should hold information of our internal network, =
but
> should have (A) in the forwarder list. My problem is that namesever =
(B)
> can't resolve adresses which are exclusevely hold on (A).

If this is for the same zone, you cannot really have hosts held
exclusively on (B) and have (A) check it if it does not find
it in its own copy of the zone. Each copy of a zone if considered
complete by an authoritative NS, and it will return an NXDOMAIN
if the queried record does not exist.

In your case, I'd just import the data on the outside (B) into the =
inside
copy (A), unless there is a different record for the same host.


> For testsing I made nslookups on (B): I could only resolve names of =
our
> zone mydomain.com that are hold on (B), but I could resolve names that
> don't belong to our zone (internet). Doesn't the forward option=20
> work within
> a zone? In the logs I recognized that (B) is asking (A) for the=20
> adress, but
> he receives "Non-existent host/domain".
> Of course: an nslookup on (A) for the same name does work.
>=20
> Detailed info:
> (A) and (B) are both masters of myzone.com.
>=20
> named.conf of (A):
>=20
> ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
> ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
> :::::::::::::
> options {
>=20
>         // Directory, where config files reside in
>=20
>          directory "/etc/bind";
>=20
>=20
>         // Fowarders of ISP
>=20
>          forward only;
>          forwarders {
>                 194.163.252.4; 195.180.210.65; 193.98.9.5;
>         };
> };
>=20
> zone "." in {
>         type hint;
>         file "db.root";
> };
>=20
>=20
> // Bind is master for:
>=20
> zone "myzone.com" in {
>         type master;
>         file "myzone.domain";
> };
>=20
> zone "143.176.193.in-addr.arpa" in {
>         type master;
>         file "myzone.rev";
> };
>=20
> zone "0.0.127.in-addr.arpa" in {
>         type master;
>         file "db.local";
> };
>=20
> ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
> :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
>=20
> named.conf of (B):
>=20
> ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
> :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
>=20
> options {
>=20
>         // Directory, where config files reside in
>=20
>          directory "/etc/bind";
>=20
>=20
>         // Fowarders
>=20
>          forward only;
>          forwarders {
>                 IP.OF.(A);
>         };
> };
>=20
> zone "." in {
>         type hint;
>         file "db.root";
> };
>=20
>=20
> // Bind is master for:
>=20
> zone "mydomain.com" in {
>         type master;
>         file "mydomain.domain";
> };
>=20
> zone "143.176.193.in-addr.arpa" in {
>         type master;
>         file "mydomain.rev";
> };
>=20
> // and master for:
>=20
> zone "0.0.127.in-addr.arpa" in {
>         type master;
> };
>=20
> ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
> :::::::::::::::::::::::::::::::::::::::::::::::::::::::::
>=20
>=20
> What's wrong with my configuration? Please help.
>=20
> Thanx in advance, Michael
>=20
>=20
>=20
>=20