8.2.1 Global/Selective Forwarding Problem

George Papadopoulos georgep at ilx.com
Thu Sep 23 16:28:25 UTC 1999


Hi,

    We've got a problem using 8.2.1 and utilizing both global
and selective forwarding. We've got a split DNS system and our
core networks are behind a firewall.

    Our main intranet DNS needs to be able to use global forward
to resolve internetaddresses. In addition its SOA for our ILX.COM
and various subdomains. Certain subdomains exist on a Windows NT4.0
DNS server that we used selective forwarding to query (see
cust.ilx.com). This behavior seemed to work under 8.2, but fails
under 8.2.1. The selectively forwarded reversals for the same network
do work however.

    Does anyone have an idea what we are missing here? Is it possible
there is a delegation issue i am missing here? Keep in mind the
selectively forward domains fall under ilx.com (that is, cust.ilx.com)
Any help would be appreciated...


Here is and example of the config inside the core:

options {
        forwarders { 172.27.253.215; }    (Our Internet name
server/resolver)
        };

zone "." {
        type hint;
        file "named.ca";
        };

zone "admin.ilx.com" {
        type master;
        file "named.admin";        (Local subdomains we maintain SOA for
locally)
        };

zone "cust.ilx.com" {
        type forward;
        forward only;
        forwarders { 172.27.101.202; 172.27.101.201; };
                    (An NT 4 DNS server we cant pull zones from)
        };

zone "100.27.172.in-addr.arpa" {
        type forward;
        forward only;
        forwarders { 172.27.101.202; 172.27.101.201; };
                    (An NT 4 DNS server we cant pull zones from)
        };



More information about the bind-users mailing list