BIND split-view DNS config problem
Posted
by organicveggie
on Server Fault
See other posts from Server Fault
or by organicveggie
Published on 2010-05-20T17:38:44Z
Indexed on
2010/05/20
17:50 UTC
Read the original article
Hit count: 421
We have two DNS servers: one external server controlled by our ISP and one internal server controlled by us. I'd like internal requests for foo.example.com to map to 192.168.100.5 and external requests continue to map to 1.2.3.4, so I'm trying to configure a view in bind. Unfortunately, bind fails when I attempt to reload the configuration. I'm sure I'm missing something simple, but I can't figure out what it is.
options {
directory "/var/cache/bind";
forwarders {
8.8.8.8;
8.8.4.4;
};
auth-nxdomain no; # conform to RFC1035
listen-on-v6 { any; };
};
zone "." {
type hint;
file "/etc/bind/db.root";
};
zone "localhost" {
type master;
file "/etc/bind/db.local";
};
zone "127.in-addr.arpa" {
type master;
file "/etc/bind/db.127";
};
zone "0.in-addr.arpa" {
type master;
file "/etc/bind/db.0";
};
zone "255.in-addr.arpa" {
type master;
file "/etc/bind/db.255";
};
view "internal" {
zone "example.com" {
type master;
notify no;
file "/etc/bind/db.example.com";
};
};
zone "example.corp" {
type master;
file "/etc/bind/db.example.corp";
};
zone "100.168.192.in-addr.arpa" {
type master;
notify no;
file "/etc/bind/db.192";
};
I have excluded the entries in the view for allow-recursion and recursion in an attempt to simplify the configuration. If I remove the view and just load the example.com zone directly, it works fine.
Any advice on what I might be missing?
© Server Fault or respective owner