LinuxQuestions.org
Go Job Hunting at the LQ Job Marketplace
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
Reload this Page nslookup ** server can't find homelan.home: SERVFAIL
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices

Reply
 
LinkBack Search this Thread
Old 05-11-2005, 07:31 PM   #1
heals1ic
Member
 
Registered: Jul 2004
Location: Sydney, Australia
Distribution: WinXP, Fedora Core 3/4
Posts: 36

Rep: Reputation: 15
nslookup ** server can't find homelan.home: SERVFAIL

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:
#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:
//
// 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:
$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:
;
; 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:
May 12 17:43:35 fedora3 named:  succeeded
May 12 17:43:38 fedora3 named[25744]: starting BIND 9.2.5 -u named -t /var/named/chroot
May 12 17:43:38 fedora3 named[25744]: using 1 CPU
May 12 17:43:38 fedora3 named[25744]: loading configuration from '/etc/named.conf'
May 12 17:43:38 fedora3 named[25744]: listening on IPv4 interface lo, 127.0.0.1#53
May 12 17:43:38 fedora3 named[25744]: listening on IPv4 interface eth0, 192.168.1.254#53
May 12 17:43:38 fedora3 named[25744]: command channel listening on 127.0.0.1#953
May 12 17:43:38 fedora3 named[25744]: command channel listening on ::1#953
May 12 17:43:38 fedora3 named[25744]: zone 0.in-addr.arpa/IN: loaded serial 42
May 12 17:43:38 fedora3 named[25744]: zone 0.0.127.in-addr.arpa/IN: loaded serial 1997022700
May 12 17:43:38 fedora3 named[25744]: zone 1.168.192.in-addr.arpa/IN: loaded serial 200211152
May 12 17:43:38 fedora3 named[25744]: zone 255.in-addr.arpa/IN: loaded serial 42
May 12 17:43:38 fedora3 named[25744]: 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 17:43:38 fedora3 named[25744]: dns_master_load: homelan.home.db:23: mail.homelan.home: CNAME and other data
May 12 17:43:38 fedora3 named[25744]: zone homelan.home/IN: loading master file homelan.home.db: CNAME and other data
May 12 17:43:38 fedora3 named[25744]: zone localdomain/IN: loaded serial 42
May 12 17:43:38 fedora3 named[25744]: zone localhost/IN: loaded serial 42
May 12 17:43:38 fedora3 named: named startup succeeded
May 12 17:43:38 fedora3 named[25744]: running
Last edited by heals1ic; 05-12-2005 at 02:44 AM.
 
Old 05-11-2005, 07:43 PM   #2
AltF4
Member
 
Registered: Sep 2002
Location: .at
Distribution: SuSE, Knoppix
Posts: 532

Rep: Reputation: 30
do a: "nslookup homelan.home."

mind the "." at the end

if you don't add the dot at the end, nslookup will add your default search domains from /etc/resolv.conf
 
Old 05-11-2005, 07:46 PM   #3
heals1ic
Member
 
Registered: Jul 2004
Location: Sydney, Australia
Distribution: WinXP, Fedora Core 3/4
Posts: 36

Original Poster
Rep: Reputation: 15
Tried "nslookup homelan.home." and I get the same response.

I have appended the system log for starting named if this helps.

cheers.
 
Old 05-15-2005, 05:18 AM   #4
AltF4
Member
 
Registered: Sep 2002
Location: .at
Distribution: SuSE, Knoppix
Posts: 532

Rep: Reputation: 30
-) any firewall active ?
-) try "dig @127.0.0.1 homelan.home."
 
Old 05-18-2005, 11:38 AM   #5
XOR007
Member
 
Registered: May 2005
Location: Africa
Distribution: Ubuntu, Redhat 6.2 to 9, Centos 4, Suse 8 Ent.,Suse 9 Ent.
Posts: 51

Rep: Reputation: 15
Hi,

I am new to bind, but I have seen many times warnings not to associate CNAME records for MXes
(mail exchangers) or else bind fails completely. Then even your virtual hosts won't work.

homelan.home. IN NS fedora3

www IN CNAME fedora3
dib2 IN CNAME fedora3
abbey IN CNAME fedora3
mail IN CNAME fedora3 <------- problem !
IN MX 10 mail <------problem !

