Linux - Server This forum is for the discussion of Linux Software used in a server related context. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
04-01-2011, 01:30 AM
|
#1
|
LQ Newbie
Registered: Apr 2011
Posts: 4
Rep:
|
Domain name server installation issue in centOS
Hi All
I am trying to install domain name server on centOS.
The following errors i am getting?
=========================================================
Error in named configuration:
zone localdomain/IN: loaded serial 42
zone localhost/IN: loaded serial 42
zone 0.0.127.in-addr.arpa/IN: loaded serial 1997022700
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
zone 255.in-addr.arpa/IN: loaded serial 42
zone 0.in-addr.arpa/IN: loaded serial 42
=========================================================
i have search lot on net but i don't get any help.
can any body help me i am not very much xp in linux.
Thanks in advanced.
|
|
|
04-01-2011, 01:50 AM
|
#2
|
LQ Guru
Registered: May 2009
Location: Gibraltar, Gibraltar
Distribution: Fedora 20 with Awesome WM
Posts: 6,805
|
Hello and Welcome to LinuxQuestions,
In order to be able to help you, can you indicate what distro and version you are using, what DNS server (bind, PowerDNS, other) you are using, post relevant part of your configuration file, and check if the DNS proces is running. The more information you provide the sooner someone can answer your questions. From the error
Quote:
Error in named configuration:
|
it appears that you have an error in your configuration.
Kind regards,
Eric
|
|
|
04-01-2011, 01:53 AM
|
#3
|
LQ Guru
Registered: Jun 2004
Location: Piraeus
Distribution: Slackware
Posts: 13,220
|
You can run
Code:
named-checkconf /etc/named.conf
to check named.conf
Regards
|
|
|
04-01-2011, 02:17 AM
|
#4
|
LQ Newbie
Registered: Apr 2011
Posts: 4
Original Poster
Rep:
|
I am using bind for DNS.
|
|
|
04-02-2011, 12:57 AM
|
#5
|
LQ Newbie
Registered: Apr 2011
Posts: 4
Original Poster
Rep:
|
no one is helping me
Hello Guys,
still i am getting following errors
Error in named configuration:
zone localdomain/IN: loaded serial 42
zone localhost/IN: loaded serial 42
zone 0.0.127.in-addr.arpa/IN: loaded serial 1997022700
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
zone 255.in-addr.arpa/IN: loaded serial 42
zone 0.in-addr.arpa/IN: loaded serial 42
dns_rdata_fromtext: /var/named/test.com.zone:7: near eol: unexpected end of input
zone test.com/IN: loading master file /var/named/test.com.zone: unexpected end of input
internal/test.com/IN: unexpected end of input
dns_rdata_fromtext: /var/named/test.com.zone:7: near eol: unexpected end of input
zone test.com/IN: loading master file /var/named/test.com.zone: unexpected end of input
external/test.com/IN: unexpected end of input
Please check bellow my configuration files
named.conf
Code:
include "/etc/rndc.key";
controls {
inet 127.0.0.1 allow { localhost; } keys { "rndc-key"; };
};
options {
/* make named use port 53 for the source of all queries, to allow
* firewalls to block all ports except 53:
*/
// query-source port 53;
/* We no longer enable this by default as the dns posion exploit
has forced many providers to open up their firewalls a bit */
// Put files that named is allowed to write in the data/ directory:
directory "/var/named"; // the default
pid-file "/var/run/named/named.pid";
dump-file "data/cache_dump.db";
statistics-file "data/named_stats.txt";
/* memstatistics-file "data/named_mem_stats.txt"; */
allow-transfer {"none";};
};
logging {
/* If you want to enable debugging, eg. using the 'rndc trace' command,
* named will try to write the 'named.run' file in the $directory (/var/named").
* By default, SELinux policy does not allow named to modify the /var/named" directory,
* so put the default debug log file in data/ :
*/
channel default_debug {
file "data/named.run";
severity dynamic;
};
};
// All BIND 9 zones are in a "view", which allow different zones to be served
// to different types of client addresses, and for options to be set for groups
// of zones.
//
// By default, if named.conf contains no "view" clauses, all zones are in the
// "default" view, which matches all clients.
//
// If named.conf contains any "view" clause, then all zones MUST be in a view;
// so it is recommended to start off using views to avoid having to restructure
// your configuration files in the future.
view "localhost_resolver" {
/* This view sets up named to be a localhost resolver ( caching only nameserver ).
* If all you want is a caching-only nameserver, then you need only define this view:
*/
match-clients { 127.0.0.0/24; };
match-destinations { localhost; };
recursion yes;
zone "." IN {
type hint;
file "/var/named/named.ca";
};
/* these are zones that contain definitions for all the localhost
* names and addresses, as recommended in RFC1912 - these names should
* ONLY be served to localhost clients:
*/
include "/var/named/named.rfc1912.zones";
};
view "internal" {
/* This view will contain zones you want to serve only to "internal" clients
that connect via your directly attached LAN interfaces - "localnets" .
*/
match-clients { localnets; };
match-destinations { localnets; };
recursion yes;
zone "." IN {
type hint;
file "/var/named/named.ca";
};
// include "/var/named/named.rfc1912.zones";
// you should not serve your rfc1912 names to non-localhost clients.
// These are your "authoritative" internal zones, and would probably
// also be included in the "localhost_resolver" view above :
zone "test.com" {
type master;
file "/var/named/test.com.zone";
};
};
view "external" {
/* This view will contain zones you want to serve only to "external" clients
* that have addresses that are not on your directly attached LAN interface subnets:
*/
recursion no;
// you'd probably want to deny recursion to external clients, so you don't
// end up providing free DNS service to all takers
// all views must contain the root hints zone:
zone "." IN {
type hint;
file "/var/named/named.ca";
};
// These are your "authoritative" external zones, and would probably
// contain entries for just your web and mail servers:
// BEGIN external zone entries
zone "test.com" {
type master;
file "/var/named/test.com.zone";
};
};
test.com.zone
Code:
$TTL 14400
@ 86400 IN SOA ns1.test.com. (
2011031402 ; serial, todays date+todays
86400 ; refresh, seconds
7200 ; retry, seconds
3600000 ; expire, seconds
86400 ) ; minimum, seconds
test.com. 86400 IN NS ns1.test.com.
test.com. 86400 IN NS ns2.test.com.
test.com. IN A 204.12.231.44
localhost.test.com. IN A 127.0.0.1
test.com. IN MX 0 test.com.
www IN CNAME test.com.
ftp IN A 204.12.231.44
named.rfc1912.zones
Code:
// named.rfc1912.zones:
//
// ISC BIND named zone configuration for zones recommended by
// RFC 1912 section 4.1 : localhost TLDs and address zones
//
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; };
};
|
|
|
04-02-2011, 04:51 AM
|
#6
|
LQ Guru
Registered: Jun 2004
Location: Piraeus
Distribution: Slackware
Posts: 13,220
|
Quote:
--snip--
dns_rdata_fromtext: /var/named/test.com.zone:7: near eol: unexpected end of input
--snip--
|
You get the above error because miss the admin's email in SOA RR. Also you don't have the A RRs for ns1 and ns2.
Try the following
Code:
$TTL 14400
@ 86400 IN SOA ns1.test.com. root.test.com. (
2011031403 ; serial, todays date+todays
86400 ; refresh, seconds
7200 ; retry, seconds
3600000 ; expire, seconds
86400 ) ; minimum, seconds
test.com. IN NS ns1.test.com.
test.com. IN NS ns2.test.com.
test.com. IN MX 0 test.com.
test.com. IN A 204.12.231.44
ns1 IN A 204.12.231.44
ns2 IN A x.x.x.x
localhost.test.com. IN A 127.0.0.1
www IN CNAME test.com.
ftp IN A 204.12.231.44
Increase the serial (in red), reload and test
|
|
1 members found this post helpful.
|
04-05-2011, 09:07 AM
|
#7
|
LQ Newbie
Registered: Apr 2011
Posts: 4
Original Poster
Rep:
|
Thanks you it's works
Thanks you it's works
|
|
|
All times are GMT -5. The time now is 03:42 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|