can any troubleshoot DNS - UNIX Resources Network

UNIX Resources » Linux » Linux Forum » Linux DNS Servers » Page.1 » can any troubleshoot DNS

The content of this page is collected from Linux Forum, All copyrights and other associated rights are reserved by the original authors of the articles.

China Linux Forum(finished)

Linux Forum(finished)

FreeBSD China(finished)

LinuxForum General Chat

Linux Advocacy

Introductions

Development Release

Linux Security

Linux Software

Linux Hardware Problems

Linux Video Problems

Linux Sound Problems

Linux Networking Support

Linux Printing Support

Linux Human Interface Devices Support

Linux Data Storage Support

Linux Applications Support

Linux Installation Support

Linux Laptops Support

Linux Motherboard, Chipsets, CPU, Memory

Miscellaneous

Mandrake Linux Support

Redhat / Fedora Linux Support

Slackware Linux Support

Linux Database Servers

Linux Email Servers

Linux FTP Servers

Linux Squid Proxy Server

Linux Webmin / Usermin Help

Qmail Toaster Help

Linux Games

Windows Game Emulation

Linux Discussions

General Linux Discussions

Red Hat Linux Discussions

More Red Hat Linux Discussions

Mandrake Linux Discussions

Slackware Linux Discussions

SuSE Linux Discussions

Debian Discussions

Samba Help

Linux Security

Linux Networking

Gentoo Help

Operating System Rant Forum

Hardware Rants

can any troubleshoot DNS

[Original] [Print] [Top]

hello

i hv configured the dns server,after restarting the service named start successfully,but when i give the command nslookup 192.168.1.2 then it displyes dat as follows:

nslookup 192.168.1.2

Server: 202.56.230.6
Address: 202.56.230.6#53

** server can't find 2.1.168.192.in-addr.arpa: NXDOMAIN

can anybody tell me where is error in DNS Server.

/var/log/messages shows error as follows:

Sep 1 17:28:54 Beta named[2663]: starting BIND 9.2.4 -u named
Sep 1 17:28:54 Beta named[2663]: using 1 CPU
Sep 1 17:28:54 Beta named: named startup succeeded
Sep 1 17:28:54 Beta named[2663]: loading configuration from '/etc/named.conf'
Sep 1 17:28:54 Beta named[2663]: none:0: open: /etc/named.conf: permission denied
Sep 1 17:28:54 Beta named[2663]: loading configuration: permission denied
Sep 1 17:28:54 Beta named[2663]: exiting (due to fatal error)

Configuration files r as follows: Named.conf

//
// named.conf for Red Hat caching-nameserver
//

options {
directory "/var/named/";
forwarders { 202.56.230.6; };
forward only;
dump-file "/var/named/data/cache_dump.db";
statistics-file "/var/named/data/named_stats.txt";
/*
* 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
//
controls {
inet 127.0.0.1 port 953 allow { localhost; } keys { rndckey; };
};

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 "beta1.com" IN {
type master;
file "beta1.com.zone";
allow-update { none; };
};
zone "2.1.168.192.in-addr.arpa" IN {
type master;
file "192.168.1.2.zone";
allow-update { none; };
};
include "/etc/rndc.key";

192.168.1.2.zone

$TTL 86400
@ IN SOA beta1.com. root.beta1.com. (
4 10800 3600 604800 86400 )
IN NS beta1.com.

2.1.168.192.IN-ADDR.ARPA. IN PTR beta1.com.

beta1.com.zone

$TTL 86400
@ IN SOA beta1.com. root.beta1.com. (
2001101100 ; serial
28800 ; refresh
14400 ; retry
3600000 ; expire
0 ) ; negative

@ IN NS beta1.com.

@ IN A 192.168.1.2

beta1.com. IN A 192.168.1.2
www IN A 192.168.1.2
ftp IN A 192.168.1.2
pop IN A 192.168.1.2

www1 IN CNAME beta1.com.
www2 IN CNAME beta1.com.
www3 IN CNAME beta1.com.

@ IN MX 10 beta1.com.
beta1 IN MX 10 beta1.com.

[Original] [Print] [Top]

Subject: Re: can any troubleshoot DNS Author: pa4wdh Posted: 2006-09-02 07:57:08 Length: 542 byte(s)
[Original] [Print] [Top]
Hi. This line in your /var/log/messages: Quote Sep 1 17:28:54 Beta named[2663]: none:0: open: /etc/named.conf: permission denied It indicaties that named can not load it's configuration because the permissions on the file doens't allow it to be read. My permissions are 644, root is the owner and group name. (in ls is looks like -rw-r--r-- root root). Try to change it and see if it helps. Best regards, pa4wdh
---- The biggest difference between M$ stuff and the rest ? Most stuff is secure by design, M$ stuff is secure by accident. bash# killall gaim killall: Don't shoot the messenger ! If we have /dev/powerbutton, what would touch /dev/powerbutton do ?
[Original] [Print] [Top]

Subject: Re: can any troubleshoot DNS Author: nagzindian Posted: 2006-10-10 11:16:48 Length: 837 byte(s)
[Original] [Print] [Top]
hi in Named.conf change as the following, zone "1.168.192.in-addr.arpa" IN { type master; file "192.168.1.2.zone"; allow-update { none; }; }; include "/etc/rndc.key"; 192.168.1.2.zone $TTL 86400 @ IN SOA beta1.com. root.beta1.com. ( 4 10800 3600 604800 86400 ) IN NS beta1.com. 2 IN PTR beta1.com. beta1.com.zone $TTL 86400 @ IN SOA beta1.com. root.beta1.com. ( 2001101100 ; serial 28800 ; refresh 14400 ; retry 3600000 ; expire 0 ) ; negative IN NS beta1.com. www IN A 192.168.1.2 ftp IN A 192.168.1.2 pop IN A 192.168.1.2 www1 IN CNAME www www2 IN CNAME www www3 IN CNAME www
[Original] [Print] [Top]

« Previous thread
SuSE DNS server does not resolve

Linux DNS Servers
Page. 1

Next thread »
Basic NAS Questions

Web	unixresources.net

This page created on 2007-08-01 12:06:53, cost 0.064011812210083 ms.