November 24, 2024, 11:07:51 PM

News : LinuxSolved.com Linux Help Community Forum..


Author Topic: nslookup ** server can't find homelan.home: SERVFAIL  (Read 14586 times)

Offline heals1ic

  • New Member
  • Posts: 1
nslookup ** server can't find homelan.home: SERVFAIL
« on: May 12, 2005, 07:39:35 AM »
I have setup a network at home and given it a domain name of "homelan.home".  The network consists of 2 windows xp machines and a fedora core 3 server running bind and httpd.  

When I run an nslookup for the domain homelan.home or for that matter whenever I run just nslookup from a windows machine I receive this message:

Code: [Select]

#nslookup
> homelan.home
Server:         127.0.0.1
Address:        127.0.0.1#53

** server can't find homelan.home: SERVFAIL


I have also setup 2 virtaul servers in apache that I still cant get to work either.  At this point I am still blaming bind.

Does anyone know what I am doing wrong?  I have been through at least 10 bind setup tutorials and I still cant seem to get it working propery.

Thanks in advance.

I have setup the named.conf file as follows:

Code: [Select]

//
// named.conf
//

options {
directory "/var/named";
dump-file "/var/named/data/cache_dump.db";
        statistics-file "/var/named/data/named_stats.txt";
// multiple-cnames 1;
auth-nxdomain no;
/*
* 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;
};

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

zone "localdomain" IN {
type master;
file "localdomain.zone";
allow-update { none; };
};

zone "localhost" IN {
type master;
file "localhost.zone";
allow-update { none; };
};

zone "0.0.127.in-addr.arpa" IN {
type master;
file "named.local";
allow-update { none; };
};

zone "0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa" IN {
        type master;
file "named.ip6.local";
allow-update { none; };
};

zone "255.in-addr.arpa" IN {
type master;
file "named.broadcast";
allow-update { none; };
};

zone "0.in-addr.arpa" IN {
type master;
file "named.zero";
allow-update { none; };
};

zone "homelan.home" IN {
type master;
allow-query { any; }; //192.168.1.0/24; };
allow-update { none; };
file "homelan.home.db";
};

zone "1.168.192.in-addr.arpa" IN {
type master;
file "homelan.home.rr.zone";
allow-update { none; };
};

include "/etc/rndc.key";


the homelan.home.db file is as follows:

Code: [Select]

$ORIGIN .
$TTL 1H
homelan.home. SOA fedora3.homelan.home. root.homelan.home. (
1
3H
1H
1W
1H
)

IN A 192.168.1.254

$ORIGIN homelan.home.
localhost IN A 127.0.0.1
fedora3 IN A 192.168.1.254

homelan.home. IN NS fedora3

www IN CNAME fedora3
dib2 IN CNAME fedora3
abbey IN CNAME fedora3
mail IN CNAME fedora3
IN MX 10 mail


the reverse lookup zone file is as follows:

Code: [Select]

;
; Reverse Zone file for homelan.home
;
;
$ORIGIN 1.168.192.in-addr.arpa
$TTL 3D

@       IN      SOA     fedora3.homelan.home. root.homelan.home. (

                        200211152       ; serial#
                        3600            ; refresh, seconds
                        3600            ; retry, seconds
                        3600            ; expire, seconds
                        3600 )          ; minimum, seconds
;

IN NS      fedora3.homelan.home.             ; Inet Address of nameserver

;

254 IN PTR mail.homelan.home.
254 IN PTR abbey.homelan.home.
254 IN PTR dib2.homelan.home.


Copy of relevant system.log

Code: [Select]

May 12 10:03:28 fedora3 named[11159]: starting BIND 9.2.5 -u named -t /var/named/chroot
May 12 10:03:28 fedora3 named[11159]: using 1 CPU
May 12 10:03:28 fedora3 named[11159]: loading configuration from '/etc/named.conf'
May 12 10:03:28 fedora3 named[11159]: listening on IPv4 interface lo, 127.0.0.1#53
May 12 10:03:28 fedora3 named[11159]: listening on IPv4 interface eth0, 192.168.1.254#53
May 12 10:03:28 fedora3 named[11159]: command channel listening on 127.0.0.1#953
May 12 10:03:28 fedora3 named[11159]: command channel listening on ::1#953
May 12 10:03:28 fedora3 named[11159]: zone 0.in-addr.arpa/IN: loaded serial 42
May 12 10:03:28 fedora3 named[11159]: zone 0.0.127.in-addr.arpa/IN: loaded serial 1997022700
May 12 10:03:28 fedora3 named[11159]: dns_master_load: homelan.home.rr.zone:18: 1.168.192.in-addr.arpa.1.168.192.in-addr.arpa: not at top of zone
May 12 10:03:28 fedora3 named[11159]: zone 1.168.192.in-addr.arpa/IN: loading master file homelan.home.rr.zone: not at top of zone
May 12 10:03:28 fedora3 named[11159]: zone 255.in-addr.arpa/IN: loaded serial 42
May 12 10:03:28 fedora3 named[11159]: zone 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa/IN: loaded serial 1997022700
May 12 10:03:28 fedora3 named[11159]: dns_master_load: homelan.home.db:23: mail.homelan.home: CNAME and other data
May 12 10:03:28 fedora3 named[11159]: zone homelan.home/IN: loading master file homelan.home.db: CNAME and other data
May 12 10:03:28 fedora3 named[11159]: zone localdomain/IN: loaded serial 42
May 12 10:03:28 fedora3 named[11159]: zone localhost/IN: loaded serial 42
May 12 10:03:28 fedora3 named: named startup succeeded
May 12 10:03:28 fedora3 named[11159]: running

Offline gauravbajaj

  • LST CareTaker
  • Experienced
  • *****
  • Posts: 658
nslookup ** server can't find homelan.home: SERVFAIL
« Reply #1 on: May 16, 2005, 11:50:27 AM »
Do one thing
make only 1 reverse entry in /etc/named.conf file...............
Forward entries may be more then 1 but reverse ia always one...
so delete others entries...........>After that it will work

Gaurav