Localhost
Aragon
aragon at aragonsworld.net
Sat Feb 9 14:19:05 UTC 2002
Thanks 'Peter Kakanson' for your answer on (no subject) for Aragonsworld.net.
I did see the syslog entries for 'zonecheck.manet.nu' .....
You said my nameserver was not answering DNS querys.....
I need to find out if this is the reason: after seeing several references
in the
digest to domains having a 'localhost' zonefile, I inquired of my friend
whether
I needed one and his answer was yes. Until a few days ago I only had zone
files for
'127.0.0' and '208.190.106.2' and of course my 'hosted domains' zone files.
Here is the 'localhost zone file' I added: (db.localhost)
===============
$TTL 1W
localhost. IN SOA ns1.aragonsworld.net.
root.ns1.aragonsworld.net. (
2002020500
24H
2H
30D
1W )
;
localhost. IN NS localhost.
;
localhost. IN PTR 127.0.0.1
;
===============
Here is my existing file: (db.127.0.0)
===============
$TTL 1W
0.0.127.in-addr.arpa. IN SOA ns1.aragonsworld.net.
root.ns1.aragonsworld.net. (
2001062701
24H
2H
30D
1W )
;
0.0.127.in-addr.arpa. IN NS ns1.aragonsworld.net.
;
1.0.0.127.in-addr.arpa. IN PTR localhost.
;
===============
Here is my 'named.conf' file:
===============
options {
directory "/etc/namedb";
dump-file "/etc/named_dump.db";
multiple-cnames yes;
version "Nexus";
notify yes;
check-names response warn;
check-names master warn;
fetch-glue yes;
allow-query { 151.164.1.1; 151.164.1.7; 63.82.197.34;
66.137.140.185; 192.168.0/24; };
allow-recursion { 192.168.0/24; };
};
zone "." {
type hint;
file "db.cache";
};
zone "0.0.127.in-addr.arpa" {
type master;
file "db.127.0.0";
};
zone "localhost" {
type master;
file "db.localhost";
};
zone "0.106.190.208.in-addr.arpa" {
type master;
file "db.208.190.106.0";
allow-transfer { 151.164.1.1; 151.164.1.7; };
};
zone "aragonsworld.net" IN {
type master;
file "db.aranet";
allow-transfer { 151.164.1.1; 151.164.1.7; };
};
zone "aragonsworld.com" IN {
type master;
file "db.aracom";
allow-transfer { 151.164.1.1; 151.164.1.7; };
};
zone "billsbestbenefits.com" IN {
type master;
file "db.bills";
allow-transfer { 151.164.1.1; 151.164.1.7; };
};
zone "khorelia.com" IN {
type master;
file "db.debs";
allow-transfer { 66.137.140.185; };
};
zone "nwrcc.com" IN {
type master;
file "db.nwrcc";
allow-transfer { 66.137.140.185; };
};
zone "e-commhouston.com" IN {
type master;
file "db.ecom";
allow-transfer { 151.164.1.1; 151.164.1.7; };
};
zone "houston-we-love-you.com" IN {
type master;
file "db.houluv";
allow-transfer { 151.164.1.1; 151.164.1.7; };
};
zone "houston-family-enterprises.com" IN {
type master;
file "db.houfam";
allow-transfer { 151.164.1.1; 151.164.1.7; };
};
zone "veegersoft.com" IN {
type master;
file "db.veegersoft";
allow-transfer { 151.164.1.1; 151.164.1.7; };
};
zone "totallyautomatichomebusiness.com" IN {
type master;
file "db.totally";
allow-transfer { 151.164.1.1; 151.164.1.7; };
};
logging {
category lame-servers {
default_syslog;
};
category xfer-out {
default_syslog;
};
category cname {
default_syslog;
};
};
===============
My friend said that the localhost zone file would help with 'reverse lookups'
What am I doing wrong?
This is the syslog error entry I get now:
ns1 named[164]: sysquery: findns error (NXDOMAIN) on localhost?
...................
My domain: 'aragonsworld.net'
My nameserver: 'ns1.aragonsworld.net' (208.190.106.2)
...................
Any and all help would be appreciated immensely. :)
----- BEGIN SIGNATURE LINE -----
Be a multi-dimensional entity and co-creator with 'all that is'
Run and administer a FreeBSD server today!
System Admin...it's a nasty job but someone has to do it!
http://www.aragonsworld.net (ARAGONSWORLDNET)
aragon at aragonsworld.net
http://www.freebsd.org - The FreeBSD project
http://www.slashdot.org - News for Nerds (Stuff that matters)
----- END SIGNATURE LINE -----
More information about the bind-users
mailing list