Is my DNS set up properly for reverse lookups?
Tim Lanza
Tim at Lanzahost.com
Thu Jun 24 03:08:17 UTC 1999
I've configured a linux 5.2 server for DNS with service for 2 domain names
(firstdomain.com and seconddomain.com). Both are registered to the same
address (111.222.333.444 in this example). Everything seems to be working
fine, but I'm wondering if it's set-up properly. In particular, I'm not
sure about the reverse lookups. It seems incorrect that named.conf would
have two zone names that are the same (333.222.111.in-addr.arpa), one
references file firstdomain.rev file, the other references file
seconddomain.rev. The .rev files, in turn, point to the same IP address.
Example files are included for reference (sorry for the length). Is this
set-up correct?
TIA for any advice!
Tim
tjlanza at west.raytheon.com
######################
/etc/named.conf file
######################
// generated by named-bootconf.pl
options {
directory "/var/named";
/*
* If there is a firewall between you and nameservers you want
* to talk to, you might need to uncomment the query-source
* directive below. Previous versions of BIND always asked
* questions using port 53, but BIND 8.1 uses an unprivileged
* port by default.
*/
// query-source address * port 53;
};
//
// a caching only nameserver config
//
zone "." {
type hint;
file "named.ca";
};
zone "0.0.127.in-addr.arpa" {
type master;
file "localhost.rev";
};
zone "firstdomain.com" {
notify no;
type master;
file "lanzahost.db";
};
zone "333.222.111.in-addr.arpa" {
notify no;
type master;
file "firstdomain.rev";
};
zone "seconddomain.com" {
notify no;
type master;
file "seconddomain.db";
};
zone "333.222.111.in-addr.arpa" {
notify no;
type master;
file "seconddomain.rev";
};
#######################
/etc/resolv.conf file
#######################
search firstdomain.com
nameserver 127.0.0.1
################################
/var/named/firstdomain.db file
################################
@ IN SOA firstdomain.com. hostmaster.firstdomain.com. (
1999050900 ; Serial
8H ; Refresh
2H ; Retry
1W ; Expire
1D ) ; Minimum
TXT "firstdomain.com, The Internet Specialists"
NS foo.firstdomain.com.
MX 10 mail
localhost A 127.0.0.1
foo A 111.222.333.444
MX 10 mail
HINFO "Name Server" "Linux 5.2"
www CNAME foo.firstdomain.com.
MX 10 mail
HINFO "WWW Server" "Linux 5.2"
#################################
/var/named/seconddomain.db file
#################################
@ IN SOA seconddomain.com. hostmaster.seconddomain.com. (
1999050900 ; Serial
8H ; Refresh
2H ; Retry
1W ; Expire
1D ) ; Minimum
TXT "seconddomain.com, The Internet Specialists"
NS foo.firstdomain.com.
MX 10 mail
www CNAME foo.firstdomain.com.
MX 10 mail
HINFO "WWW Server" "Linux 5.2"
#################################
/var/named/firstdomain.rev file
#################################
@ IN SOA firstdomain.com. hostmaster.firstdomain.com. (
1999050900 ; Serial
8H ; Refresh
2H ; Retry
1W ; Expire
1D ) ; Minimum
NS foo.firstdomain.com.
444 PTR foo.firstdomain.com.
444 PTR www.firstdomain.com.
##################################
/var/named/seconddomain.rev file
##################################
@ IN SOA seconddomain.com. hostmaster.seconddomain.com. (
1999050900 ; Serial
8H ; Refresh
2H ; Retry
1W ; Expire
1D ) ; Minimum
NS foo.firstdomain.com.
444 PTR www.seconddomain.com.
More information about the bind-users
mailing list