Re:setting up bind(sorry)

Re:setting up bind(sorry)

[gracecott]

[-- Attachment #1: Type: text/plain, Size: 378 bytes --]

Hello again :-( ,

I did what Ahsan told me to do
and ran named-checkzone on db.pcm.com
and it gives me an error:

no current owner name

and no OK (obviously) after finising up.

I would've read up more before I asked this but 
I have 4 days before my 4 Sem.,  exams and really can't read up
too much now and would like to get this up before D-day.

Thanx in advance,
Joy.M.M 

[-- Attachment #2: Attached file: db.192 --]
[-- Type: application/octet-stream, Size: 354 bytes --]

$TTL 604800
@		IN SOA parrot.pcm.com.	root.pcm.com.(
			204774084	;serial
			604800		; Refresh
			  86400		; Retry
			2419200		; Expire
			 604800 )	; Negative Cache TTL
;

@	NS	parrot.pcm.com

16.2.168	IN	PTR	parrot.pcm.com.
11.2.168	IN	PTR	eagle.pcm.com.
14.2.168	IN	PTR	swan1.pcm.com.
15.2.168	IN	PTR	swan2.pcm.com.
13.2.168	IN	PTR	peacock.pcm.com.



[-- Attachment #3: Attached file: db.pcm.com --]
[-- Type: application/octet-stream, Size: 436 bytes --]

$TTL 86400
 @   1D	IN SOA parrot.pcm.com.	root.pcm.com.(
 			20384765 ;serial
			10000	;refresh
			500	;retry
			2419200 ; expire
			604800	);negative TTL
;

@		604800	IN	NS	parrot.pcm.com.
parrot.pcm.com.		604800	IN	A	192.168.2.16	

eagle.pcm.com.		604800	IN	A	192.168.2.11
swan1.pcm.com.		604800	IN	A	192.168.2.14
swan2.pcm.com.		604800	IN	A	192.168.2.15
peacock.pcm.com.	604800	IN	A	192.168.2.13
pcm.com.		7155	IN	A	209.233.130.34



[-- Attachment #4: Attached file: named.conf --]
[-- Type: application/octet-stream, Size: 1085 bytes --]

// This is the primary configuration file for the BIND DNS server named.
//
// Please read /usr/share/doc/bind9/README.Debian.gz for information on the 
// structure of BIND configuration files in Debian, *BEFORE* you customize 
// this configuration file.
//
// If you are just adding zones, please do that in /etc/bind/named.conf.local

include "/etc/bind/named.conf.options";

// prime the server with knowledge of the root servers
zone "." {
	type hint;
	file "/etc/bind/db.root";
};

// be authoritative for the localhost forward and reverse zones, and for
// broadcast zones as per RFC 1912

zone "localhost" {
	type master;
	file "/etc/bind/db.local";
};

zone "127.in-addr.arpa" {
	type master;
	file "/etc/bind/db.127";
};

zone "0.in-addr.arpa" {
	type master;
	file "/etc/bind/db.0";
};

zone "255.in-addr.arpa" {
	type master;
	file "/etc/bind/db.255";
};

//zone "com" { type delegation-only; };
zone "net" { type delegation-only; };


zone "pcm.com" IN{
	type master;
	file "/etc/bind/db.pcm.com";
};

zone "192.in-addr.arpa"{
	type master;
	file "/etc/bind/db.192";
};

Re: Re:setting up bind(sorry)

[Richard Nairn]

no current owner name
In your named logs, "no current owner name" means that that zone doesn't  
have a valid SOA.

In your db.pcm.com, your file start with
@ 1D SOA ...

I think the problem is the "1D" that you have in your file.. See if that  
makes any difference.  Could be a typo in there, or a control character of  
some sort?



On Fri, 09 Jul 2004 12:19:12 +0530 (GMT+05:30), <gracecott@sancharnet.in>  
wrote:

> Hello again :-( ,
>
> I did what Ahsan told me to do
> and ran named-checkzone on db.pcm.com
> and it gives me an error:
>
> no current owner name
>
> and no OK (obviously) after finising up.
>
> I would've read up more before I asked this but
> I have 4 days before my 4 Sem.,  exams and really can't read up
> too much now and would like to get this up before D-day.
>
> Thanx in advance,
> Joy.M.M



-- 
|       Richard Nairn          Specializing in Linux
|     Nairn Consulting         Web / Database Solutions
|        Calgary, AB
| Richard@NairnConsulting.ca

Re: Re:setting up bind(sorry)

[Glynn Clements]

Richard Nairn wrote:

> In your db.pcm.com, your file start with
> @ 1D SOA ...
> 
> I think the problem is the "1D" that you have in your file.. See if that  
> makes any difference.  Could be a typo in there, or a control character of  
> some sort?

"1D" means a TTL of one day.

However, there appears to be a space at the start of the first line of
the SOA record, which will cause problems.

-- 
Glynn Clements <glynn.clements@virgin.net>