[CampusManager] Wildcard DNS Configuration

We were asked to provide an example configuration files for Linux
configuration for wildcard DNS to a single IP with explicit mappings
for specific IP(s).

Below are the contents of the /etc/named.conf file:

root_at_nessus4:/etc
> more named.conf
options {

        # The directory statement defines the name server?s
        # working directory

        directory "/var/named";
        recursion no;

        listen-on-v6 { any; };

        notify no;
};

server 192.168.15.14 {
bogus yes;
};

view "registration" {
      // This should match our registration network.
      match-clients { 192.168.15.0/24; };

      zone "." in {
              type master;
              file "root.hint.reg";
      };
};

view "remediation" {
      // This should match our internal networks.
      match-clients { 192.168.20.0/24; };

      zone "." in {
              type master;
              file "root.hint.rem";
      };
};

Below are the contents of the /var/named/root.hint.rem file:

root_at_nessus4:/var/named
> more root.hint.rem
$ORIGIN .
$TTL 1W
. IN SOA rem.bradford-rem.com. root.rem.bradford-rem.com. (
                        1
                        10800
                        3600
                        604800
                        86400
                        )
                NS rem.bradford-rem.com.
                TXT "Remediation Domain"
$ORIGIN bradford-rem.com.

; These are the servers on the Remediation Vlan
rem-server A 192.168.20.14

; These are the servers optionally required for Nessus Reports
; only if the clients are allowed to try to follow the links
; in the reports to clean themselves up.
cgi.nessus.org. A 206.241.31.24
archives.neohapsis.com. A 64.151.140.130
www.kb.cert.org. A 192.88.209.17
www.microsoft.com. A 207.46.249.221
msgs.securepoint.com. A 65.246.59.154

; Everybody Else
*. A 192.168.20.14
Received on Tue Mar 16 2004 - 21:35:13 EST