Hope this helps.
 
Old 05-18-2005, 07:03 PM   #6
heals1ic
Member
 
Registered: Jul 2004
Location: Sydney, Australia
Distribution: WinXP, Fedora Core 3/4
Posts: 36

Original Poster
Rep: Reputation: 15
Thanks for your tips!

I have deleted the cname and changed the mx record to
Code:
homelan.home.     IN      MX  10   mail.homelan.home.
and added an A record :
Code:
mail		IN	A	192.168.1.254
and now get these results from the fedora3 box:

Code:
[root@fedora3 html]# ping www.homelan.home
PING fedora3.homelan.home (192.168.1.254) 56(84) bytes of data.
64 bytes from mail.homelan.home (192.168.1.254): icmp_seq=0 ttl=64 time=0.047 ms
--- fedora3.homelan.home ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.047/0.047/0.047/0.000 ms, pipe 2

[root@fedora3 html]# ping www.homelan.home
PING fedora3.homelan.home (192.168.1.254) 56(84) bytes of data.
64 bytes from dib2.homelan.home (192.168.1.254): icmp_seq=0 ttl=64 time=0.057 ms
--- fedora3.homelan.home ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 0.057/0.061/0.065/0.004 ms, pipe 2

[root@fedora3 html]# ping www.homelan.home
PING fedora3.homelan.home (192.168.1.254) 56(84) bytes of data.
64 bytes from abbey.homelan.home (192.168.1.254): icmp_seq=0 ttl=64 time=0.049 ms
--- fedora3.homelan.home ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.049/0.049/0.049/0.000 ms, pipe 2

[root@fedora3 html]# ping www.homelan.home
PING fedora3.homelan.home (192.168.1.254) 56(84) bytes of data.
64 bytes from mail.homelan.home (192.168.1.254): icmp_seq=0 ttl=64 time=0.051 ms
--- fedora3.homelan.home ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.051/0.051/0.051/0.000 ms, pipe 2
It seems odd that the return icmp packets are comming from other cnames?

In fact when I run seperate pings on the same address consecutively I seem to get icmp responses from random cnames?

Any ideas as to why?

This will play havoc with my virtual servers for apache.
Last edited by heals1ic; 05-18-2005 at 09:18 PM.
 
Old 05-18-2005, 11:03 PM   #7
scowles
Member
 
Registered: Sep 2004
Location: Texas, USA
Distribution: Fedora
Posts: 620

Rep: Reputation: 30
In fact when I run seperate pings on the same address consecutively I seem to get icmp responses from random cnames?

You have multiple names assigned to the same IP in your reverse zone. i.e. round-robin
Code:
254	IN	PTR	mail.homelan.home.
254	IN	PTR	abbey.homelan.home.
254	IN	PTR	dib2.homelan.home.
Choose only one PTR record and delete the others. BTW: PTR records "should" point to A records, not CNAMES.
 
Old 05-19-2005, 07:20 PM   #8
heals1ic
Member
 
Registered: Jul 2004
Location: Sydney, Australia
Distribution: WinXP, Fedora Core 3/4
Posts: 36

Original Poster
Rep: Reputation: 15
Muchos Gracias guys.

It seems dns is sorted :-)

Now I have to figure out why my virtual servers are all providing the default apache test page instead of the document roots I have instructed.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
NAMED (SERVFAIL message) overlord73 Linux - Software 1 01-30-2006 11:29 PM
nslookup gives "connection timed out; no server could be reached" hello321_1999 Linux - Networking 3 11-26-2004 11:23 AM
homelan timecontrol ??? PeO Linux - Newbie 0 09-02-2003 03:41 AM
2(SERVFAIL) error? GraemeK Linux - Networking 7 08-21-2003 11:45 AM
NSlookup with DNS server piglingz Linux - Networking 1 04-08-2003 09:46 AM


All times are GMT -5. The time now is 01:40 AM.

Contact Us - Advertising Info - Rules - LQ Merchandise - Donations - Contributing Member - LQ Sitemap -
Main Menu
 
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: @linuxquestions
Open Source Consulting | Domain Registration