svn commit: r240807 - in stable/9/contrib/bind9: . lib/dns lib/dns/include/dns
Hi This morning at about 7 am, I noticed to commits to stable/9 that I wanted to pull in and so did and then rebuilt from source. Just now, I noticed this: svn commit: r240807 - in stable/9/contrib/bind9: . lib/dns lib/dns/include/dns I really can't be bother to requildworld again, can I just go into /usr/src/contrib/bind9 and make, build, install that bit? It does affect me do I should really update to this commit, up to now i've only rebuilt the entire system from source rather than individual code commits. Cheers, Jamie ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
was the problem/problemS surrounding upgrading bind9 fixed?
Guys, I never got my old, bind9[3.X] that is past its EOL to upgrade. Pretty sure I read about the same problem I found that some others had to. Am I misinformed? thanks in advance. gary -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix Journey Toward the Dawn, E-Book: http://www.thought.org The 7.98a release of Jottings: http://jottings.thought.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: reverse dns in bind9
hey guys, ok I fixed the reverse zone file and now it's working perfectly! @ IN SOA ns1.summitnjhome.com. bluethundr.gmail.com. ( 2011032901 ;serial 14400 ;refresh 3600 ;retry 604800 ;expire 10800;minimum ) 1.168.192.in-addr.arpa.IN NS ns1.yournameserver.com. 42 IN PTR LCENT01.summitnjhome.com. 43 IN PTR LCENT03.summitnjhome.com. 44 IN PTR LBSD2.summitnjhome.com. LBSD2# host 192.168.1.42 42.1.168.192.in-addr.arpa domain name pointer LCENT01.summitnjhome.com. On Tue, Mar 29, 2011 at 12:25 AM, Jon Radel j...@radel.com wrote: On 3/29/11 12:05 AM, Tim Dunphy wrote: hello no crabby comments on restart at all! LBSD2# /etc/rc.d/named restart Stopping named. Waiting for PIDS: 4970. Starting named. Ah but yes some complaints from the logs Mar 29 04:59:47 LBSD2 named[5469]: master/summitnjhome-reverse.db:10: ignoring out-of-zone data (summitnjhome.com) Mar 29 04:59:47 LBSD2 named[5469]: dns_master_load: master/summitnjhome-reverse.db:11: unexpected end of line Mar 29 04:59:47 LBSD2 named[5469]: dns_master_load: master/summitnjhome-reverse.db:10: unexpected end of input Mar 29 04:59:47 LBSD2 named[5469]: zone 1.168.192.in-addr.arpa/IN: loading from master file master/summitnjhome-reverse.db failed: unexpected end of input Mar 29 04:59:47 LBSD2 named[5469]: zone 1.168.192.in-addr.arpa/IN: not loaded due to errors. Mar 29 04:59:47 LBSD2 named[5469]: running Tho I am not sure why it's complaining about unexpected end of input this is the whole file Really? Judging from the line numbers in the log messages, you're missing about 3 lines that, I would hope, include something like IN SOA ns1.summitnjhome.com bluethunder.gmail.com ( 201103271 ; Serial, todays date + todays serial 8H ; Refresh 2H ; Retry 4W ; Expire 1D) ; Minimum TTL NS ns1.summitnjhome.com. summitnjhome.com. doesn't make much sense as data in this zone, error message 1 ^ Whoa, Nelly, where's the rest of this line? error message 2 Oh, never mind, I'm so out of here.ignore all that stuff below, messages 3 and 4 42 PTR LCENT01.summitnjhome.com. 43 PTR LCENT02.summitnjhome.com. 44 PTR LBSD2.summitnjhome.com. 45 PTR LCENT02.summitnjhome.com. 46 PTR LCENT03.summitnjhome.com. 47 PTR LCENT04.summitnjhome.com. 23 PTR virtcent01.summitnjhome.com. 24 PTR virtcent02.summitnjhome.com. 21 PTR virtcent03.summitnjhome.com. 26 PTR virtcent04.summitnjhome.com. 27 PTR virtcent05.summitnjhome.com. 28 PTR virtcent06.summitnjhome.com. 29 PTR virtcent07.summitnjhome.com. 30 PTR virtcent08.summitnjhome.com. 31 PTR virtcent09.summitnjhome.com. 32 PTR virtcent10.summitnjhome.com. 33 PTR virtcent11.summitnjhome.com. 34 PTR virtcent12.summitnjhome.com. 35 PTR virtcent13.summitnjhome.com. 36 PTR virtcent14.summitnjhome.com. 37 PTR virtcent15.summitnjhome.com. 38 PTR virtcent16.summitnjhome.com. 39 PTR virtcent17.summitnjhome.com. 40 PTR virtcent18.summitnjhome.com. 41 PTR virtcent19.summitnjhome.com. -- --Jon Radel j...@radel.com -- GPG me!! gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: reverse dns in bind9
Hello,
Thanks for your reply!
I took your advice and removed that line from resolv.conf and added
it into /etc/named/named.conf
Now it looks like this
// RFC 1912
zone localhost{ type master; file master/localhost-forward.db; };
zone 127.in-addr.arpa { type master; file master/localhost-reverse.db; };
zone 255.in-addr.arpa { type master; file master/empty.db; };
zone 192.in-addr.arpa { type master; file master/summitjnhome-reverse.db; };
And I did a restart of both network and named but the issue remains:
LBSD2# host 192.168.1.44
Host 44.1.168.192.in-addr.arpa. not found: 3(NXDOMAIN)
On Mon, Mar 28, 2011 at 1:06 AM, Robert Bonomi bon...@mail.r-bonomi.com wrote:
Date: Mon, 28 Mar 2011 00:19:26 -0400
From: Tim Dunphy bluethu...@gmail.com
Subject: reverse dns in bind9
Hello,
I am attempting to setup reverse dns in bind 9 under freebsd... this is
in an attempt to allow mysql to work a little easier with DNS
resolution.
In my /etc/named/named.conf file I have the following:
// RFC 1912
zone localhost { type master; file master/localhost-forward.db; };
zone 127.in-addr.arpa { type master; ile master/localhost-reverse.db; };
zone 255.in-addr.arpa { type master; file master/empty.db; };
zone 192.in-addr.arpa { type master; file
master/summitjnhome-reverse.db; };
zone summitnjhome.com { type master; file master/summitnjhome.db; };
My master/summitnjhome.com looks like the following:
For starters, this should be in master/summitnjhome-reerse.db
$TTL 3D
@ IN SOA ns1.summitnjhome.com. bluethundr.gmail.com. (
201103271 ; Serial, todays date + todays serial
8H ; Refresh
2H ; Retry
4W ; Expire
1D) ; Minimum TTL
NS ns1.summitnjhome.com.
summitnjhome.com.
42 PTR LCENT01.summitnjhome.com.
43 PTR LCENT02.summitnjhome.com.
44 PTR LBSD2.summitnjhome.com.
45 PTR LCENT02.summitnjhome.com.
46 PTR LCENT03.summitnjhome.com.
47 PTR LCENT04.summitnjhome.com.
23 PTR virtcent01.summitnjhome.com.
24 PTR virtcent02.summitnjhome.com.
21 PTR virtcent03.summitnjhome.com.
26 PTR virtcent04.summitnjhome.com.
27 PTR virtcent05.summitnjhome.com.
28 PTR virtcent06.summitnjhome.com.
29 PTR virtcent07.summitnjhome.com.
30 PTR virtcent08.summitnjhome.com.
31 PTR virtcent09.summitnjhome.com.
32 PTR virtcent10.summitnjhome.com.
33 PTR virtcent11.summitnjhome.com.
34 PTR virtcent12.summitnjhome.com.
35 PTR virtcent13.summitnjhome.com.
36 PTR virtcent14.summitnjhome.com.
37 PTR virtcent15.summitnjhome.com.
38 PTR virtcent16.summitnjhome.com.
39 PTR virtcent17.summitnjhome.com.
40 PTR virtcent18.summitnjhome.com.
41 PTR virtcent19.summitnjhome.com.
and my /etc/resolv.conf looks like this:
domain summitnjhome.com
nameserver 192.168.1.44
nameserver 4.2.2.2
zone 1.168.192.in-addr.arpa { type master; file
/etc/named/master/summitnjhome-reverse.db
};
the 'zone' line you show should *NOT* be in resolv.conf at all.
this line should be in the named.conf file *instead* of the one for
the '192.in-addr.arpa' zone.
then I restart both named and the network service
and yet if I were to try forward resolution:
LBSD2# host sum1
sum1.summitnjhome.com is an alias for LCENT01.summitnjhome.com.
LCENT01.summitnjhome.com has address 192.168.1.42
and then reverse resolution:
LBSD2# host 192.168.1.42
Host 42.1.168.192.in-addr.arpa. not found: 3(NXDOMAIN)
I have no luck. Any thoughts on this?
see above.
--
GPG me!!
gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: reverse dns in bind9
On 3/28/11 7:21 AM, Tim Dunphy wrote:
Hello,
Thanks for your reply!
I took your advice and removed that line from resolv.conf and added
it into /etc/named/named.conf
Now it looks like this
// RFC 1912
zone localhost{ type master; file master/localhost-forward.db; };
zone 127.in-addr.arpa { type master; file master/localhost-reverse.db; };
zone 255.in-addr.arpa { type master; file master/empty.db; };
zone 192.in-addr.arpa { type master; file master/summitjnhome-reverse.db; };
And I did a restart of both network and named but the issue remains:
LBSD2# host 192.168.1.44
Host 44.1.168.192.in-addr.arpa. not found: 3(NXDOMAIN)
Nowhere do you mention that you moved all the PTR records into the
192.in-addr.arpa zone where they belong, as noted by Robert Bonomi. And
why did you change
zone 1.168.192.in-addr.arpa { type master; file
/etc/named/master/summitnjhome-reverse.db
};
to
zone 192.in-addr.arpa { type master; file
master/summitjnhome-reverse.db; };
when your PTR lines only give the last octet? Where do you expect the
168.1 to come from?
--Jon Radel
j...@radel.com
Re: reverse dns in bind9
2011/3/28 Tim Dunphy bluethu...@gmail.com
Hello,
Thanks for your reply!
I took your advice and removed that line from resolv.conf and added
it into /etc/named/named.conf
Now it looks like this
// RFC 1912
zone localhost{ type master; file master/localhost-forward.db;
};
zone 127.in-addr.arpa { type master; file master/localhost-reverse.db;
};
zone 255.in-addr.arpa { type master; file master/empty.db; };
zone 192.in-addr.arpa { type master; file
master/summitjnhome-reverse.db; };
Robert said that you should replace 192.in-addr.arpa with
1.168.192.in-addr.arpa in your named.conf.
Your named.conf should be look like the following:
zone localhost{ type master; file master/localhost-forward.db;
};
zone 127.in-addr.arpa { type master; file master/localhost-reverse.db;
};
zone 255.in-addr.arpa { type master; file master/empty.db; };
zone 1.168.192.in-addr.arpa { type master; file
master/summitjnhome-reverse.db; };
And I did a restart of both network and named but the issue remains:
LBSD2# host 192.168.1.44
Host 44.1.168.192.in-addr.arpa. not found: 3(NXDOMAIN)
On Mon, Mar 28, 2011 at 1:06 AM, Robert Bonomi bon...@mail.r-bonomi.com
wrote:
Date: Mon, 28 Mar 2011 00:19:26 -0400
From: Tim Dunphy bluethu...@gmail.com
Subject: reverse dns in bind9
Hello,
I am attempting to setup reverse dns in bind 9 under freebsd... this is
in an attempt to allow mysql to work a little easier with DNS
resolution.
In my /etc/named/named.conf file I have the following:
// RFC 1912
zone localhost { type master; file master/localhost-forward.db; };
zone 127.in-addr.arpa { type master; ile
master/localhost-reverse.db; };
zone 255.in-addr.arpa { type master; file master/empty.db; };
zone 192.in-addr.arpa { type master; file
master/summitjnhome-reverse.db; };
zone summitnjhome.com { type master; file master/summitnjhome.db;
};
My master/summitnjhome.com looks like the following:
For starters, this should be in master/summitnjhome-reerse.db
$TTL 3D
@ IN SOA ns1.summitnjhome.com. bluethundr.gmail.com. (
201103271 ; Serial, todays date + todays serial
8H ; Refresh
2H ; Retry
4W ; Expire
1D) ; Minimum TTL
NS ns1.summitnjhome.com.
summitnjhome.com.
42 PTR LCENT01.summitnjhome.com.
43 PTR LCENT02.summitnjhome.com.
44 PTR LBSD2.summitnjhome.com.
45 PTR LCENT02.summitnjhome.com.
46 PTR LCENT03.summitnjhome.com.
47 PTR LCENT04.summitnjhome.com.
23 PTR virtcent01.summitnjhome.com.
24 PTR virtcent02.summitnjhome.com.
21 PTR virtcent03.summitnjhome.com.
26 PTR virtcent04.summitnjhome.com.
27 PTR virtcent05.summitnjhome.com.
28 PTR virtcent06.summitnjhome.com.
29 PTR virtcent07.summitnjhome.com.
30 PTR virtcent08.summitnjhome.com.
31 PTR virtcent09.summitnjhome.com.
32 PTR virtcent10.summitnjhome.com.
33 PTR virtcent11.summitnjhome.com.
34 PTR virtcent12.summitnjhome.com.
35 PTR virtcent13.summitnjhome.com.
36 PTR virtcent14.summitnjhome.com.
37 PTR virtcent15.summitnjhome.com.
38 PTR virtcent16.summitnjhome.com.
39 PTR virtcent17.summitnjhome.com.
40 PTR virtcent18.summitnjhome.com.
41 PTR virtcent19.summitnjhome.com.
and my /etc/resolv.conf looks like this:
domain summitnjhome.com
nameserver 192.168.1.44
nameserver 4.2.2.2
zone 1.168.192.in-addr.arpa { type master; file
/etc/named/master/summitnjhome-reverse.db
};
the 'zone' line you show should *NOT* be in resolv.conf at all.
this line should be in the named.conf file *instead* of the one for
the '192.in-addr.arpa' zone.
then I restart both named and the network service
and yet if I were to try forward resolution:
LBSD2# host sum1
sum1.summitnjhome.com is an alias for LCENT01.summitnjhome.com.
LCENT01.summitnjhome.com has address 192.168.1.42
and then reverse resolution:
LBSD2# host 192.168.1.42
Host 42.1.168.192.in-addr.arpa. not found: 3(NXDOMAIN)
I have no luck. Any thoughts on this?
see above.
--
GPG me!!
gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
freebsd-questions-unsubscr...@freebsd.org
--
--
AP
Re: reverse dns in bind9
Ok guys.. I totally get it now and sorry for the misunderstanding. I'm
really looking forward to getting this working but might not get a
chance to try this again until this evening. time. where does it go?
don't know but I certainly appreciate yourst!
On Mon, Mar 28, 2011 at 8:01 AM, Peter Andreev andreev.pe...@gmail.com wrote:
2011/3/28 Tim Dunphy bluethu...@gmail.com
Hello,
Thanks for your reply!
I took your advice and removed that line from resolv.conf and added
it into /etc/named/named.conf
Now it looks like this
// RFC 1912
zone localhost { type master; file master/localhost-forward.db;
};
zone 127.in-addr.arpa { type master; file master/localhost-reverse.db;
};
zone 255.in-addr.arpa { type master; file master/empty.db; };
zone 192.in-addr.arpa { type master; file
master/summitjnhome-reverse.db; };
Robert said that you should replace 192.in-addr.arpa with
1.168.192.in-addr.arpa in your named.conf.
Your named.conf should be look like the following:
zone localhost { type master; file master/localhost-forward.db;
};
zone 127.in-addr.arpa { type master; file master/localhost-reverse.db;
};
zone 255.in-addr.arpa { type master; file master/empty.db; };
zone 1.168.192.in-addr.arpa { type master; file
master/summitjnhome-reverse.db; };
And I did a restart of both network and named but the issue remains:
LBSD2# host 192.168.1.44
Host 44.1.168.192.in-addr.arpa. not found: 3(NXDOMAIN)
On Mon, Mar 28, 2011 at 1:06 AM, Robert Bonomi bon...@mail.r-bonomi.com
wrote:
Date: Mon, 28 Mar 2011 00:19:26 -0400
From: Tim Dunphy bluethu...@gmail.com
Subject: reverse dns in bind9
Hello,
I am attempting to setup reverse dns in bind 9 under freebsd... this is
in an attempt to allow mysql to work a little easier with DNS
resolution.
In my /etc/named/named.conf file I have the following:
// RFC 1912
zone localhost { type master; file master/localhost-forward.db; };
zone 127.in-addr.arpa { type master; ile
master/localhost-reverse.db; };
zone 255.in-addr.arpa { type master; file master/empty.db; };
zone 192.in-addr.arpa { type master; file
master/summitjnhome-reverse.db; };
zone summitnjhome.com { type master; file master/summitnjhome.db;
};
My master/summitnjhome.com looks like the following:
For starters, this should be in master/summitnjhome-reerse.db
$TTL 3D
@ IN SOA ns1.summitnjhome.com. bluethundr.gmail.com. (
201103271 ; Serial, todays date + todays serial
8H ; Refresh
2H ; Retry
4W ; Expire
1D) ; Minimum TTL
NS ns1.summitnjhome.com.
summitnjhome.com.
42 PTR LCENT01.summitnjhome.com.
43 PTR LCENT02.summitnjhome.com.
44 PTR LBSD2.summitnjhome.com.
45 PTR LCENT02.summitnjhome.com.
46 PTR LCENT03.summitnjhome.com.
47 PTR LCENT04.summitnjhome.com.
23 PTR virtcent01.summitnjhome.com.
24 PTR virtcent02.summitnjhome.com.
21 PTR virtcent03.summitnjhome.com.
26 PTR virtcent04.summitnjhome.com.
27 PTR virtcent05.summitnjhome.com.
28 PTR virtcent06.summitnjhome.com.
29 PTR virtcent07.summitnjhome.com.
30 PTR virtcent08.summitnjhome.com.
31 PTR virtcent09.summitnjhome.com.
32 PTR virtcent10.summitnjhome.com.
33 PTR virtcent11.summitnjhome.com.
34 PTR virtcent12.summitnjhome.com.
35 PTR virtcent13.summitnjhome.com.
36 PTR virtcent14.summitnjhome.com.
37 PTR virtcent15.summitnjhome.com.
38 PTR virtcent16.summitnjhome.com.
39 PTR virtcent17.summitnjhome.com.
40 PTR virtcent18.summitnjhome.com.
41 PTR virtcent19.summitnjhome.com.
and my /etc/resolv.conf looks like this:
domain summitnjhome.com
nameserver 192.168.1.44
nameserver 4.2.2.2
zone 1.168.192.in-addr.arpa { type master; file
/etc/named/master/summitnjhome-reverse.db
};
the 'zone' line you show should *NOT* be in resolv.conf at all.
this line should be in the named.conf file *instead* of the one for
the '192.in-addr.arpa' zone.
then I restart both named and the network service
and yet if I were to try forward resolution:
LBSD2# host sum1
sum1.summitnjhome.com is an alias for LCENT01.summitnjhome.com.
LCENT01.summitnjhome.com has address 192.168.1.42
and then reverse resolution:
LBSD2# host 192.168.1.42
Host 42.1.168.192.in-addr.arpa. not found: 3(NXDOMAIN)
I have no luck. Any thoughts
Re: reverse dns in bind9
hello list,
I was able to make that correction:
zone 1.168.192.in-addr.arpa { type master; file master/summitnjhome-reverse.d
b; };
zone summitnjhome.com { type master; file master/summitnjhome.db; };
is now in named.conf. otherwise named.conf is identical to the way it
is higher up in the thread, and summitnjhome-reverse.db is untouched.
But as of now, forward lookups work, but reverse time out:
LBSD2# host sum1
sum1.summitnjhome.com is an alias for LCENT01.summitnjhome.com.
LCENT01.summitnjhome.com has address 192.168.1.42
LBSD2# nslookup sum1
Server: 192.168.1.44
Address:192.168.1.44#53
sum1.summitnjhome.com canonical name = LCENT01.summitnjhome.com.
Name: LCENT01.summitnjhome.com
Address: 192.168.1.42
LBSD2# host 192.168.1.42
;; connection timed out; no servers could be reached
LBSD2# nslookup 192.168.1.42
;; Got SERVFAIL reply from 192.168.1.44, trying next server
;; connection timed out; no servers could be reached
Now I could probably understand it FAILING due to perhaps a type-o in
the config. But I am genuinely curious as to how forward lookups will
work and reverse lookups time out.
regards
tim
On Mon, Mar 28, 2011 at 9:36 AM, Tim Dunphy bluethu...@gmail.com wrote:
Ok guys.. I totally get it now and sorry for the misunderstanding. I'm
really looking forward to getting this working but might not get a
chance to try this again until this evening. time. where does it go?
don't know but I certainly appreciate yourst!
On Mon, Mar 28, 2011 at 8:01 AM, Peter Andreev andreev.pe...@gmail.com
wrote:
2011/3/28 Tim Dunphy bluethu...@gmail.com
Hello,
Thanks for your reply!
I took your advice and removed that line from resolv.conf and added
it into /etc/named/named.conf
Now it looks like this
// RFC 1912
zone localhost { type master; file master/localhost-forward.db;
};
zone 127.in-addr.arpa { type master; file master/localhost-reverse.db;
};
zone 255.in-addr.arpa { type master; file master/empty.db; };
zone 192.in-addr.arpa { type master; file
master/summitjnhome-reverse.db; };
Robert said that you should replace 192.in-addr.arpa with
1.168.192.in-addr.arpa in your named.conf.
Your named.conf should be look like the following:
zone localhost { type master; file master/localhost-forward.db;
};
zone 127.in-addr.arpa { type master; file master/localhost-reverse.db;
};
zone 255.in-addr.arpa { type master; file master/empty.db; };
zone 1.168.192.in-addr.arpa { type master; file
master/summitjnhome-reverse.db; };
And I did a restart of both network and named but the issue remains:
LBSD2# host 192.168.1.44
Host 44.1.168.192.in-addr.arpa. not found: 3(NXDOMAIN)
On Mon, Mar 28, 2011 at 1:06 AM, Robert Bonomi bon...@mail.r-bonomi.com
wrote:
Date: Mon, 28 Mar 2011 00:19:26 -0400
From: Tim Dunphy bluethu...@gmail.com
Subject: reverse dns in bind9
Hello,
I am attempting to setup reverse dns in bind 9 under freebsd... this is
in an attempt to allow mysql to work a little easier with DNS
resolution.
In my /etc/named/named.conf file I have the following:
// RFC 1912
zone localhost { type master; file master/localhost-forward.db; };
zone 127.in-addr.arpa { type master; ile
master/localhost-reverse.db; };
zone 255.in-addr.arpa { type master; file master/empty.db; };
zone 192.in-addr.arpa { type master; file
master/summitjnhome-reverse.db; };
zone summitnjhome.com { type master; file master/summitnjhome.db;
};
My master/summitnjhome.com looks like the following:
For starters, this should be in master/summitnjhome-reerse.db
$TTL 3D
@ IN SOA ns1.summitnjhome.com. bluethundr.gmail.com. (
201103271 ; Serial, todays date + todays serial
8H ; Refresh
2H ; Retry
4W ; Expire
1D) ; Minimum TTL
NS ns1.summitnjhome.com.
summitnjhome.com.
42 PTR LCENT01.summitnjhome.com.
43 PTR LCENT02.summitnjhome.com.
44 PTR LBSD2.summitnjhome.com.
45 PTR LCENT02.summitnjhome.com.
46 PTR LCENT03.summitnjhome.com.
47 PTR LCENT04.summitnjhome.com.
23 PTR virtcent01.summitnjhome.com.
24 PTR virtcent02.summitnjhome.com.
21 PTR virtcent03.summitnjhome.com.
26 PTR virtcent04.summitnjhome.com.
27 PTR virtcent05.summitnjhome.com.
28 PTR virtcent06.summitnjhome.com.
29 PTR virtcent07.summitnjhome.com.
30 PTR virtcent08.summitnjhome.com.
31 PTR virtcent09.summitnjhome.com.
32 PTR virtcent10.summitnjhome.com.
33 PTR virtcent11.summitnjhome.com.
34 PTR
Re: reverse dns in bind9
On 3/28/11 11:36 PM, Tim Dunphy wrote: Now I could probably understand it FAILING due to perhaps a type-o in the config. But I am genuinely curious as to how forward lookups will work and reverse lookups time out. I would expect them to time out if your dns server knows nothing about the reverse zone; give or take how you connect to the rest of the DNS. What messages about zones loading did you get when you restarted bind? Where there any crabby comments in the log file about not loading master/summitnjhome-reverse.db due to error(s)? Was that file mentioned at all? --Jon Radel j...@radel.com
Re: reverse dns in bind9
hello no crabby comments on restart at all! LBSD2# /etc/rc.d/named restart Stopping named. Waiting for PIDS: 4970. Starting named. Ah but yes some complaints from the logs Mar 29 04:59:47 LBSD2 named[5469]: master/summitnjhome-reverse.db:10: ignoring out-of-zone data (summitnjhome.com) Mar 29 04:59:47 LBSD2 named[5469]: dns_master_load: master/summitnjhome-reverse.db:11: unexpected end of line Mar 29 04:59:47 LBSD2 named[5469]: dns_master_load: master/summitnjhome-reverse.db:10: unexpected end of input Mar 29 04:59:47 LBSD2 named[5469]: zone 1.168.192.in-addr.arpa/IN: loading from master file master/summitnjhome-reverse.db failed: unexpected end of input Mar 29 04:59:47 LBSD2 named[5469]: zone 1.168.192.in-addr.arpa/IN: not loaded due to errors. Mar 29 04:59:47 LBSD2 named[5469]: running Tho I am not sure why it's complaining about unexpected end of input this is the whole file 201103271 ; Serial, todays date + todays serial 8H ; Refresh 2H ; Retry 4W ; Expire 1D) ; Minimum TTL NS ns1.summitnjhome.com. summitnjhome.com. 42 PTR LCENT01.summitnjhome.com. 43 PTR LCENT02.summitnjhome.com. 44 PTR LBSD2.summitnjhome.com. 45 PTR LCENT02.summitnjhome.com. 46 PTR LCENT03.summitnjhome.com. 47 PTR LCENT04.summitnjhome.com. 23 PTR virtcent01.summitnjhome.com. 24 PTR virtcent02.summitnjhome.com. 21 PTR virtcent03.summitnjhome.com. 26 PTR virtcent04.summitnjhome.com. 27 PTR virtcent05.summitnjhome.com. 28 PTR virtcent06.summitnjhome.com. 29 PTR virtcent07.summitnjhome.com. 30 PTR virtcent08.summitnjhome.com. 31 PTR virtcent09.summitnjhome.com. 32 PTR virtcent10.summitnjhome.com. 33 PTR virtcent11.summitnjhome.com. 34 PTR virtcent12.summitnjhome.com. 35 PTR virtcent13.summitnjhome.com. 36 PTR virtcent14.summitnjhome.com. 37 PTR virtcent15.summitnjhome.com. 38 PTR virtcent16.summitnjhome.com. 39 PTR virtcent17.summitnjhome.com. 40 PTR virtcent18.summitnjhome.com. 41 PTR virtcent19.summitnjhome.com. tim On Mon, Mar 28, 2011 at 11:54 PM, Jon Radel j...@radel.com wrote: On 3/28/11 11:36 PM, Tim Dunphy wrote: Now I could probably understand it FAILING due to perhaps a type-o in the config. But I am genuinely curious as to how forward lookups will work and reverse lookups time out. I would expect them to time out if your dns server knows nothing about the reverse zone; give or take how you connect to the rest of the DNS. What messages about zones loading did you get when you restarted bind? Where there any crabby comments in the log file about not loading master/summitnjhome-reverse.db due to error(s)? Was that file mentioned at all? --Jon Radel j...@radel.com -- GPG me!! gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: reverse dns in bind9
On 3/29/11 12:05 AM, Tim Dunphy wrote: hello no crabby comments on restart at all! LBSD2# /etc/rc.d/named restart Stopping named. Waiting for PIDS: 4970. Starting named. Ah but yes some complaints from the logs Mar 29 04:59:47 LBSD2 named[5469]: master/summitnjhome-reverse.db:10: ignoring out-of-zone data (summitnjhome.com) Mar 29 04:59:47 LBSD2 named[5469]: dns_master_load: master/summitnjhome-reverse.db:11: unexpected end of line Mar 29 04:59:47 LBSD2 named[5469]: dns_master_load: master/summitnjhome-reverse.db:10: unexpected end of input Mar 29 04:59:47 LBSD2 named[5469]: zone 1.168.192.in-addr.arpa/IN: loading from master file master/summitnjhome-reverse.db failed: unexpected end of input Mar 29 04:59:47 LBSD2 named[5469]: zone 1.168.192.in-addr.arpa/IN: not loaded due to errors. Mar 29 04:59:47 LBSD2 named[5469]: running Tho I am not sure why it's complaining about unexpected end of input this is the whole file Really? Judging from the line numbers in the log messages, you're missing about 3 lines that, I would hope, include something like IN SOA ns1.summitnjhome.com bluethunder.gmail.com ( 201103271 ; Serial, todays date + todays serial 8H ; Refresh 2H ; Retry 4W ; Expire 1D) ; Minimum TTL NS ns1.summitnjhome.com. summitnjhome.com. doesn't make much sense as data in this zone, error message 1 ^ Whoa, Nelly, where's the rest of this line? error message 2 Oh, never mind, I'm so out of here.ignore all that stuff below, messages 3 and 4 42 PTR LCENT01.summitnjhome.com. 43 PTR LCENT02.summitnjhome.com. 44 PTR LBSD2.summitnjhome.com. 45 PTR LCENT02.summitnjhome.com. 46 PTR LCENT03.summitnjhome.com. 47 PTR LCENT04.summitnjhome.com. 23 PTR virtcent01.summitnjhome.com. 24 PTR virtcent02.summitnjhome.com. 21 PTR virtcent03.summitnjhome.com. 26 PTR virtcent04.summitnjhome.com. 27 PTR virtcent05.summitnjhome.com. 28 PTR virtcent06.summitnjhome.com. 29 PTR virtcent07.summitnjhome.com. 30 PTR virtcent08.summitnjhome.com. 31 PTR virtcent09.summitnjhome.com. 32 PTR virtcent10.summitnjhome.com. 33 PTR virtcent11.summitnjhome.com. 34 PTR virtcent12.summitnjhome.com. 35 PTR virtcent13.summitnjhome.com. 36 PTR virtcent14.summitnjhome.com. 37 PTR virtcent15.summitnjhome.com. 38 PTR virtcent16.summitnjhome.com. 39 PTR virtcent17.summitnjhome.com. 40 PTR virtcent18.summitnjhome.com. 41 PTR virtcent19.summitnjhome.com. -- --Jon Radel j...@radel.com
reverse dns in bind9
Hello,
I am attempting to setup reverse dns in bind 9 under freebsd... this
is in an attempt to allow mysql to work a little easier with DNS
resolution.
In my /etc/named/named.conf file I have the following:
// RFC 1912
zone localhost{ type master; file master/localhost-forward.db; };
zone 127.in-addr.arpa { type master; file master/localhost-reverse.db; };
zone 255.in-addr.arpa { type master; file master/empty.db; };
zone 192.in-addr.arpa { type master; file master/summitjnhome-reverse.db; };
zone summitnjhome.com { type master; file master/summitnjhome.db; };
My master/summitnjhome.com looks like the following:
$TTL 3D
@ IN SOA ns1.summitnjhome.com. bluethundr.gmail.com. (
201103271 ; Serial, todays date + todays serial
8H ; Refresh
2H ; Retry
4W ; Expire
1D) ; Minimum TTL
NS ns1.summitnjhome.com.
summitnjhome.com.
42 PTR LCENT01.summitnjhome.com.
43 PTR LCENT02.summitnjhome.com.
44 PTR LBSD2.summitnjhome.com.
45 PTR LCENT02.summitnjhome.com.
46 PTR LCENT03.summitnjhome.com.
47 PTR LCENT04.summitnjhome.com.
23 PTR virtcent01.summitnjhome.com.
24 PTR virtcent02.summitnjhome.com.
21 PTR virtcent03.summitnjhome.com.
26 PTR virtcent04.summitnjhome.com.
27 PTR virtcent05.summitnjhome.com.
28 PTR virtcent06.summitnjhome.com.
29 PTR virtcent07.summitnjhome.com.
30 PTR virtcent08.summitnjhome.com.
31 PTR virtcent09.summitnjhome.com.
32 PTR virtcent10.summitnjhome.com.
33 PTR virtcent11.summitnjhome.com.
34 PTR virtcent12.summitnjhome.com.
35 PTR virtcent13.summitnjhome.com.
36 PTR virtcent14.summitnjhome.com.
37 PTR virtcent15.summitnjhome.com.
38 PTR virtcent16.summitnjhome.com.
39 PTR virtcent17.summitnjhome.com.
40 PTR virtcent18.summitnjhome.com.
41 PTR virtcent19.summitnjhome.com.
and my /etc/resolv.conf looks like this:
domain summitnjhome.com
nameserver 192.168.1.44
nameserver 4.2.2.2
zone 1.168.192.in-addr.arpa {
type master;
file /etc/named/master/summitnjhome-reverse.db
};
then I restart both named and the network service
and yet if I were to try forward resolution:
LBSD2# host sum1
sum1.summitnjhome.com is an alias for LCENT01.summitnjhome.com.
LCENT01.summitnjhome.com has address 192.168.1.42
and then reverse resolution:
LBSD2# host 192.168.1.42
Host 42.1.168.192.in-addr.arpa. not found: 3(NXDOMAIN)
I have no luck. Any thoughts on this?
thanks!
--
GPG me!!
gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: reverse dns in bind9
Date: Mon, 28 Mar 2011 00:19:26 -0400
From: Tim Dunphy bluethu...@gmail.com
Subject: reverse dns in bind9
Hello,
I am attempting to setup reverse dns in bind 9 under freebsd... this is
in an attempt to allow mysql to work a little easier with DNS
resolution.
In my /etc/named/named.conf file I have the following:
// RFC 1912
zone localhost { type master; file master/localhost-forward.db; };
zone 127.in-addr.arpa { type master; ile master/localhost-reverse.db; };
zone 255.in-addr.arpa { type master; file master/empty.db; };
zone 192.in-addr.arpa { type master; file master/summitjnhome-reverse.db;
};
zone summitnjhome.com { type master; file master/summitnjhome.db; };
My master/summitnjhome.com looks like the following:
For starters, this should be in master/summitnjhome-reerse.db
$TTL 3D
@ IN SOA ns1.summitnjhome.com. bluethundr.gmail.com. (
201103271 ; Serial, todays date + todays serial
8H ; Refresh
2H ; Retry
4W ; Expire
1D) ; Minimum TTL
NS ns1.summitnjhome.com.
summitnjhome.com.
42 PTR LCENT01.summitnjhome.com.
43 PTR LCENT02.summitnjhome.com.
44 PTR LBSD2.summitnjhome.com.
45 PTR LCENT02.summitnjhome.com.
46 PTR LCENT03.summitnjhome.com.
47 PTR LCENT04.summitnjhome.com.
23 PTR virtcent01.summitnjhome.com.
24 PTR virtcent02.summitnjhome.com.
21 PTR virtcent03.summitnjhome.com.
26 PTR virtcent04.summitnjhome.com.
27 PTR virtcent05.summitnjhome.com.
28 PTR virtcent06.summitnjhome.com.
29 PTR virtcent07.summitnjhome.com.
30 PTR virtcent08.summitnjhome.com.
31 PTR virtcent09.summitnjhome.com.
32 PTR virtcent10.summitnjhome.com.
33 PTR virtcent11.summitnjhome.com.
34 PTR virtcent12.summitnjhome.com.
35 PTR virtcent13.summitnjhome.com.
36 PTR virtcent14.summitnjhome.com.
37 PTR virtcent15.summitnjhome.com.
38 PTR virtcent16.summitnjhome.com.
39 PTR virtcent17.summitnjhome.com.
40 PTR virtcent18.summitnjhome.com.
41 PTR virtcent19.summitnjhome.com.
and my /etc/resolv.conf looks like this:
domain summitnjhome.com
nameserver 192.168.1.44
nameserver 4.2.2.2
zone 1.168.192.in-addr.arpa { type master; file
/etc/named/master/summitnjhome-reverse.db
};
the 'zone' line you show should *NOT* be in resolv.conf at all.
this line should be in the named.conf file *instead* of the one for
the '192.in-addr.arpa' zone.
then I restart both named and the network service
and yet if I were to try forward resolution:
LBSD2# host sum1
sum1.summitnjhome.com is an alias for LCENT01.summitnjhome.com.
LCENT01.summitnjhome.com has address 192.168.1.42
and then reverse resolution:
LBSD2# host 192.168.1.42
Host 42.1.168.192.in-addr.arpa. not found: 3(NXDOMAIN)
I have no luck. Any thoughts on this?
see above.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
questions on bind9-3.6-P1
oKay, since my prev question caught no wixards, how about looking at the errors from bind-9.3.6? [I rebuilt this from the src tarball; it finally installed; I fixed some obvious errors, but several remain. Here is the log file where bind9 fails on em0, my NIC in my server. This is one failure that is simply over my head. +++ Jan 24 11:14:55 ethic named[59747]: starting BIND 9.3.6-P1 -c /var/named/etc/namedb/named.conf Jan 24 11:14:55 ethic named[59747]: could not listen on UDP socket: address in use Jan 24 11:14:55 ethic named[59747]: creating IPv4 interface em0 failed; interface ignored Jan 24 11:14:55 ethic named[59747]: could not listen on UDP socket: address in use Jan 24 11:14:55 ethic named[59747]: creating IPv4 interface lo0 failed; interface ignored Jan 24 11:14:55 ethic named[59747]: not listening on any interfaces Jan 24 11:14:55 ethic named[59747]: couldn't add command channel 127.0.0.1#953: address in use Jan 24 11:14:55 ethic named[59747]: couldn't add command channel ::1#953: address in use Jan 24 11:14:55 ethic named[59747]: could not listen on UDP socket: address in use Jan 24 11:14:55 ethic named[59747]: creating IPv4 interface em0 failed; interface ignored Jan 24 11:14:55 ethic named[59747]: could not listen on UDP socket: address in use Jan 24 11:14:55 ethic named[59747]: creating IPv4 interface lo0 failed; interface ignored Jan 24 11:14:55 ethic named[59747]: running +++ Can anybody explain why (eg) the lo0 failed or was ignored. And why bind9--now offically at its EOLife--has trouble creating an IPv4 interface with my NIC, em0? Do I have to do some very simple? like rebooting? -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix The 7.97a release of Jottings: http://jottings.thought.org/index.php http://journey.thought.org ethic ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: questions on bind9-3.6-P1
On 1/24/11 2:33 PM, Gary Kline wrote: oKay, since my prev question caught no wixards, how about looking at the errors from bind-9.3.6? [I rebuilt this from the src tarball; it finally installed; I fixed some obvious errors, but several remain. Here is the log file where bind9 fails on em0, my NIC in my server. This is one failure that is simply over my head. +++ Jan 24 11:14:55 ethic named[59747]: starting BIND 9.3.6-P1 -c /var/named/etc/namedb/named.conf Jan 24 11:14:55 ethic named[59747]: could not listen on UDP socket: address in use Jan 24 11:14:55 ethic named[59747]: creating IPv4 interface em0 failed; interface ignored Jan 24 11:14:55 ethic named[59747]: could not listen on UDP socket: address in use Jan 24 11:14:55 ethic named[59747]: creating IPv4 interface lo0 failed; interface ignored Jan 24 11:14:55 ethic named[59747]: not listening on any interfaces Jan 24 11:14:55 ethic named[59747]: couldn't add command channel 127.0.0.1#953: address in use Jan 24 11:14:55 ethic named[59747]: couldn't add command channel ::1#953: address in use Jan 24 11:14:55 ethic named[59747]: could not listen on UDP socket: address in use Jan 24 11:14:55 ethic named[59747]: creating IPv4 interface em0 failed; interface ignored Jan 24 11:14:55 ethic named[59747]: could not listen on UDP socket: address in use Jan 24 11:14:55 ethic named[59747]: creating IPv4 interface lo0 failed; interface ignored Jan 24 11:14:55 ethic named[59747]: running +++ Can anybody explain why (eg) the lo0 failed or was ignored. And why bind9--now offically at its EOLife--has trouble creating an IPv4 interface with my NIC, em0? Do I have to do some very simple? like rebooting? It appears to be complaining that you're already running another piece of software that is listening on all those ports. I'd be guessing another copy of bind. Try: ps uxwwa | grep named and see what all is running. If you're dealing with a bind from base and bind from ports I could see you trying to start both of them. Do you have named files in both /etc/rc.d and /usr/local/etc/rc.d? -- --Jon Radel j...@radel.com
Re: questions on bind9-3.6-P1
On Mon, Jan 24, 2011 at 10:33 PM, Gary Kline kl...@thought.org wrote: oKay, since my prev question caught no wixards, how about looking at the errors from bind-9.3.6? [I rebuilt this from the src tarball; it finally installed; I fixed some obvious errors, but several remain. Here is the log file where bind9 fails on em0, my NIC in my server. This is one failure that is simply over my head. +++ Jan 24 11:14:55 ethic named[59747]: starting BIND 9.3.6-P1 -c /var/named/etc/namedb/named.conf Jan 24 11:14:55 ethic named[59747]: could not listen on UDP socket: address in use Jan 24 11:14:55 ethic named[59747]: creating IPv4 interface em0 failed; interface ignored Jan 24 11:14:55 ethic named[59747]: could not listen on UDP socket: address in use Jan 24 11:14:55 ethic named[59747]: creating IPv4 interface lo0 failed; interface ignored Jan 24 11:14:55 ethic named[59747]: not listening on any interfaces Jan 24 11:14:55 ethic named[59747]: couldn't add command channel 127.0.0.1#953: address in use Jan 24 11:14:55 ethic named[59747]: couldn't add command channel ::1#953: address in use Jan 24 11:14:55 ethic named[59747]: could not listen on UDP socket: address in use Jan 24 11:14:55 ethic named[59747]: creating IPv4 interface em0 failed; interface ignored Jan 24 11:14:55 ethic named[59747]: could not listen on UDP socket: address in use Jan 24 11:14:55 ethic named[59747]: creating IPv4 interface lo0 failed; interface ignored Jan 24 11:14:55 ethic named[59747]: running +++ Can anybody explain why (eg) the lo0 failed or was ignored. And why bind9--now offically at its EOLife--has trouble creating an IPv4 interface with my NIC, em0? Do I have to do some very simple? like rebooting? You already have another instance of Bind running, so you cannot have TWO !!! -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Damn!! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: questions on bind9-3.6-P1
On 1/24/11 12:33 PM, Gary Kline wrote: oKay, since my prev question caught no wixards, how about looking at the errors from bind-9.3.6? [I rebuilt this from the src tarball; it finally installed; I fixed some obvious errors, but several remain. Here is the log file where bind9 fails on em0, my NIC in my server. This is one failure that is simply over my head. +++ Jan 24 11:14:55 ethic named[59747]: starting BIND 9.3.6-P1 -c /var/named/etc/namedb/named.conf Jan 24 11:14:55 ethic named[59747]: could not listen on UDP socket: address in use Jan 24 11:14:55 ethic named[59747]: creating IPv4 interface em0 failed; interface ignored Jan 24 11:14:55 ethic named[59747]: could not listen on UDP socket: address in use Jan 24 11:14:55 ethic named[59747]: creating IPv4 interface lo0 failed; interface ignored Jan 24 11:14:55 ethic named[59747]: not listening on any interfaces Jan 24 11:14:55 ethic named[59747]: couldn't add command channel 127.0.0.1#953: address in use Jan 24 11:14:55 ethic named[59747]: couldn't add command channel ::1#953: address in use Jan 24 11:14:55 ethic named[59747]: could not listen on UDP socket: address in use Jan 24 11:14:55 ethic named[59747]: creating IPv4 interface em0 failed; interface ignored Jan 24 11:14:55 ethic named[59747]: could not listen on UDP socket: address in use Jan 24 11:14:55 ethic named[59747]: creating IPv4 interface lo0 failed; interface ignored Jan 24 11:14:55 ethic named[59747]: running +++ Can anybody explain why (eg) the lo0 failed or was ignored. And why bind9--now offically at its EOLife--has trouble creating an IPv4 interface with my NIC, em0? Do I have to do some very simple? like rebooting? I think the issue probably lies in the address in use part of your error output. Try a sockstat/netstat to see what's bound on port 953. If it's an old instance of bind, kill it and then try restarting. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: questions on bind9-3.6-P1
On Mon, Jan 24, 2011 at 12:39:46PM -0700, Jarrod Slick wrote: On 1/24/11 12:33 PM, Gary Kline wrote: oKay, since my prev question caught no wixards, how about looking at the errors from bind-9.3.6? [I rebuilt this from the src tarball; it finally installed; I fixed some obvious errors, but several remain. Here is the log file where bind9 fails on em0, my NIC in my server. This is one failure that is simply over my head. +++ Jan 24 11:14:55 ethic named[59747]: starting BIND 9.3.6-P1 -c /var/named/etc/namedb/named.conf Jan 24 11:14:55 ethic named[59747]: could not listen on UDP socket: address in use Jan 24 11:14:55 ethic named[59747]: creating IPv4 interface em0 failed; interface ignored Jan 24 11:14:55 ethic named[59747]: could not listen on UDP socket: address in use Jan 24 11:14:55 ethic named[59747]: creating IPv4 interface lo0 failed; interface ignored Jan 24 11:14:55 ethic named[59747]: not listening on any interfaces Jan 24 11:14:55 ethic named[59747]: couldn't add command channel 127.0.0.1#953: address in use Jan 24 11:14:55 ethic named[59747]: couldn't add command channel ::1#953: address in use Jan 24 11:14:55 ethic named[59747]: could not listen on UDP socket: address in use Jan 24 11:14:55 ethic named[59747]: creating IPv4 interface em0 failed; interface ignored Jan 24 11:14:55 ethic named[59747]: could not listen on UDP socket: address in use Jan 24 11:14:55 ethic named[59747]: creating IPv4 interface lo0 failed; interface ignored Jan 24 11:14:55 ethic named[59747]: running +++ Can anybody explain why (eg) the lo0 failed or was ignored. And why bind9--now offically at its EOLife--has trouble creating an IPv4 interface with my NIC, em0? Do I have to do some very simple? like rebooting? I think the issue probably lies in the address in use part of your error output. Try a sockstat/netstat to see what's bound on port 953. If it's an old instance of bind, kill it and then try restarting. HMMM: Here's what the log shows: --sorry for the overage; i cannot cut/paste here on ethic]. Looks like same thing. Jan 24 12:14:56 ethic named[59747]: creating IPv4 interface lo0 failed; interface ignored Jan 24 12:14:56 ethic named[59747]: not listening on any interfaces Jan 24 12:15:09 ethic root: Unknown USB device: vendor 0x17f6 product 0x0709 bus uhub4 Jan 24 12:15:09 ethic kernel: ukbd1: Unicomp Endura Keyboard, class 0/0, rev 1.10/2.15, addr 4 on uhub4 Jan 24 12:15:09 ethic kernel: kbd3 at ukbd1 Jan 24 12:15:39 ethic sm-mta[60106]: p0OKD6D2060106: SYSERR(root): collect: I/O error on connection from mx2.freebsd.org, from=owner-freebsd-hack...@freebsd.org Jan 24 12:33:50 ethic ntpd[862]: kernel time sync status change 6001 Jan 24 12:37:04 ethic named[60266]: starting BIND 9.3.6-P1 -c /var/named/etc/namedb/named.conf Jan 24 12:37:04 ethic named[60266]: could not listen on UDP socket: address in use Jan 24 12:37:04 ethic named[60266]: creating IPv4 interface em0 failed; interface ignored Jan 24 12:37:04 ethic named[60266]: could not listen on UDP socket: address in use Jan 24 12:37:04 ethic named[60266]: creating IPv4 interface lo0 failed; interface ignored Jan 24 12:37:04 ethic named[60266]: not listening on any interfaces Jan 24 12:37:04 ethic named[60266]: couldn't add command channel 127.0.0.1#953: address in use Jan 24 12:37:04 ethic named[60266]: couldn't add command channel ::1#953: address in use Jan 24 12:37:04 ethic named[60266]: could not listen on UDP socket: address in use Jan 24 12:37:04 ethic named[60266]: creating IPv4 interface em0 failed; interface ignored Jan 24 12:37:04 ethic named[60266]: could not listen on UDP socket: address in use Jan 24 12:37:04 ethic named[60266]: creating IPv4 interface lo0 failed; interface ignored Jan 24 12:37:04 ethic named[60266]: running ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix The 7.97a release of Jottings: http://jottings.thought.org/index.php http://journey.thought.org ethic ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: questions on bind9-3.6-P1
On 1/24/11 1:48 PM, Gary Kline wrote: On Mon, Jan 24, 2011 at 12:39:46PM -0700, Jarrod Slick wrote: On 1/24/11 12:33 PM, Gary Kline wrote: oKay, since my prev question caught no wixards, how about looking at the errors from bind-9.3.6? [I rebuilt this from the src tarball; it finally installed; I fixed some obvious errors, but several remain. Here is the log file where bind9 fails on em0, my NIC in my server. This is one failure that is simply over my head. +++ Jan 24 11:14:55 ethic named[59747]: starting BIND 9.3.6-P1 -c /var/named/etc/namedb/named.conf Jan 24 11:14:55 ethic named[59747]: could not listen on UDP socket: address in use Jan 24 11:14:55 ethic named[59747]: creating IPv4 interface em0 failed; interface ignored Jan 24 11:14:55 ethic named[59747]: could not listen on UDP socket: address in use Jan 24 11:14:55 ethic named[59747]: creating IPv4 interface lo0 failed; interface ignored Jan 24 11:14:55 ethic named[59747]: not listening on any interfaces Jan 24 11:14:55 ethic named[59747]: couldn't add command channel 127.0.0.1#953: address in use Jan 24 11:14:55 ethic named[59747]: couldn't add command channel ::1#953: address in use Jan 24 11:14:55 ethic named[59747]: could not listen on UDP socket: address in use Jan 24 11:14:55 ethic named[59747]: creating IPv4 interface em0 failed; interface ignored Jan 24 11:14:55 ethic named[59747]: could not listen on UDP socket: address in use Jan 24 11:14:55 ethic named[59747]: creating IPv4 interface lo0 failed; interface ignored Jan 24 11:14:55 ethic named[59747]: running +++ Can anybody explain why (eg) the lo0 failed or was ignored. And why bind9--now offically at its EOLife--has trouble creating an IPv4 interface with my NIC, em0? Do I have to do some very simple? like rebooting? I think the issue probably lies in the address in use part of your error output. Try a sockstat/netstat to see what's bound on port 953. If it's an old instance of bind, kill it and then try restarting. HMMM: Here's what the log shows: --sorry for the overage; i cannot cut/paste here on ethic]. Looks like same thing. Jan 24 12:14:56 ethic named[59747]: creating IPv4 interface lo0 failed; interface ignored Jan 24 12:14:56 ethic named[59747]: not listening on any interfaces Jan 24 12:15:09 ethic root: Unknown USB device: vendor 0x17f6 product 0x0709 bus uhub4 Jan 24 12:15:09 ethic kernel: ukbd1:Unicomp Endura Keyboard, class 0/0, rev 1.10/2.15, addr 4 on uhub4 Jan 24 12:15:09 ethic kernel: kbd3 at ukbd1 Jan 24 12:15:39 ethic sm-mta[60106]: p0OKD6D2060106: SYSERR(root): collect: I/O error on connection from mx2.freebsd.org, from=owner-freebsd-hack...@freebsd.org Jan 24 12:33:50 ethic ntpd[862]: kernel time sync status change 6001 Jan 24 12:37:04 ethic named[60266]: starting BIND 9.3.6-P1 -c /var/named/etc/namedb/named.conf Jan 24 12:37:04 ethic named[60266]: could not listen on UDP socket: address in use Jan 24 12:37:04 ethic named[60266]: creating IPv4 interface em0 failed; interface ignored Jan 24 12:37:04 ethic named[60266]: could not listen on UDP socket: address in use Jan 24 12:37:04 ethic named[60266]: creating IPv4 interface lo0 failed; interface ignored Jan 24 12:37:04 ethic named[60266]: not listening on any interfaces Jan 24 12:37:04 ethic named[60266]: couldn't add command channel 127.0.0.1#953: address in use Jan 24 12:37:04 ethic named[60266]: couldn't add command channel ::1#953: address in use Jan 24 12:37:04 ethic named[60266]: could not listen on UDP socket: address in use Jan 24 12:37:04 ethic named[60266]: creating IPv4 interface em0 failed; interface ignored Jan 24 12:37:04 ethic named[60266]: could not listen on UDP socket: address in use Jan 24 12:37:04 ethic named[60266]: creating IPv4 interface lo0 failed; interface ignored Jan 24 12:37:04 ethic named[60266]: running ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org Okay, but what exactly did you do? I guess my instruction to, restart, was a bit ambiguous. I meant after killing whatever is running on port 953 you should restart __bind__, preferably by executing your desired binary manually, not the system itself. You may be executing two instances of bind at startup as another respondent suggested. To recap, see what's bound on port 953: netstat -ntpl | grep 953 kill whatever is bound on 953 (you should be able to get the pid from the netstat output) kill -9 PID start your desired named: /path/to/bind your_arguments If that leaves you with a working named installation, remove the extraneous startup script and reboot to confirm that your issue is fixed. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions
Re: questions on bind9-3.6-P1
On Mon, Jan 24, 2011 at 02:45:41PM -0500, Jon Radel wrote: On 1/24/11 2:33 PM, Gary Kline wrote: oKay, since my prev question caught no wixards, how about looking at the errors from bind-9.3.6? [I rebuilt this from the src tarball; it finally installed; I fixed some obvious errors, but several remain. Here is the log file where bind9 fails on em0, my NIC in my server. This is one failure that is simply over my head. +++ Jan 24 11:14:55 ethic named[59747]: starting BIND 9.3.6-P1 -c /var/named/etc/namedb/named.conf Jan 24 11:14:55 ethic named[59747]: could not listen on UDP socket: address in use Jan 24 11:14:55 ethic named[59747]: creating IPv4 interface em0 failed; interface ignored Jan 24 11:14:55 ethic named[59747]: could not listen on UDP socket: address in use Jan 24 11:14:55 ethic named[59747]: creating IPv4 interface lo0 failed; interface ignored Jan 24 11:14:55 ethic named[59747]: not listening on any interfaces Jan 24 11:14:55 ethic named[59747]: couldn't add command channel 127.0.0.1#953: address in use Jan 24 11:14:55 ethic named[59747]: couldn't add command channel ::1#953: address in use Jan 24 11:14:55 ethic named[59747]: could not listen on UDP socket: address in use Jan 24 11:14:55 ethic named[59747]: creating IPv4 interface em0 failed; interface ignored Jan 24 11:14:55 ethic named[59747]: could not listen on UDP socket: address in use Jan 24 11:14:55 ethic named[59747]: creating IPv4 interface lo0 failed; interface ignored Jan 24 11:14:55 ethic named[59747]: running +++ Can anybody explain why (eg) the lo0 failed or was ignored. And why bind9--now offically at its EOLife--has trouble creating an IPv4 interface with my NIC, em0? Do I have to do some very simple? like rebooting? It appears to be complaining that you're already running another piece of software that is listening on all those ports. I'd be guessing another copy of bind. Try: ps uxwwa | grep named and see what all is running. If you're dealing with a bind from base and bind from ports I could see you trying to start both of them. Do you have named files in both /etc/rc.d and /usr/local/etc/rc.d? -- --Jon Radel j...@radel.com There is only one /etc/rc.d/named script; in fact, I have neven seen one from bind9-3 or bind9-7 [in /usr/local/etc/rc.d]. You're right about dup instances of named going! I'll kill9 and see what happens when i restart. Jan 24 12:37:04 ethic named[60266]: creating IPv4 interface lo0 failed; interface ignored Jan 24 12:37:04 ethic named[60266]: running Jan 24 12:59:32 ethic named[60411]: starting BIND 9.3.6-P1 -c /var/named/etc/namedb/named.conf Jan 24 12:59:32 ethic named[60411]: command channel listening on 127.0.0.1#953 Jan 24 12:59:32 ethic named[60411]: command channel listening on ::1#953 Jan 24 12:59:32 ethic named[60411]: running You're good, Jon! Somebody mentioned this yesterday but i had already KILLED my named. Just by script. So, should I follow the FBSD tradition of: if it works, why upgrade? Or should I try buind97 again? tHe reason for all this caution is that bind97 output a trucloak of errors that well way the hell over my head. And I really do need UDP. gary -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix The 7.97a release of Jottings: http://jottings.thought.org/index.php http://journey.thought.org ethic ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: questions on bind9-3.6-P1
On Mon, Jan 24, 2011 at 10:48:46PM +0300, Odhiambo Washington wrote: On Mon, Jan 24, 2011 at 10:33 PM, Gary Kline kl...@thought.org wrote: You already have another instance of Bind running, so you cannot have TWO !!! Yes indeed. So, since things are working again, as before I did a blind upgrade, do I want to upgrade to bind97? --There were about triple the errors in the messages logfile. HMMmmm, what would you do? gary -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Damn!! -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix The 7.97a release of Jottings: http://jottings.thought.org/index.php http://journey.thought.org ethic ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: questions on bind9-3.6-P1
On 01/25/11 07:26, Gary Kline wrote: On Mon, Jan 24, 2011 at 10:48:46PM +0300, Odhiambo Washington wrote: On Mon, Jan 24, 2011 at 10:33 PM, Gary Klinekl...@thought.org wrote: You already have another instance of Bind running, so you cannot have TWO !!! Yes indeed. So, since things are working again, as before I did a blind upgrade, do I want to upgrade to bind97? --There were about triple the errors in the messages logfile. HMMmmm, what would you do? gary Gary, deinstall bind97 and run make config and install as base. It may solve the problem you're having. If you have 2 instances of named on the system it could be having a hissy fit and tying to load both. As far as I can see the rest of the errors can be resolved easily. I've only done a base install so I've never actually seen an error like this, but unless someone else can provide better insight I'd go with that :) If it all does fail in the long run (but I seriously doubt it) you only need to update your sources and rebuild world to return to bind9. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: Manage Bind9 through the web, PowerDNS crash my system at startup
Hello, My problem (PowerDNS crash my system at startup) have been solved by correcting the configuration of PowerDNS as follow: Edit /usr/local/etc/pdns/pdns.conf and be sure that : daemon=yes guardian=yes Thanks with best wishes. Hello, I was looking for a solution to manage Bind9 DNS server through a web so I can add/edit zone. I thought PowerDNS/PowerAdmin would be a good solution for my requirements. I successfully installed both PowerDNS/PowerAdmin and tested them was working fine. When I restart my box I found PowerDNS crash my system giving many errors can't find mysqlserver. Any suggestions for the requirement to manage Bind9 through the web, or the PowerDNS problem. Thanks and have a nice day. Have you tried making sure that the MySQL daemon is started /BEFORE/ PowerDNS and Apache is started? Hello, Thank you for your reply. I thought you put your hand in my exact problem. When I start PowerDNS from command line using /usr/local/etc/rc.d/pdns onestart its running smooth. To make auto startup I just put this line pdns_enable=YES to the end of /etc/rc.conf. Can you please highlight to me how and where to add the instruction for auto startup of PowerDNS to be sure it's starting after Mysql. Thank, and have a nice day. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org look at the require and provide lines of the rc scripts hello, this snap of my rc.conf sshd_enable=YES ntpdate_enable=YES apache22_enable=YES named_enable=NO mysql_enable=YES mysql_dbdir=/usr/local/etc/mysql sendmail_enable=NO sendmail_submit_enable=NO sendmail_outbound_enable=NO sendmail_msp_queue_enable=NO pdns_enable=YES Thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: Manage Bind9 through the web, PowerDNS crash my system at startup
On Fri, Jan 7, 2011 at 8:39 AM, Sayed Nimer sayed...@gmail.com wrote: Hello, I was looking for a solution to manage Bind9 DNS server through a web so I can add/edit zone. I thought PowerDNS/PowerAdmin would be a good solution for my requirements. I successfully installed both PowerDNS/PowerAdmin and tested them was working fine. When I restart my box I found PowerDNS crash my system giving many errors can't find mysqlserver. Any suggestions for the requirement to manage Bind9 through the web, or the PowerDNS problem. Thanks and have a nice day. Have you tried making sure that the MySQL daemon is started /BEFORE/ PowerDNS and Apache is started? Hello, Thank you for your reply. I thought you put your hand in my exact problem. When I start PowerDNS from command line using /usr/local/etc/rc.d/pdns onestart its running smooth. To make auto startup I just put this line pdns_enable=YES to the end of /etc/rc.conf. Can you please highlight to me how and where to add the instruction for auto startup of PowerDNS to be sure it's starting after Mysql. Thank, and have a nice day. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Manage Bind9 through the web, PowerDNS crash my system at startup
On 7 January 2011 15:53, Sayed Nimer sayed...@gmail.com wrote: On Fri, Jan 7, 2011 at 8:39 AM, Sayed Nimer sayed...@gmail.com wrote: Hello, I was looking for a solution to manage Bind9 DNS server through a web so I can add/edit zone. I thought PowerDNS/PowerAdmin would be a good solution for my requirements. I successfully installed both PowerDNS/PowerAdmin and tested them was working fine. When I restart my box I found PowerDNS crash my system giving many errors can't find mysqlserver. Any suggestions for the requirement to manage Bind9 through the web, or the PowerDNS problem. Thanks and have a nice day. Have you tried making sure that the MySQL daemon is started /BEFORE/ PowerDNS and Apache is started? Hello, Thank you for your reply. I thought you put your hand in my exact problem. When I start PowerDNS from command line using /usr/local/etc/rc.d/pdns onestart its running smooth. To make auto startup I just put this line pdns_enable=YES to the end of /etc/rc.conf. Can you please highlight to me how and where to add the instruction for auto startup of PowerDNS to be sure it's starting after Mysql. Thank, and have a nice day. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org look at the require and provide lines of the rc scripts ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: Manage Bind9 through the web, PowerDNS crash my system at startup
Hello, I was looking for a solution to manage Bind9 DNS server through a web so I can add/edit zone. I thought PowerDNS/PowerAdmin would be a good solution for my requirements. I successfully installed both PowerDNS/PowerAdmin and tested them was working fine. When I restart my box I found PowerDNS crash my system giving many errors can't find mysqlserver. Any suggestions for the requirement to manage Bind9 through the web, or the PowerDNS problem. Thanks and have a nice day. Have you tried making sure that the MySQL daemon is started /BEFORE/ PowerDNS and Apache is started? Hello, Thank you for your reply. I thought you put your hand in my exact problem. When I start PowerDNS from command line using /usr/local/etc/rc.d/pdns onestart its running smooth. To make auto startup I just put this line pdns_enable=YES to the end of /etc/rc.conf. Can you please highlight to me how and where to add the instruction for auto startup of PowerDNS to be sure it's starting after Mysql. Thank, and have a nice day. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org look at the require and provide lines of the rc scripts hello, this snap of my rc.conf sshd_enable=YES ntpdate_enable=YES apache22_enable=YES named_enable=NO mysql_enable=YES mysql_dbdir=/usr/local/etc/mysql sendmail_enable=NO sendmail_submit_enable=NO sendmail_outbound_enable=NO sendmail_msp_queue_enable=NO pdns_enable=YES Thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: Manage Bind9 through the web, PowerDNS crash my system at startup
Hello. I am sorry if my comment sounds stupid... but It won't be WEBMIN an alternative for managing simple BIND operations? Jorge Biquez At 11:10 a.m. 07/01/2011, Sayed Nimer wrote: Hello, I was looking for a solution to manage Bind9 DNS server through a web so I can add/edit zone. I thought PowerDNS/PowerAdmin would be a good solution for my requirements. I successfully installed both PowerDNS/PowerAdmin and tested them was working fine. When I restart my box I found PowerDNS crash my system giving many errors can't find mysqlserver. Any suggestions for the requirement to manage Bind9 through the web, or the PowerDNS problem. Thanks and have a nice day. Have you tried making sure that the MySQL daemon is started /BEFORE/ PowerDNS and Apache is started? Hello, Thank you for your reply. I thought you put your hand in my exact problem. When I start PowerDNS from command line using /usr/local/etc/rc.d/pdns onestart its running smooth. To make auto startup I just put this line pdns_enable=YES to the end of /etc/rc.conf. Can you please highlight to me how and where to add the instruction for auto startup of PowerDNS to be sure it's starting after Mysql. Thank, and have a nice day. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org look at the require and provide lines of the rc scripts hello, this snap of my rc.conf sshd_enable=YES ntpdate_enable=YES apache22_enable=YES named_enable=NO mysql_enable=YES mysql_dbdir=/usr/local/etc/mysql sendmail_enable=NO sendmail_submit_enable=NO sendmail_outbound_enable=NO sendmail_msp_queue_enable=NO pdns_enable=YES Thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Manage Bind9 through the web, PowerDNS crash my system at startup
Hello, I was looking for a solution to manage Bind9 DNS server through a web so I can add/edit zone. I thought PowerDNS/PowerAdmin would be a good solution for my requirements. I successfully installed both PowerDNS/PowerAdmin and tested them was working fine. When I restart my box I found PowerDNS crash my system giving many errors can't find mysqlserver. Any suggestions for the requirement to manage Bind9 through the web, or the PowerDNS problem. Thanks and have a nice day. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Manage Bind9 through the web, PowerDNS crash my system at startup
On Fri, Jan 7, 2011 at 8:39 AM, Sayed Nimer sayed...@gmail.com wrote: Hello, I was looking for a solution to manage Bind9 DNS server through a web so I can add/edit zone. I thought PowerDNS/PowerAdmin would be a good solution for my requirements. I successfully installed both PowerDNS/PowerAdmin and tested them was working fine. When I restart my box I found PowerDNS crash my system giving many errors can't find mysqlserver. Any suggestions for the requirement to manage Bind9 through the web, or the PowerDNS problem. Thanks and have a nice day. Have you tried making sure that the MySQL daemon is started /BEFORE/ PowerDNS and Apache is started? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Issues reinstalling Bind9 on FreeBSD 8.0
Ok i'll make it short coz it's the 2nd time i write this -.-' and don't even ask why :D So here it goes: Fresh FreeBSD 8.0 install, installed bind97 to witch i have busted up the named.conf fine and tought, at the time, that deleting the whole content of /etc/namedb and reinstalling the bind port will simply write the files up again. Well it's not like that... i;ve did pgk_delete, make deinstall, make rmconfig, tryed to manually delete all the files required but no joy. Now i've tryed to use all bind9 bind96 and bind97 from ports and even get the source from isc.org but they all did the same, even more after a reboot and again the same process (source+ports) the builds didn't even install the named binary /etc/rc.d/named: WARNING: run_rc_command: cannot run /usr/sbin/named Please do tell me how to purge completly a port, delete all it's files and configs then install it again from scratch... I'm using a 64bit FreeBSD 8.0 on AMD Athlon X2. Best regards, Bogdan. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Issues reinstalling Bind9 on FreeBSD 8.0
Hi, /etc/rc.d/named: WARNING: run_rc_command: cannot run /usr/sbin/named /etc/rc.d/named ans /usr/sbin/named are not from the ports but from native FreeBSD distribution. Portsx will go into /usr/local/ only. So apparently you mixed-up distribution and port, deleted part of one and part of the other... If you have a fresh FreeBSD install, just reinstall it? Olivier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Issues reinstalling Bind9 on FreeBSD 8.0
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/06/2010 16:51:09, Olivier Nicole wrote: /etc/rc.d/named: WARNING: run_rc_command: cannot run /usr/sbin/named /etc/rc.d/named ans /usr/sbin/named are not from the ports but from native FreeBSD distribution. Portsx will go into /usr/local/ only. So apparently you mixed-up distribution and port, deleted part of one and part of the other... If you have a fresh FreeBSD install, just reinstall it? Also, if you're trying to run one of the bind ports, then you should just use all the default configuration stuff in /etc/namedb (which is really /var/named/etc/namedb) and the rc script /etc/rc.d/named with the binaries installed by the port by putting the following in /etc/rc.conf: named_enable=YES named_program=/usr/local/sbin/named named_flags=-c /etc/namedb/named.conf This is a bit unusual -- most ports install their own startup script in /usr/local/etc/rc.d/ and their own config files under /usr/local/etc or subdirs thereof. One handy hint is to link /usr/local/etc/rndc.conf to /etc/namedb/rndc.conf which helps the rc-script control the named process better. (Or .../rndc.key, depending on how you set things up.) Actually, I believe the various bind ports do this automatically now, but it doesn't hurt to double check. Cheers, Matthew - -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.14 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkwH3PIACgkQ8Mjk52CukIwDFQCfQRnuL/eOlV4V6lERkE480+OT J4QAnRHrzd5VWzEKswpR0eUtDa20zTzo =+8Vv -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
FreeBSD 7.0-RELEASE-p12 bind9 log files not found
Hello,
I have setup FreeBSD recently, can somebody help me with one interesting
thing - Bind9 slave DNS server, everything is works great, but I got a
problem with extended logging of xfer, etc.
Bind9 started in chroot:
root 7880.0 0.1 3156 1004 ?? Ss Fri01AM 0:02.10
/usr/sbin/syslogd -l /var/run/log -l /var/named/var/run/log -s
bind30792 0.0 1.2 16212 12864 ?? Is4:10PM 0:00.23
/usr/sbin/named -t /var/named -u bind
Configuration of logging channels from named.conf:
logging
{
channel xfer
{
file /var/named/var/log/xfer.log versions 3 size
10m;
print-time
yes;
print-severity
yes;
severity
info;
};
channel lame
{
file /var/named/var/log/lame.log versions 2 size
10m;
print-time
yes;
print-severity
yes;
severity
info;
};
channel config
{
file /var/named/var/log/conf.log versions 3 size
10m;
print-time
yes;
print-severity
yes;
severity
info;
};
channel security
{
file /var/named/var/log/security.log versions 3 size
10m;
print-time
yes;
print-severity
yes;
severity
info;
};
category xfer-in { xfer; };
category xfer-out { xfer; };
category notify { xfer; };
category lame-servers { lame; };
category config { config; };
category security { security; };
category default { default_syslog; default_debug; };
};
Next, I've create files in /var/named/var/log and chown them to bind:wheel
(cause of -u bind is defined above):
[po...@mgork23-gw /var/named/var/log]$ ls -la
total 4
drwxr-xr-x 2 bind wheel 512 May 30 16:09 .
drwxr-xr-x 6 root wheel 512 May 21 19:16 ..
-rw-r--r-- 1 bind wheel0 May 30 14:54 conf.log
-rw-r--r-- 1 bind wheel0 May 30 14:55 lame.log
-rw-r--r-- 1 bind wheel0 May 30 14:55 security.log
-rw-r--r-- 1 bind wheel0 May 30 14:54 xfer.log
But I get following messages in /var/log/messages:
May 30 16:27:42 srv named[31139]: starting BIND 9.4.2 -t /var/named -u bind
May 30 16:27:42 srv named[31139]: command channel listening on 127.0.0.1#953
May 30 16:27:42 srv named[31139]: command channel listening on ::1#953
May 30 16:27:42 srv named[31139]: logging channel 'xfer' file
'/var/named/var/log/xfer.log': file not found
May 30 16:27:42 srv named[31139]: logging channel 'lame' file
'/var/named/var/log/lame.log': file not found
May 30 16:27:42 srv named[31139]: logging channel 'config' file
'/var/named/var/log/conf.log': file not found
May 30 16:27:42 srv named[31139]: logging channel 'security' file
'/var/named/log/security.log': file not found
May 30 16:27:42 srv named[31139]: running
May 30 16:27:42 srv named[31139]: isc_log_open '/var/named/var/log/xfer.log'
failed: file not found
Changing permissions and putting log-files in different places (with
changing paths in named.conf of course) has no effect. I see that problem is
pretty silly but searching info about this doesn't say something special - I
still got file not found in /var/messages.
Maybe Iam don't understand where files must be placed, so, thanks in advance
for everybody who can explain how it works :)
VP
v.prokof...@gmail.com
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0-RELEASE-p12 bind9 log files not found
On Saturday 30 May 2009 14:50:31 Prokofyev Vladislav wrote:
Bind9 started in chroot:
root 7880.0 0.1 3156 1004 ?? Ss Fri01AM 0:02.10
/usr/sbin/syslogd -l /var/run/log -l /var/named/var/run/log -s
bind30792 0.0 1.2 16212 12864 ?? Is4:10PM 0:00.23
/usr/sbin/named -t /var/named -u bind
Configuration of logging channels from named.conf:
logging
{
channel xfer
{
file /var/named/var/log/xfer.log versions 3 size
10m;
The named running chrooted has no clue about /var/named. You can either use
ducttape:
cd /var/named/var sudo ln -s .. named
or just strip /var/named from your config file, hence use /var/log/xfer.log.
--
Mel
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0-RELEASE-p12 bind9 log files not found
Prokofyev Vladislav wrote: Hello, I have setup FreeBSD recently, can somebody help me with one interesting thing - Bind9 slave DNS server, everything is works great, but I got a problem with extended logging of xfer, etc. Bind9 started in chroot: root 7880.0 0.1 3156 1004 ?? Ss Fri01AM 0:02.10 /usr/sbin/syslogd -l /var/run/log -l /var/named/var/run/log -s bind30792 0.0 1.2 16212 12864 ?? Is4:10PM 0:00.23 /usr/sbin/named -t /var/named -u bind [snip] Changing permissions and putting log-files in different places (with changing paths in named.conf of course) has no effect. I see that problem is pretty silly but searching info about this doesn't say something special - I still got file not found in /var/messages. Maybe Iam don't understand where files must be placed, so, thanks in advance for everybody who can explain how it works :) Don't know if this will help, but took a quick look at my box here at home and have the following in my rc.conf - but I don't have logging turned on with this machine. Note the last line. So the logs should be in /var/named/var/log named_enable=YES named_program=/usr/sbin/named named_chrootdir=/var/named -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0-RELEASE-p12 bind9 log files not found
named_enable=YES named_program=/usr/sbin/named named_chrootdir=/var/named -Mike After adding these options on my system, named didn't start at boot. Manully attempt to start it via '/etc/rc.d/named start' brought to the following error: /etc/rc.d/named: WARNING: run_rc_command: cannot run /usr/sbin/named Anyway, thank you for time you've spent to write an answer. Hope this thread will help somebody who is stuck with the same problem. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 7.0-RELEASE-p12 bind9 log files not found
On Saturday 30 May 2009 17:01:17 Prokofyev Vladislav wrote: The named running chrooted has no clue about /var/named. You can either use ducttape: cd /var/named/var sudo ln -s .. named or just strip /var/named from your config file, hence use /var/log/xfer.log. -- Mel This helped, thank you a lot. So, if I think in a right way, /usr/sbin/named with -t start option don't effect on any symlinks etc. Erm, yes or ... no. I suggest you read up on chroot. The short answer is that relative symlinks within the chroot environment work while absolute ones should take into the account the new filesystem root. I didn't pay attention to this cause named(8) says: -t directory Chroot to directory after processing the command line arguments, but before reading the configuration file. and have a look at what /etc/namedb really is: # ls -l /etc/namedb lrwxr-xr-x 1 root wheel 21 May 21 06:24 /etc/namedb - /var/named/etc/namedb And this demonstrates chroot a bit: # cp /rescue/ls /var/named/ # chroot /var/named /ls -l /etc/namedb total 1 drwxr-xr-x 2 53 0512 Feb 28 05:57 dynamic drwxr-xr-x 2 0 0512 May 15 13:42 master -rw-r--r-- 1 0 0 11714 May 15 14:40 named.conf -rw-r--r-- 1 0 0 2956 May 15 13:42 named.root -rw--- 1 53 0 97 Apr 18 10:29 rndc.key drwxr-xr-x 2 53 0512 May 30 11:21 slave Warning: This option should be used in conjunction with the -u option, as chrooting a process running as root doesn't enhance security on most systems; the way chroot(2) is defined allows a process with root privileges to escape a chroot jail. And I thought that all actions for proper work are made by named :) They are, you just need reference the right path, the one without /var/named, or use relative paths where the working directory is /etc/namedb. So one would get to /var/log using: file ../../var/log/xfer; -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: [SOLVED} bind9 sdb pgsql
On Sun, Aug 10, 2008 at 12:53 AM, R Dicaire [EMAIL PROTECTED] wrote: On Sun, Aug 10, 2008 at 12:32 AM, User Lenzi [EMAIL PROTECTED] wrote: With a bit of work I was able to successfully build/replace bind9.4.2 port and add pgsql sdb support. If anyone's interested, I can post the method I used. I am interested, please if you put the posts it would be nice Sergio, I hope this helps. http://www.freebsddiary.org/phorum/read.php?f=4i=331t=331 does anyone have a sample pgsql table layout and sample zone data, I can't get this to work Sam Fourman Jr. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
bind9 sdb pgsql
Hi folks...I'm looking to rebuild bind9 to support the pgsql sdb interface, from /usr/src/contrib/bind9. However I don't see the contrib subdir in bind9/ where the sdb files reside (as they do in the src tarball). So how would I go about rebuilding bind to have this support? -- aRDy Music and Rick Dicaire present: http://www.ardynet.com http://www.ardynet.com:9000/ardymusic.ogg.m3u ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
[SOLVED} bind9 sdb pgsql
With a bit of work I was able to successfully build/replace bind9.4.2 port and add pgsql sdb support. If anyone's interested, I can post the method I used. -- aRDy Music and Rick Dicaire present: http://www.ardynet.com http://www.ardynet.com:9000/ardymusic.ogg.m3u ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [SOLVED} bind9 sdb pgsql
On Sun, Aug 10, 2008 at 12:32 AM, User Lenzi [EMAIL PROTECTED] wrote: With a bit of work I was able to successfully build/replace bind9.4.2 port and add pgsql sdb support. If anyone's interested, I can post the method I used. I am interested, please if you put the posts it would be nice Sergio, I hope this helps. http://www.freebsddiary.org/phorum/read.php?f=4i=331t=331 -- aRDy Music and Rick Dicaire present: http://www.ardynet.com http://www.ardynet.com:9000/ardymusic.ogg.m3u ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Upgrading Bind9 safely using portupgrade
Which is the best way to upgrade bind9 using portupgrade without setting anything on fire? I have two FreeBSDs which act as master and slave DNS (not installed by me), should i upgrade both bind's before they can work again? should i kill bind before upgrading? I'm sorry if any of my questions has an obvoius answer but i really don't know the first thing about FreeBSD and really want to get to know it better. Thanks in advance Rafael ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: BIND9 won't start
On Sun, Dec 23, 2007 at 11:45:58PM +0100, QADMOS wrote: Gelsema, P (Patrick) a écrit : On Sun, December 23, 2007 23:04, QADMOS wrote: Jonathan Horne a écrit : On Sunday 23 December 2007 02:52:43 pm QADMOS wrote: Hi everyone, i'm having a hard time with bind9. I'm trying to set up an authoritative dns server. Unfortunately when i try to launch it with an 'rndc start' i get this error message : rndc: connect failed: 127.0.0.1#953: connection refused I've reviewed my conf files but frankly i couldn't see what was wrong. I've actually rewritten them from scratch several times to really check that nothing was missing and couldn't see anything was wrong. The localhost.rev file is configured correctly. I've also tried to regenerate new rndc.keys and edit named.conf accordingly but to no avail. I've also considered a possible file permissions in /etc/namedb and in /var/run/named issue but that didn't yield much either. Finally the biggest trouble is that nothing is logged in any log file ! nothing in /var/log/messages nothing in /var/log/all.log nothing anywhere so i'm really confused here about what direction to investigate. Has anyone ever encountered such an issue ? Thx in advance for any help. do you get same problem with: /etc/rc.d/named start ? Well i've also tried that actually and when i do that : 1/ nothing is logged 2/ nothing is launched either Do you have the following in rc.conf? hulk# cat /etc/rc.conf | grep named named_enable=YES To me it seems your problem lies in the fact that named is not starting, so rndc can not control anything. Rgds, Patrick there's just no error message despite that the named is not running (checked with ps waux | grep named ) Well Patrick i followed your suggestion and rebooted (it didn't do much after just editing rc.conf) the box and now /etc/rc.d/named start works fine annd named is running, 'rndc' still has the same problem though (???) I'm a bit befuddled though, because i don't understand why it's necessary to use the named_enable directive to have named running ? I understand this is necessary if you want the daemon to run at boot time but why is this necessary if you want to run it manually once the box is on ? Well, if you use the rc script or any of the other scripts that might be supplied with it to start it, then that script checks that variable - namely 'named_enable' and if it is not set, the script exits without doing anything. jerry In any case thx a lot for your help :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
BIND9 won't start
Hi everyone, i'm having a hard time with bind9. I'm trying to set up an authoritative dns server. Unfortunately when i try to launch it with an 'rndc start' i get this error message : rndc: connect failed: 127.0.0.1#953: connection refused I've reviewed my conf files but frankly i couldn't see what was wrong. I've actually rewritten them from scratch several times to really check that nothing was missing and couldn't see anything was wrong. The localhost.rev file is configured correctly. I've also tried to regenerate new rndc.keys and edit named.conf accordingly but to no avail. I've also considered a possible file permissions in /etc/namedb and in /var/run/named issue but that didn't yield much either. Finally the biggest trouble is that nothing is logged in any log file ! nothing in /var/log/messages nothing in /var/log/all.log nothing anywhere so i'm really confused here about what direction to investigate. Has anyone ever encountered such an issue ? Thx in advance for any help. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: BIND9 won't start
On Sunday 23 December 2007 02:52:43 pm QADMOS wrote: Hi everyone, i'm having a hard time with bind9. I'm trying to set up an authoritative dns server. Unfortunately when i try to launch it with an 'rndc start' i get this error message : rndc: connect failed: 127.0.0.1#953: connection refused I've reviewed my conf files but frankly i couldn't see what was wrong. I've actually rewritten them from scratch several times to really check that nothing was missing and couldn't see anything was wrong. The localhost.rev file is configured correctly. I've also tried to regenerate new rndc.keys and edit named.conf accordingly but to no avail. I've also considered a possible file permissions in /etc/namedb and in /var/run/named issue but that didn't yield much either. Finally the biggest trouble is that nothing is logged in any log file ! nothing in /var/log/messages nothing in /var/log/all.log nothing anywhere so i'm really confused here about what direction to investigate. Has anyone ever encountered such an issue ? Thx in advance for any help. do you get same problem with: /etc/rc.d/named start ? -- Jonathan Horne http://dfwlpiki.dfwlp.org [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: BIND9 won't start
Jonathan Horne a écrit : On Sunday 23 December 2007 02:52:43 pm QADMOS wrote: Hi everyone, i'm having a hard time with bind9. I'm trying to set up an authoritative dns server. Unfortunately when i try to launch it with an 'rndc start' i get this error message : rndc: connect failed: 127.0.0.1#953: connection refused I've reviewed my conf files but frankly i couldn't see what was wrong. I've actually rewritten them from scratch several times to really check that nothing was missing and couldn't see anything was wrong. The localhost.rev file is configured correctly. I've also tried to regenerate new rndc.keys and edit named.conf accordingly but to no avail. I've also considered a possible file permissions in /etc/namedb and in /var/run/named issue but that didn't yield much either. Finally the biggest trouble is that nothing is logged in any log file ! nothing in /var/log/messages nothing in /var/log/all.log nothing anywhere so i'm really confused here about what direction to investigate. Has anyone ever encountered such an issue ? Thx in advance for any help. do you get same problem with: /etc/rc.d/named start ? Well i've also tried that actually and when i do that : 1/ nothing is logged 2/ nothing is launched either there's just no error message despite that the named is not running (checked with ps waux | grep named ) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: BIND9 won't start
On Sun, December 23, 2007 23:04, QADMOS wrote: Jonathan Horne a écrit : On Sunday 23 December 2007 02:52:43 pm QADMOS wrote: Hi everyone, i'm having a hard time with bind9. I'm trying to set up an authoritative dns server. Unfortunately when i try to launch it with an 'rndc start' i get this error message : rndc: connect failed: 127.0.0.1#953: connection refused I've reviewed my conf files but frankly i couldn't see what was wrong. I've actually rewritten them from scratch several times to really check that nothing was missing and couldn't see anything was wrong. The localhost.rev file is configured correctly. I've also tried to regenerate new rndc.keys and edit named.conf accordingly but to no avail. I've also considered a possible file permissions in /etc/namedb and in /var/run/named issue but that didn't yield much either. Finally the biggest trouble is that nothing is logged in any log file ! nothing in /var/log/messages nothing in /var/log/all.log nothing anywhere so i'm really confused here about what direction to investigate. Has anyone ever encountered such an issue ? Thx in advance for any help. do you get same problem with: /etc/rc.d/named start ? Well i've also tried that actually and when i do that : 1/ nothing is logged 2/ nothing is launched either Do you have the following in rc.conf? hulk# cat /etc/rc.conf | grep named named_enable=YES To me it seems your problem lies in the fact that named is not starting, so rndc can not control anything. Rgds, Patrick there's just no error message despite that the named is not running (checked with ps waux | grep named ) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: BIND9 won't start
Gelsema, P (Patrick) a écrit : On Sun, December 23, 2007 23:04, QADMOS wrote: Jonathan Horne a écrit : On Sunday 23 December 2007 02:52:43 pm QADMOS wrote: Hi everyone, i'm having a hard time with bind9. I'm trying to set up an authoritative dns server. Unfortunately when i try to launch it with an 'rndc start' i get this error message : rndc: connect failed: 127.0.0.1#953: connection refused I've reviewed my conf files but frankly i couldn't see what was wrong. I've actually rewritten them from scratch several times to really check that nothing was missing and couldn't see anything was wrong. The localhost.rev file is configured correctly. I've also tried to regenerate new rndc.keys and edit named.conf accordingly but to no avail. I've also considered a possible file permissions in /etc/namedb and in /var/run/named issue but that didn't yield much either. Finally the biggest trouble is that nothing is logged in any log file ! nothing in /var/log/messages nothing in /var/log/all.log nothing anywhere so i'm really confused here about what direction to investigate. Has anyone ever encountered such an issue ? Thx in advance for any help. do you get same problem with: /etc/rc.d/named start ? Well i've also tried that actually and when i do that : 1/ nothing is logged 2/ nothing is launched either Do you have the following in rc.conf? hulk# cat /etc/rc.conf | grep named named_enable=YES To me it seems your problem lies in the fact that named is not starting, so rndc can not control anything. Rgds, Patrick there's just no error message despite that the named is not running (checked with ps waux | grep named ) Well Patrick i followed your suggestion and rebooted (it didn't do much after just editing rc.conf) the box and now /etc/rc.d/named start works fine annd named is running, 'rndc' still has the same problem though (???) I'm a bit befuddled though, because i don't understand why it's necessary to use the named_enable directive to have named running ? I understand this is necessary if you want the daemon to run at boot time but why is this necessary if you want to run it manually once the box is on ? In any case thx a lot for your help :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: BIND9 won't start
My apologies for the blank post. Apparently, I became a bit trigger happy while setting up Kmail for mailing lists. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: BIND9 won't start
On Sunday 23 December 2007 05:45:58 pm QADMOS wrote: -- Glen Barber (570)328-0318 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: BIND9 won't start
QADMOS wrote: Gelsema, P (Patrick) a écrit : On Sun, December 23, 2007 23:04, QADMOS wrote: Jonathan Horne a écrit : On Sunday 23 December 2007 02:52:43 pm QADMOS wrote: Hi everyone, i'm having a hard time with bind9. I'm trying to set up an authoritative dns server. Unfortunately when i try to launch it with an 'rndc start' i get this error message : rndc: connect failed: 127.0.0.1#953: connection refused I've reviewed my conf files but frankly i couldn't see what was wrong. I've actually rewritten them from scratch several times to really check that nothing was missing and couldn't see anything was wrong. The localhost.rev file is configured correctly. I've also tried to regenerate new rndc.keys and edit named.conf accordingly but to no avail. I've also considered a possible file permissions in /etc/namedb and in /var/run/named issue but that didn't yield much either. Finally the biggest trouble is that nothing is logged in any log file ! nothing in /var/log/messages nothing in /var/log/all.log nothing anywhere so i'm really confused here about what direction to investigate. Has anyone ever encountered such an issue ? Thx in advance for any help. do you get same problem with: /etc/rc.d/named start ? Well i've also tried that actually and when i do that : 1/ nothing is logged 2/ nothing is launched either Do you have the following in rc.conf? hulk# cat /etc/rc.conf | grep named named_enable=YES To me it seems your problem lies in the fact that named is not starting, so rndc can not control anything. Rgds, Patrick there's just no error message despite that the named is not running (checked with ps waux | grep named ) Well Patrick i followed your suggestion and rebooted (it didn't do much after just editing rc.conf) the box and now /etc/rc.d/named start works fine annd named is running, 'rndc' still has the same problem though (???) I'm a bit befuddled though, because i don't understand why it's necessary to use the named_enable directive to have named running ? I understand this is necessary if you want the daemon to run at boot time but why is this necessary if you want to run it manually once the box is on ? In any case thx a lot for your help :) the entries in the rc.conf are there for system security. [something] might be installed, but its not supposed to be allowed to run unless the system admin knows about it. otherwise, there is always 'forcestart' intead of 'start'. cheers, -- Jonathan Horne http://www.dfwlp.org [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: BIND9 won't start
On Dec 23, 2007 3:45 PM, QADMOS [EMAIL PROTECTED] wrote: Gelsema, P (Patrick) a écrit : On Sun, December 23, 2007 23:04, QADMOS wrote: Jonathan Horne a écrit : On Sunday 23 December 2007 02:52:43 pm QADMOS wrote: Hi everyone, i'm having a hard time with bind9. I'm trying to set up an authoritative dns server. Unfortunately when i try to launch it with an 'rndc start' i get this error message : rndc: connect failed: 127.0.0.1#953: connection refused do you get same problem with: /etc/rc.d/named start Well i've also tried that actually and when i do that : 1/ nothing is logged 2/ nothing is launched either Do you have the following in rc.conf? hulk# cat /etc/rc.conf | grep named named_enable=YES To me it seems your problem lies in the fact that named is not starting, so rndc can not control anything. Rgds, Patrick there's just no error message despite that the named is not running (checked with ps waux | grep named ) Well Patrick i followed your suggestion and rebooted (it didn't do much after just editing rc.conf) the box and now /etc/rc.d/named start works fine annd named is running, 'rndc' still has the same problem though (???) I'm a bit befuddled though, because i don't understand why it's necessary to use the named_enable directive to have named running ? I understand this is necessary if you want the daemon to run at boot time but why is this necessary if you want to run it manually once the box is on ? /etc/rc.d/named is the rc script to control (start, stop etc.) named, and this script is inactive unless you've specified that named is to be enabled using the named_enable variable. You can get around the need to activate the variable by prefixing your commands with the 'force' keyword (e.g. /etc/rc.d/named forcestart, etc.) Use sockstat(1) to figure out if the control port (953/tcp) is listening. 'sockstat -4l' should show a listener on 127.0.0.1:953. Also, 'start' is not a valid command to rndc. You would have a chicken and egg problem; if named has not been started, then there is no service to handle the start command to rndc. Use the rc script to start named and rndc to control its runtime operation. DS ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: BIND9 won't start
On Monday 24 December 2007 02:15, Jonathan Horne wrote: otherwise, there is always 'forcestart' intead of 'start'. and Darren Spruell wrote: You can get around the need to activate the variable by prefixing your commands with the 'force' keyword (e.g. /etc/rc.d/named forcestart, etc.) To start a service which isn't enabled in rc.conf, it's better to use onestart From the rc.subr(8) manpage: force Skip the checks for rcvar being set to ``YES'', and sets rc_force=YES. This ignores argument_precmd returning non-zero, and ignores any of the required_* tests failing, and always returns a zero exit status. oneSkip the checks for rcvar being set to ``YES'', but performs all the other prerequisite tests. Jonathan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: BIND9 won't start
On Dec 23, 2007 10:43 PM, Jonathan McKeown [EMAIL PROTECTED] wrote: On Monday 24 December 2007 02:15, Jonathan Horne wrote: otherwise, there is always 'forcestart' intead of 'start'. and Darren Spruell wrote: You can get around the need to activate the variable by prefixing your commands with the 'force' keyword (e.g. /etc/rc.d/named forcestart, etc.) To start a service which isn't enabled in rc.conf, it's better to use onestart From the rc.subr(8) manpage: force Skip the checks for rcvar being set to ``YES'', and sets rc_force=YES. This ignores argument_precmd returning non-zero, and ignores any of the required_* tests failing, and always returns a zero exit status. oneSkip the checks for rcvar being set to ``YES'', but performs all the other prerequisite tests. Good to know, thx. DS ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ISC bind9 with dynamic DNS update (chroot problem)
Written by Patrick Dung on 07/28/07 10:52 Thanks for reply. Yes, your method works. But I wonder why /var/named/etc/named/master directory permission always reset to root at starting the daemon. Regards Patrick --- Reid Linnemann [EMAIL PROTECTED] wrote: Written by Patrick Dung on 07/27/07 08:19 Hi I use FreeBSD 6.2 and the base bind9. For dynamic DNS update, bind9 automatically generate the journal file (end in .jnl). The default config is to use chroot and the running user as 'bind'. The problem is that after named is started (/etc/init.d/named start), the default chroot directory /var/named/etc/named permission will be reset to own by root. So the named daemon (run as user 'bind') cannot create the journal file and complain: Jul 27 21:06:54 fbsd62 named[2862]: general: localdomain.db.jnl: create: permission denied One temp fix is to use chroot and run as root, any suggestions? Regards Patrick When I did ddns, I had my dynamic zone files in a subdirectory off of the named chroot- i.e. /var/named/etc/namedb/dynamic - and chowned it to bind, allowing the bind user to read/write anything inside. I forgot to CC: questions@ on my original reply This is because /etc/rc.d/named auto-updates the chroot to an expected state defined by the mtree at /etc/mtree/BIND.chroot.dist P.S. Please do not top post, so the conversation order progresses from oldest to newest. -Reid ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ISC bind9 with dynamic DNS update (chroot problem)
Thanks for reply. Your suggestion solved my problem, thanks. Yes, /etc/init.d/named is a typo. Regards Patrick --- Doug Barton [EMAIL PROTECTED] wrote: Patrick Dung wrote: Hi I use FreeBSD 6.2 and the base bind9. For dynamic DNS update, bind9 automatically generate the journal file (end in .jnl). The default config is to use chroot and the running user as 'bind'. The problem is that after named is started (/etc/init.d/named start), Are you sure you're doing this on FreeBSD? We have rc.d, not initd. Assuming that was just a typo ... the default chroot directory /var/named/etc/named The default directory is /etc/namedb, which is a symlink to /var/named/etc/namedb. permission will be reset to own by root. So the named daemon (run as user 'bind') cannot create the journal file and complain: You shouldn't be creating journal files in the config directory anyway. One temp fix is to use chroot and run as root, any suggestions? Yeah, don't run named as root. Ever. :) Assuming that you are actually running FreeBSD, and that you have not turned off the mtree option, you should have the following directories in /etc/namedb: drwxr-xr-x 2 bind wheel512 Jul 23 00:47 dynamic/ drwxr-xr-x 2 root wheel512 Jul 13 22:33 master/ drwxr-xr-x 2 bind wheel512 Jul 27 14:05 slave/ The dynamic directory is obviously designed to hold dynamic zones, and it (like the slave directory) is chowned to user bind so that named can write to it after it drops privileges. hth, Doug -- This .signature sanitized for your protection Get the free Yahoo! toolbar and rest assured with the added security of spyware protection. http://new.toolbar.yahoo.com/toolbar/features/norton/index.php ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
ISC bind9 with dynamic DNS update (chroot problem)
Hi I use FreeBSD 6.2 and the base bind9. For dynamic DNS update, bind9 automatically generate the journal file (end in .jnl). The default config is to use chroot and the running user as 'bind'. The problem is that after named is started (/etc/init.d/named start), the default chroot directory /var/named/etc/named permission will be reset to own by root. So the named daemon (run as user 'bind') cannot create the journal file and complain: Jul 27 21:06:54 fbsd62 named[2862]: general: localdomain.db.jnl: create: permission denied One temp fix is to use chroot and run as root, any suggestions? Regards Patrick Be a better Globetrotter. Get better travel answers from someone who knows. Yahoo! Answers - Check it out. http://answers.yahoo.com/dir/?link=listsid=396545469 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ISC bind9 with dynamic DNS update (chroot problem)
Patrick Dung wrote: Hi I use FreeBSD 6.2 and the base bind9. For dynamic DNS update, bind9 automatically generate the journal file (end in .jnl). The default config is to use chroot and the running user as 'bind'. The problem is that after named is started (/etc/init.d/named start), Are you sure you're doing this on FreeBSD? We have rc.d, not initd. Assuming that was just a typo ... the default chroot directory /var/named/etc/named The default directory is /etc/namedb, which is a symlink to /var/named/etc/namedb. permission will be reset to own by root. So the named daemon (run as user 'bind') cannot create the journal file and complain: You shouldn't be creating journal files in the config directory anyway. One temp fix is to use chroot and run as root, any suggestions? Yeah, don't run named as root. Ever. :) Assuming that you are actually running FreeBSD, and that you have not turned off the mtree option, you should have the following directories in /etc/namedb: drwxr-xr-x 2 bind wheel512 Jul 23 00:47 dynamic/ drwxr-xr-x 2 root wheel512 Jul 13 22:33 master/ drwxr-xr-x 2 bind wheel512 Jul 27 14:05 slave/ The dynamic directory is obviously designed to hold dynamic zones, and it (like the slave directory) is chowned to user bind so that named can write to it after it drops privileges. hth, Doug -- This .signature sanitized for your protection ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.2 default bind9, question about customize logging [re-post] (solved)
--- Doug Barton [EMAIL PROTECTED] wrote:
On Sunday, 8 July 2007 at 12:06:26 -0700, Patrick Dung wrote:
I am using FreeBSD 6.2 with the default bind (not ports).
By default chroot is used.
It's not a major issue, but it's probably worth pointing out that
whatever code base you use (base or ports) the behavior such as
chroot, logging, etc. is controlled by the combination of
/etc/rc.d/named and your named.conf options. Therefore this
discussion
applies equally well either way.
I use FreeBSD 6.2 with the named come with the base.
/etc/rc.conf
named_enable=YES # Run named, the DNS server (or NO).
named_program=/usr/sbin/named # path to named, if you want a
different one.
#named_flags= # Flags for named
named_pidfile=/var/run/named/pid # Must set this in named.conf as
well
named_uid=bind# User to run named as
named_chrootdir=/var/named# Chroot directory (or not to
auto-chroot it)
named_chroot_autoupdate=YES # Automatically install/update chrooted
# components of named. See
/etc/rc.d/named.
named_symlink_enable=YES # Symlink the chrooted pid file
When named start or stop, it does have log in /var/log/messages.
But for example, when some do domain transfer successfully, that
is not
logged (zone transfer denied is logged).
I have intentionally avoided adding more complex logging to the
default named.conf because it's very hard to decide which way to land
on this to make the most people happy (and/or the least people mad).
I
am of course always open to suggestions. :)
I need to log successful domain transfer for debugging purpose (which
slave/client has done domain transfer at what time).
So I tried to add this part in named.conf (enabled local0.* in
syslog.conf) , but still no luck. Any suggestions?
The obvious ones, did you HUP the daemon after you changed the conf,
and did you pre-create any new files that syslogd is supposed to
write
to for the local0 facility? Can you share your syslog.conf line for
this? Do you get any joy when you try 'logger -plocal0.info blah' ?
logging {
channel named-log {
While I don't see that it's explicitly forbidden to use a - in a
channel name, every example I've ever seen or used myself uses an
underscore instead (named_log).
//syslog daemon;
syslog local0;
severity info;
print-category yes;
};
category default { named-log; };
category xfer-in { named-log; };
category xfer-out { named-log; };
category unmatched { null; };
};
This all looks good (modulo the - issue I mentioned above), and I use
something similar myself, so once you're sure you can write to the
syslog facility, you should be able to get this to work.
I should probably also point out that unless you really need this to
go to syslog, you're probably better off writing to a file channel
instead (less overhead, especially on a busy server). Either way
there
is information in the ARM that will help you,
/usr/share/doc/bind9/arm.
After furher testing, I got my problem solved.
1. I found named-log is ok to use.
2. I did not need to change my previous named.conf.
3. The problem is in /etc/syslog.conf
With the default /etc/syslog.conf, I have add a line:
local0.*/var/log/messages
There is a difference on where I put it, if I put it at the bottom of
the file, even `logger -p local0.info test` will not work.
If it put that line on the top-most of syslog.conf, everything is
working fine...
BTW, could anyone explain why putting local0.* /var/log/messages at the
bottom of syslog.conf will not work?
Regards
Patrick
hth,
Doug
--
This .signature sanitized for your protection
Looking for a deal? Find great prices on flights and hotels with Yahoo!
FareChase.
http://farechase.yahoo.com/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.2 default bind9, question about customize logging [re-post] (solved)
hi,
i am not sure why local0 would not work at the bottom of the file
may be some sort of rules - first come, first serv
but, sorry i forgot to mention of the my syslog.conf file along with
named.conf file
!named
*.* /var/log/bind/named.log
this is what i got, but i don't like to log named instances into /var/
log/messages
On Jul 11, 2007, at 8:14 AM, Patrick Dung wrote:
--- Doug Barton [EMAIL PROTECTED] wrote:
On Sunday, 8 July 2007 at 12:06:26 -0700, Patrick Dung wrote:
I am using FreeBSD 6.2 with the default bind (not ports).
By default chroot is used.
It's not a major issue, but it's probably worth pointing out that
whatever code base you use (base or ports) the behavior such as
chroot, logging, etc. is controlled by the combination of
/etc/rc.d/named and your named.conf options. Therefore this
discussion
applies equally well either way.
I use FreeBSD 6.2 with the named come with the base.
/etc/rc.conf
named_enable=YES # Run named, the DNS server (or NO).
named_program=/usr/sbin/named # path to named, if you want a
different one.
#named_flags= # Flags for named
named_pidfile=/var/run/named/pid # Must set this in named.conf as
well
named_uid=bind# User to run named as
named_chrootdir=/var/named# Chroot directory (or not to
auto-chroot it)
named_chroot_autoupdate=YES # Automatically install/update
chrooted
# components of named. See
/etc/rc.d/named.
named_symlink_enable=YES # Symlink the chrooted pid file
When named start or stop, it does have log in /var/log/messages.
But for example, when some do domain transfer successfully, that
is not
logged (zone transfer denied is logged).
I have intentionally avoided adding more complex logging to the
default named.conf because it's very hard to decide which way to land
on this to make the most people happy (and/or the least people mad).
I
am of course always open to suggestions. :)
I need to log successful domain transfer for debugging purpose (which
slave/client has done domain transfer at what time).
So I tried to add this part in named.conf (enabled local0.* in
syslog.conf) , but still no luck. Any suggestions?
The obvious ones, did you HUP the daemon after you changed the conf,
and did you pre-create any new files that syslogd is supposed to
write
to for the local0 facility? Can you share your syslog.conf line for
this? Do you get any joy when you try 'logger -plocal0.info blah' ?
logging {
channel named-log {
While I don't see that it's explicitly forbidden to use a - in a
channel name, every example I've ever seen or used myself uses an
underscore instead (named_log).
//syslog daemon;
syslog local0;
severity info;
print-category yes;
};
category default { named-log; };
category xfer-in { named-log; };
category xfer-out { named-log; };
category unmatched { null; };
};
This all looks good (modulo the - issue I mentioned above), and I use
something similar myself, so once you're sure you can write to the
syslog facility, you should be able to get this to work.
I should probably also point out that unless you really need this to
go to syslog, you're probably better off writing to a file channel
instead (less overhead, especially on a busy server). Either way
there
is information in the ARM that will help you,
/usr/share/doc/bind9/arm.
After furher testing, I got my problem solved.
1. I found named-log is ok to use.
2. I did not need to change my previous named.conf.
3. The problem is in /etc/syslog.conf
With the default /etc/syslog.conf, I have add a line:
local0.*/var/log/messages
There is a difference on where I put it, if I put it at the bottom of
the file, even `logger -p local0.info test` will not work.
If it put that line on the top-most of syslog.conf, everything is
working fine...
BTW, could anyone explain why putting local0.* /var/log/messages at
the
bottom of syslog.conf will not work?
Regards
Patrick
hth,
Doug
--
This .signature sanitized for your protection
__
__
Looking for a deal? Find great prices on flights and hotels with
Yahoo! FareChase.
http://farechase.yahoo.com/
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-isp
To unsubscribe, send any mail to [EMAIL PROTECTED]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.2 default bind9, question about customize logging [re-post]
this is what i have from 5.2
logging {
channel namedlog {
file /var/log/named.log;
severity info;
print-category yes;
print-severity yes;
print-time yes;
};
category lame-servers {
null;
};
category default {
namedlog;
};
category xfer-out { namedlog;};
};
hope this help
On Jul 8, 2007, at 2:06 PM, Patrick Dung wrote:
I am using FreeBSD 6.2 with the default bind (not ports).
By default chroot is used.
When named start or stop, it does have log in /var/log/messages.
But for example, when some do domain transfer successfully, that is
not
logged (zone transfer denied is logged).
So I tried to add this part in named.conf (enabled local0.* in
syslog.conf) , but still no luck. Any suggestions?
logging {
channel named-log {
//syslog daemon;
syslog local0;
severity info;
print-category yes;
};
category default { named-log; };
category xfer-in { named-log; };
category xfer-out { named-log; };
category unmatched { null; };
};
Thanks
Patrick
__
__
Be a better Heartthrob. Get better relationship answers from
someone who knows. Yahoo! Answers - Check it out.
http://answers.yahoo.com/dir/?link=listsid=396545433
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-isp
To unsubscribe, send any mail to [EMAIL PROTECTED]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD 6.2 default bind9, question about customize logging [re-post]
I am using FreeBSD 6.2 with the default bind (not ports).
By default chroot is used.
When named start or stop, it does have log in /var/log/messages.
But for example, when some do domain transfer successfully, that is not
logged (zone transfer denied is logged).
So I tried to add this part in named.conf (enabled local0.* in
syslog.conf) , but still no luck. Any suggestions?
logging {
channel named-log {
//syslog daemon;
syslog local0;
severity info;
print-category yes;
};
category default { named-log; };
category xfer-in { named-log; };
category xfer-out { named-log; };
category unmatched { null; };
};
Thanks
Patrick
Be a better Heartthrob. Get better relationship answers from someone who knows.
Yahoo! Answers - Check it out.
http://answers.yahoo.com/dir/?link=listsid=396545433
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD 6.2 default bind9, question about customize logging
I am using FreeBSD 6.2 with the default bind (not ports).
By default chroot is used.
When named start or stop, it does have log in /var/log/messages.
But for example, when some do domain transfer successfully, that is not
logged (zone transfer denied is logged).
So I tried to add this part in named.conf (enabled local0.* in
syslog.conf) , but still no luck. Any suggestions?
logging {
channel named-log {
//syslog daemon;
syslog local0;
severity info;
print-category yes;
};
category default { named-log; };
category xfer-in { named-log; };
category xfer-out { named-log; };
category unmatched { null; };
};
Thanks
Patrick
Park yourself in front of a world of choices in alternative vehicles. Visit the
Yahoo! Auto Green Center.
http://autos.yahoo.com/green_center/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: OT: Re: The worst error message in history belongs to... BIND9!
On Thu, Jul 05, 2007 at 04:46:52PM +0100, John Murphy wrote: Wasn't there, once upon a time, an error message in FreeBSD which reported 'This doesn't look like Kansas, Toto'? I remember seeing that error message somewhere, but do not remember where or if it was in FreeBSD. jerry Seem to recall it occurring when I deleted the directory I was 'in'. I may have imagined it though! -- John. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: OT: Re: The worst error message in history belongs to... BIND9!
Jerry McAllister wrote: On Thu, Jul 05, 2007 at 04:46:52PM +0100, John Murphy wrote: Wasn't there, once upon a time, an error message in FreeBSD which reported 'This doesn't look like Kansas, Toto'? I remember seeing that error message somewhere, but do not remember where or if it was in FreeBSD. It's a fortune. Whether it has also ever been an error message I cannot say, but not in 5.4 unless it's well hidden. Gee, Toto, I don't think we are in Kansas anymore. find /usr/src -type f -print0 | xargs -0 egrep -l Kansas --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: OT: Re: The worst error message in history belongs to... BIND9!
Alex Zbyslaw wrote: Jerry McAllister wrote: On Thu, Jul 05, 2007 at 04:46:52PM +0100, John Murphy wrote: Wasn't there, once upon a time, an error message in FreeBSD which reported 'This doesn't look like Kansas, Toto'? I remember seeing that error message somewhere, but do not remember where or if it was in FreeBSD. It's a fortune. Whether it has also ever been an error message I cannot say, but not in 5.4 unless it's well hidden. Gee, Toto, I don't think we are in Kansas anymore. find /usr/src -type f -print0 | xargs -0 egrep -l Kansas Seems it was replaced in 2000 with unable to return to working directory. http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/pkg_install/delete/perform.c.diff?r1=1.20;r2=1.21 -- John. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: OT: Re: The worst error message in history belongs to... BIND9!
[EMAIL PROTECTED] wrote: Favourite worst written error message in history: Keyboard not found. Press F1 to continue. I have always loved this one!! Who made that up!? Someone at IBM. That's what the original IBM PC, PC-AT, and (presumably) PC-XT displayed if the keyboard was dead or not plugged in. It was probably a case of modular code: any problem in POST would display a message and return a fail status, and the generic code would append Press F1 to continue. and wait. Not a bad idea at all -- certainly better than blindly trying to boot the machine without giving the operator a chance to decide what to do about the problem -- but this particular combination does have a chicken- egg aspect :( ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] This still happened on my fairly recent ASUS p4s8x Pentium 4 motherboard. I think you could make almost any motherboard yield that error, even these days. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: The worst error message in history belongs to... BIND9!
On Wed, Jul 04, 2007 at 08:14:44PM -0700, Garrett Cooper wrote: [EMAIL PROTECTED] wrote: Except that bash requires all the icky GNU utilities to build so you have to GNUify your system. And perl doesn't? It was GPL last I knew. The entirety of Perl falls under the GPL and Artistic license at this time. Read the perl-porters archives for more debate on Perl licensing. More to the point, Perl is dual-licensed -- redistributable under the terms of either the GPL or the Artistic License, at your discretion. As such, I tend to think of my Perl installs as being Artistic License, not GPL. -- CCD CopyWrite Chad Perrin [ http://ccd.apotheon.org ] MacUser, Nov. 1990: There comes a time in the history of any project when it becomes necessary to shoot the engineers and begin production. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Re[2]: The worst error message in history belongs to... BIND9!
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Gerard Sent: Wednesday, July 04, 2007 9:30 AM To: User Questions Subject: Re[2]: The worst error message in history belongs to... BIND9! On July 04, 2007 at 09:53AM Ted Mittelstaedt wrote: [snip] Actually perl has a lot of problems too. One of the biggest is that perl script writers always seem to think like you, in that perl is consistent across all platforms. The biggest problems I've seen with perl scripts are when people use perl extensions that are not on the system. You then have to go find the extension they use and very few of the perl script writers seem to be smart enough to put a section at the beginning of their scripts that define the CPAN location of the particular extensions they are using. The second biggest problem is perl script writers using constructs that are valid in Perl 5.6 and later but not valid in Perl 5.0 I don't know how many times I've wanted to strangle someone when trying to run a perl script under Perl 5.0 that had ONE single friggin statement in the entire thousand line script that isn't valid under 5.0 but is under 5.6 And I've also run across a number of Perl extensions that won't run under 5.0 as well, even though the authors are supposed to regression test under 5.0 I was under the impression that Perl 5.6.0 was released on 2000-Mar-22, while Perl 5.000 was issued on or about 1994-Oct-17. For the life of me, I cannot comprehend why anyone would be using such an antiquated version. I should have said the perl 5.0 family. Including 5.004 which is still being maintained by the Perl maintainers. Perl 5.005-04 just came out in 2004 by the way. perl 5.6.2 came out in Nov 2003. I have a rather limited knowledge of Perl; That's apparent. however, I am not going to be bothered regression testing it under a seven year old obsoleted version. There were major structural changes in perl 5.0 and 5.6 The changes going from 5.6 to 5.8 and 5.9 are much less. You can take it as a given that anything that runs on perl 5.005-04 will run on all perl 5.0 versions, anything that runs on perl 5.6.2 will run on all 5.6 versions, etc. The whole reason that the perl project maintains 5.0, 5.6, 5.8 and so on is that they know that there's systems that have lots of tested programs that have been tested under 5.0 and the system maintainers have not yet gone through the process of testing all that software on newer perl versions. Despite what you probably believe, when an organization has a server that is running fine, they are not frothing at the mouth to upgrade it to the latest version. This is why IMHO that perl is not a good choice to use for building large systems, not because the perl maintainers don't understand the importance of backwards compatability, but because too many programmers like yourself simply don't. If I was building a system that was ONLY going to use perl and the modules supplied with it, and NOT use any other 3rd party modules, then I would consider using perl, there wouldn't be anything wrong with it. But most of the perl scripts out there use many 3rd party modules (and I understand why, it saves them time) and that is where you have the problem, is with those. I believe that FreeBSD-3.4 was released around 12/21/1999 or there about. Should we also be testing against that version also? I wasn't talking about 1999 software I was talking about 2004 software. Ted ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: OT: Re: The worst error message in history belongs to... BIND9!
Anything you have actually seen is fair game. Ted -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of doug Sent: Wednesday, July 04, 2007 12:19 PM To: freebsd-questions@freebsd.org Subject: Re: OT: Re: The worst error message in history belongs to... BIND9! How far do we get to go back in time? From the first online fortran compiler: ugh1 and ugh2. In fairness these were conditions that were not supposed to happen, but somehow they always do. In more recent times I always liked, invalid page fault this perhaps as late as win98. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: OT: Re: The worst error message in history belongs to... BIND9!
Wasn't there, once upon a time, an error message in FreeBSD which reported 'This doesn't look like Kansas, Toto'? Seem to recall it occurring when I deleted the directory I was 'in'. I may have imagined it though! -- John. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: The worst error message in history belongs to... BIND9!
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Chad Perrin Sent: Thursday, July 05, 2007 12:39 AM To: FreeBSD Questions Subject: Re: The worst error message in history belongs to... BIND9! On Wed, Jul 04, 2007 at 08:14:44PM -0700, Garrett Cooper wrote: [EMAIL PROTECTED] wrote: Except that bash requires all the icky GNU utilities to build so you have to GNUify your system. And perl doesn't? It was GPL last I knew. The entirety of Perl falls under the GPL and Artistic license at this time. Read the perl-porters archives for more debate on Perl licensing. More to the point, Perl is dual-licensed -- redistributable under the terms of either the GPL or the Artistic License, at your discretion. Not correct. The Artistic license is less restrictive than the GPL so GPL advocates can take a Perl install and call it GPLd perl - but the Perl FAQ makes it very clear the intent of the Perl maintainers is not to use GPL. As they said, there is no GNU Perl I challenge you to point to one, single Perl scrap of code, that is ONLY gpled. As far as I know, anyone submitting patches or modifications to the Perl maintainers has been required to license their patches under Artistic for them to be included. Of course, if people put Perl extensions under GPL the Perl maintainers cannot help that. I do not think, however, that any extensions that are included with the default install are GPL-only. Ted ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: The worst error message in history belongs to... BIND9!
On Thu, Jul 05, 2007 at 09:19:00AM -0700, Ted Mittelstaedt wrote: -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Chad Perrin Sent: Thursday, July 05, 2007 12:39 AM To: FreeBSD Questions Subject: Re: The worst error message in history belongs to... BIND9! More to the point, Perl is dual-licensed -- redistributable under the terms of either the GPL or the Artistic License, at your discretion. Not correct. The Artistic license is less restrictive than the GPL so GPL advocates can take a Perl install and call it GPLd perl - but the Perl FAQ makes it very clear the intent of the Perl maintainers is not to use GPL. As they said, there is no GNU Perl I challenge you to point to one, single Perl scrap of code, that is ONLY gpled. Nothing I said should in any way be construed to mean that Perl, or any part of it, is in any way solely GPLed. I have no idea where you would have gotten such an impression. See above, where I point out that Perl is dual-licensed -- *not* solely GPLed. Also see the rest of what I said in the earlier email, in text you cut out of the quote, indicating that for my purposes Perl is installed under terms of the Perl Artistic License (and not the GPL). Nothing you have said suggests at all that my statement was incorrect, except the two words not correct. -- CCD CopyWrite Chad Perrin [ http://ccd.apotheon.org ] Dr. Ron Paul: Liberty has meaning only if we still believe in it when terrible things happen and a false government security blanket beckons. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: The worst error message in history belongs to... BIND9!
On Tue, 3 Jul 2007 22:05:50 -0600 Chad Perrin [EMAIL PROTECTED] wrote: On Tue, Jul 03, 2007 at 11:41:13PM -0400, Robert Huff wrote: Chad Perrin writes: Isn't Perl part of the base system these days? Perl has not been part of the base system for several years and was deprecated for some time before that. Is it part of the default install without being part of the base system, then? I don't recall needing to install it after system install on this laptop (using FreeBSD 6.2-RELEASE). A huge number of ports and packages have it as a dependency. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: The worst error message in history belongs to... BIND9!
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Bill Campbell Sent: Tuesday, July 03, 2007 9:36 AM To: freebsd-questions@freebsd.org Subject: Re: The worst error message in history belongs to... BIND9! On Tue, Jul 03, 2007, Martin McCormick wrote: Paul Chvostek writes: This is actually just the difference between sh and bash. You'll see the latter error if you type `a = 5` in bash in any OS. It just so happens that most Linux distributions don't have a real sh: I kind of thought that was the real issue. While something like this is maybe slightly annoying at times, the differences in, say, arithmetic handling and loops can sometimes mean rewriting parts of shell scripts depending on whether it is going to run in BSD or Linux. That's a major argument for doing things in python or perl as they are consistent across all platforms. While perl has a well deserved reputation for looking like modem noise, it's certainly no worse than shell scripts. Actually perl has a lot of problems too. One of the biggest is that perl script writers always seem to think like you, in that perl is consistent across all platforms. The biggest problems I've seen with perl scripts are when people use perl extensions that are not on the system. You then have to go find the extension they use and very few of the perl script writers seem to be smart enough to put a section at the beginning of their scripts that define the CPAN location of the particular extensions they are using. The second biggest problem is perl script writers using constructs that are valid in Perl 5.6 and later but not valid in Perl 5.0 I don't know how many times I've wanted to strangle someone when trying to run a perl script under Perl 5.0 that had ONE single friggin statement in the entire thousand line script that isn't valid under 5.0 but is under 5.6 And I've also run across a number of Perl extensions that won't run under 5.0 as well, even though the authors are supposed to regression test under 5.0 Pure /bin/sh is very limited in its constructs compared to other shells such as ksh, bash, etc. ksh is consistent across platfroms, of course, you generally have to compile it for the system your on. If you cannot work within a limited construct set your not much of a programmer. Ted ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: The worst error message in history belongs to... BIND9!
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of [EMAIL PROTECTED] Sent: Tuesday, July 03, 2007 7:34 PM To: [EMAIL PROTECTED] Cc: freebsd-questions@freebsd.org Subject: Re: The worst error message in history belongs to... BIND9! This is actually just the difference between sh and bash ... differences in, say, arithmetic handling and loops can sometimes mean rewriting parts of shell scripts depending on whether it is going to run in BSD or Linux. That's a major argument for doing things in python or perl as they are consistent across all platforms ... If one is going to require the installation of something that may not be part of a base system, that something might as well be bash :) Except that bash requires all the icky GNU utilities to build so you have to GNUify your system. The second you put in gmake, gmake requires iconv, readline and all the other nasty libraries, and from that point on if you build something you never know if it's going to link in to one of those libraries. Lots of programs use configure and if they don't see the gnu libraries they will use the more traditional bsd ones, but if they see the gnu stuff they will silently use it. For example, one I see a lot is programs using gdbm if they see it, and if they don't they will use ndbm. This can cause major problems for commercial users. I'd love for someone to modify the gmake port to have a variable you can set that would build all the GNUified dependency libraries, build and install gmake and statically link in all it's GNUified libraries, then remove all the GNUified libraries. Ted ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re[2]: The worst error message in history belongs to... BIND9!
On July 04, 2007 at 09:53AM Ted Mittelstaedt wrote: [snip] Actually perl has a lot of problems too. One of the biggest is that perl script writers always seem to think like you, in that perl is consistent across all platforms. The biggest problems I've seen with perl scripts are when people use perl extensions that are not on the system. You then have to go find the extension they use and very few of the perl script writers seem to be smart enough to put a section at the beginning of their scripts that define the CPAN location of the particular extensions they are using. The second biggest problem is perl script writers using constructs that are valid in Perl 5.6 and later but not valid in Perl 5.0 I don't know how many times I've wanted to strangle someone when trying to run a perl script under Perl 5.0 that had ONE single friggin statement in the entire thousand line script that isn't valid under 5.0 but is under 5.6 And I've also run across a number of Perl extensions that won't run under 5.0 as well, even though the authors are supposed to regression test under 5.0 I was under the impression that Perl 5.6.0 was released on 2000-Mar-22, while Perl 5.000 was issued on or about 1994-Oct-17. For the life of me, I cannot comprehend why anyone would be using such an antiquated version. I have a rather limited knowledge of Perl; however, I am not going to be bothered regression testing it under a seven year old obsoleted version. I believe that FreeBSD-3.4 was released around 12/21/1999 or there about. Should we also be testing against that version also? -- Gerard ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: The worst error message in history belongs to... BIND9!
On Wed, Jul 04, 2007 at 12:26:01PM +0100, RW wrote: On Tue, 3 Jul 2007 22:05:50 -0600 Chad Perrin [EMAIL PROTECTED] wrote: On Tue, Jul 03, 2007 at 11:41:13PM -0400, Robert Huff wrote: Chad Perrin writes: Isn't Perl part of the base system these days? Perl has not been part of the base system for several years and was deprecated for some time before that. Is it part of the default install without being part of the base system, then? I don't recall needing to install it after system install on this laptop (using FreeBSD 6.2-RELEASE). A huge number of ports and packages have it as a dependency. Yes, of course -- there's a great deal of Perl-based software on various unices that is written in Perl. I seem to recall having Perl available before I had most of my usual software installed on this system, however. In retrospect, though, I think something associated with Portupgrade uses Perl -- and I would have had that installed by the time I recall having Perl available -- so that's probably the culprit in this case. -- CCD CopyWrite Chad Perrin [ http://ccd.apotheon.org ] print substr(Just another Perl hacker, 0, -2); ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: OT: Re: The worst error message in history belongs to... BIND9!
How far do we get to go back in time? From the first online fortran compiler: ugh1 and ugh2. In fairness these were conditions that were not supposed to happen, but somehow they always do. In more recent times I always liked, invalid page fault this perhaps as late as win98. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: OT: Re: The worst error message in history belongs to... BIND9!
Andrea Venturoli wrote: Robert Huff wrote: =?iso-8859-1?Q?Kyrre_Nyg=E5rd?= writes: It has to be the worst written error message in history. Not even close. I commend to you the Amiga's BSOD: Software Guru Meditation Number very long string of hex digits Well, there's always Windows' Insufficient Memory, which usually means anything but memory being full :-) Unable to delete file: not enough free space available. Fatal error: the operation completed successfully -- Fuzzy love, -CyberLeo Technical Administrator CyberLeo.Net Webhosting http://www.CyberLeo.Net [EMAIL PROTECTED] Furry Peace! - http://www.fur.com/peace/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: OT: Re: The worst error message in history belongs to... BIND9!
On Wed, 4 Jul 2007, CyberLeo Kitsana wrote: Andrea Venturoli wrote: Robert Huff wrote: =?iso-8859-1?Q?Kyrre_Nyg=E5rd?= writes: It has to be the worst written error message in history. Not even close. I commend to you the Amiga's BSOD: Software Guru Meditation Number very long string of hex digits Well, there's always Windows' Insufficient Memory, which usually means anything but memory being full :-) Unable to delete file: not enough free space available. Fatal error: the operation completed successfully -- IBM: keyboard no present, press F1 to continue. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: OT: Re: The worst error message in history belongs to... BIND9!
Eduardo Viruena Silva wrote: On Wed, 4 Jul 2007, CyberLeo Kitsana wrote: Andrea Venturoli wrote: Robert Huff wrote: =?iso-8859-1?Q?Kyrre_Nyg=E5rd?= writes: It has to be the worst written error message in history. Not even close. I commend to you the Amiga's BSOD: Software Guru Meditation Number very long string of hex digits Well, there's always Windows' Insufficient Memory, which usually means anything but memory being full :-) Unable to delete file: not enough free space available. Fatal error: the operation completed successfully -- IBM: keyboard no present, press F1 to continue. Perhaps this has been mentioned before from Unix, I don't know: Bad Magic Number -- Tim Daneliuk [EMAIL PROTECTED] PGP Key: http://www.tundraware.com/PGP/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: The worst error message in history belongs to... BIND9!
If one is going to require the installation of something that may not be part of a base system, that something might as well be bash :) Except that bash requires all the icky GNU utilities to build so you have to GNUify your system. And perl doesn't? It was GPL last I knew. The second you put in gmake, gmake requires iconv, readline and all the other nasty libraries, and from that point on if you build something you never know if it's going to link in to one of those libraries. ... This can cause major problems for commercial users. How? Last I heard, the *L*GPL only requires making the *library* source available (and that only if the library has been modified). It doesn't extend to the using application. I'd love for someone to modify the gmake port to have a variable you can set that would build all the GNUified dependency libraries, build and install gmake and statically link in all it's GNUified libraries, then remove all the GNUified libraries. Or, change all the gnu ports to install into something like /usr/local/gnu or /usr/local/gpl instead of straight into /usr/local. You'd still have the gnu libs when needed, but without having them included in normal search paths. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: The worst error message in history belongs to... BIND9!
[EMAIL PROTECTED] wrote: If one is going to require the installation of something that may not be part of a base system, that something might as well be bash :) Except that bash requires all the icky GNU utilities to build so you have to GNUify your system. And perl doesn't? It was GPL last I knew. The entirety of Perl falls under the GPL and Artistic license at this time. Read the perl-porters archives for more debate on Perl licensing. The second you put in gmake, gmake requires iconv, readline and all the other nasty libraries, and from that point on if you build something you never know if it's going to link in to one of those libraries. ... This can cause major problems for commercial users. How? Last I heard, the *L*GPL only requires making the *library* source available (and that only if the library has been modified). It doesn't extend to the using application. I'd love for someone to modify the gmake port to have a variable you can set that would build all the GNUified dependency libraries, build and install gmake and statically link in all it's GNUified libraries, then remove all the GNUified libraries. Or, change all the gnu ports to install into something like /usr/local/gnu or /usr/local/gpl instead of straight into /usr/local. You'd still have the gnu libs when needed, but without having them included in normal search paths. That would seriously muck up a lot of people's assumptions on locations for programs, and would be incredibly necessary. Plus it would make searching for programs in $PATH a slight bit more time consuming (on the order of milliseconds I know, but those milliseconds are the exact reason why I have to manually profile pkg_install to determine bottlenecks). Also, please don't muck up email addresses. It's not cool, by any means. -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: The worst error message in history belongs to... BIND9!
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Martin McCormick Then, there is the ultimate, the Check engine. light on the modern car. Check engine - CEL It would be so nice if it said some indication as to the seriousness of the problem so that one knows whether to get it fixed now and maybe save $5,000 worth of repair costs or let it slide a few days until a better time. Most people take the tack that if the CEL comes on and the engine is still running and the car still goes, that they can let it slide. Ted ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: The worst error message in history belongs to... BIND9!
Reminds me of a typical windows user i dealt with who saw an error about explorer.exe and how it could not be read and let it slide. :-P using my wicked non user friendly skillz of the damned, i personally like the concept of a simple pebkac error when bind refuses to start due to a named.conf setting or similar. sortof creates a challenge, an adventure to find what's causing the issue yourself. wait. i shouldn't be promoting ideas on how make things worse off on freebsd-questions. pardon this useless email. -ben Ted Mittelstaedt wrote: -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Martin McCormick Then, there is the ultimate, the Check engine. light on the modern car. Check engine - CEL It would be so nice if it said some indication as to the seriousness of the problem so that one knows whether to get it fixed now and maybe save $5,000 worth of repair costs or let it slide a few days until a better time. Most people take the tack that if the CEL comes on and the engine is still running and the car still goes, that they can let it slide. Ted ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: The worst error message in history belongs to... BIND9!
On Mon, Jul 02, 2007 at 03:11:56PM -0500, Martin McCormick wrote: #! /bin/sh a = 5 that's enough to make it happen. Run that, and you get: a: not found Interestingly enough, if you run that same script in a Debian Linux environment, you get: ./testfile: line 2: a: command not found This is actually just the difference between sh and bash. You'll see the latter error if you type `a = 5` in bash in any OS. It just so happens that most Linux distributions don't have a real sh: [EMAIL PROTECTED] ~]$ uname -s Linux [EMAIL PROTECTED] ~]$ ls -l `which bash sh` -rwxr-xr-x 1 root root 616248 Aug 13 2006 /bin/bash lrwxrwxrwx 1 root root 4 Mar 25 20:36 /bin/sh - bash -- Paul Chvostek [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: The worst error message in history belongs to... BIND9!
Paul Chvostek writes: This is actually just the difference between sh and bash. You'll see the latter error if you type `a = 5` in bash in any OS. It just so happens that most Linux distributions don't have a real sh: I kind of thought that was the real issue. While something like this is maybe slightly annoying at times, the differences in, say, arithmetic handling and loops can sometimes mean rewriting parts of shell scripts depending on whether it is going to run in BSD or Linux. Martin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: The worst error message in history belongs to... BIND9!
On Tue, 03 Jul 2007 08:44:14 -0500 Martin McCormick [EMAIL PROTECTED] wrote: Paul Chvostek writes: This is actually just the difference between sh and bash. You'll see the latter error if you type `a = 5` in bash in any OS. It just so happens that most Linux distributions don't have a real sh: I kind of thought that was the real issue. While something like this is maybe slightly annoying at times, the differences in, say, arithmetic handling and loops can sometimes mean rewriting parts of shell scripts depending on whether it is going to run in BSD or Linux. That's why there is a POSIX standard, and why many people think it's bad idea to get into the habit of using bash specific scripts. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: The worst error message in history belongs to... BIND9!
You could make it more zen-like, perhaps: You are out of tune with the Universe, grasshopper. Continue your studies And, if everything was correct it could issue: awakening has been attained, entering zazen Ted -Original Message- From: nawcom [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 03, 2007 2:24 AM To: Ted Mittelstaedt Cc: freebsd-questions@freebsd.org Subject: Re: The worst error message in history belongs to... BIND9! Reminds me of a typical windows user i dealt with who saw an error about explorer.exe and how it could not be read and let it slide. :-P using my wicked non user friendly skillz of the damned, i personally like the concept of a simple pebkac error when bind refuses to start due to a named.conf setting or similar. sortof creates a challenge, an adventure to find what's causing the issue yourself. wait. i shouldn't be promoting ideas on how make things worse off on freebsd-questions. pardon this useless email. -ben Ted Mittelstaedt wrote: -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Martin McCormick Then, there is the ultimate, the Check engine. light on the modern car. Check engine - CEL It would be so nice if it said some indication as to the seriousness of the problem so that one knows whether to get it fixed now and maybe save $5,000 worth of repair costs or let it slide a few days until a better time. Most people take the tack that if the CEL comes on and the engine is still running and the car still goes, that they can let it slide. Ted ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: The worst error message in history belongs to... BIND9!
On Tue, Jul 03, 2007, Martin McCormick wrote: Paul Chvostek writes: This is actually just the difference between sh and bash. You'll see the latter error if you type `a = 5` in bash in any OS. It just so happens that most Linux distributions don't have a real sh: I kind of thought that was the real issue. While something like this is maybe slightly annoying at times, the differences in, say, arithmetic handling and loops can sometimes mean rewriting parts of shell scripts depending on whether it is going to run in BSD or Linux. That's a major argument for doing things in python or perl as they are consistent across all platforms. While perl has a well deserved reputation for looking like modem noise, it's certainly no worse than shell scripts. Pure /bin/sh is very limited in its constructs compared to other shells such as ksh, bash, etc. Bill -- INTERNET: [EMAIL PROTECTED] Bill Campbell; Celestial Software LLC URL: http://www.celestial.com/ PO Box 820; 6641 E. Mercer Way FAX:(206) 232-9186 Mercer Island, WA 98040-0820; (206) 236-1676 Marijuana will be legal some day, because the many law students who now smoke pot will someday become congressmen and legalize it in order to protect themselves. -- Lenny Bruce ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: The worst error message in history belongs to... BIND9!
On Tue, 2007-07-03 at 09:36 -0700, Bill Campbell wrote: On Tue, Jul 03, 2007, Martin McCormick wrote: Paul Chvostek writes: This is actually just the difference between sh and bash. You'll see the latter error if you type `a = 5` in bash in any OS. It just so happens that most Linux distributions don't have a real sh: I kind of thought that was the real issue. While something like this is maybe slightly annoying at times, the differences in, say, arithmetic handling and loops can sometimes mean rewriting parts of shell scripts depending on whether it is going to run in BSD or Linux. That's a major argument for doing things in python or perl as they are consistent across all platforms. While perl has a well deserved reputation for looking like modem noise, it's certainly no worse than shell scripts. Pure /bin/sh is very limited in its constructs compared to other shells such as ksh, bash, etc. Bill -- INTERNET: [EMAIL PROTECTED] Bill Campbell; Celestial Software LLC URL: http://www.celestial.com/ PO Box 820; 6641 E. Mercer Way FAX:(206) 232-9186 Mercer Island, WA 98040-0820; (206) 236-1676 Marijuana will be legal some day, because the many law students who now smoke pot will someday become congressmen and legalize it in order to protect themselves. -- Lenny Bruce sh should always be sh compatible on every platform (surprisingly). It may even be defined in one of the POSIX standards. This is why you write shell scripts in sh, even if you prefer csh, ksh or bash as your actual shell. Tom signature.asc Description: This is a digitally signed message part
Re: The worst error message in history belongs to... BIND9!
This is actually just the difference between sh and bash ... differences in, say, arithmetic handling and loops can sometimes mean rewriting parts of shell scripts depending on whether it is going to run in BSD or Linux. That's a major argument for doing things in python or perl as they are consistent across all platforms ... If one is going to require the installation of something that may not be part of a base system, that something might as well be bash :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: The worst error message in history belongs to... BIND9!
On Tue, Jul 03, 2007 at 07:34:20PM -0700, [EMAIL PROTECTED] wrote: This is actually just the difference between sh and bash ... differences in, say, arithmetic handling and loops can sometimes mean rewriting parts of shell scripts depending on whether it is going to run in BSD or Linux. That's a major argument for doing things in python or perl as they are consistent across all platforms ... If one is going to require the installation of something that may not be part of a base system, that something might as well be bash :) Isn't Perl part of the base system these days? -- CCD CopyWrite Chad Perrin [ http://ccd.apotheon.org ] Amazon.com interview candidate: When C++ is your hammer, everything starts to look like your thumb. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: The worst error message in history belongs to... BIND9!
Chad Perrin writes: Isn't Perl part of the base system these days? Perl has not been part of the base system for several years and was deprecated for some time before that. Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: The worst error message in history belongs to... BIND9!
On Tue, Jul 03, 2007 at 11:41:13PM -0400, Robert Huff wrote: Chad Perrin writes: Isn't Perl part of the base system these days? Perl has not been part of the base system for several years and was deprecated for some time before that. Is it part of the default install without being part of the base system, then? I don't recall needing to install it after system install on this laptop (using FreeBSD 6.2-RELEASE). -- CCD CopyWrite Chad Perrin [ http://ccd.apotheon.org ] Baltasar Gracian: A wise man gets more from his enemies than a fool from his friends. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: The worst error message in history belongs to... BIND9!
On Tue, Jul 03, 2007, [EMAIL PROTECTED] wrote: This is actually just the difference between sh and bash ... differences in, say, arithmetic handling and loops can sometimes mean rewriting parts of shell scripts depending on whether it is going to run in BSD or Linux. That's a major argument for doing things in python or perl as they are consistent across all platforms ... If one is going to require the installation of something that may not be part of a base system, that something might as well be bash :) One of the reasons I started using perl almost 20 years ago was that it was cleaner and more consistent than tying a bunch of utilities together with the shell (not to mention only having to master one type of regular expressions :-). I now use python for the vast majority of my development work instead of perl as I find it much cleaner with better object oriented features. When I write shell scripts, I use a very limited set of features which are /bin/sh compatible. As soon as I start having to do anything much more than run a program against a list of files, I switch to python. Bill -- INTERNET: [EMAIL PROTECTED] Bill Campbell; Celestial Software LLC URL: http://www.celestial.com/ PO Box 820; 6641 E. Mercer Way FAX:(206) 232-9186 Mercer Island, WA 98040-0820; (206) 236-1676 ``Intellectually, teachers fall between education theorists and bright cocker spaniels. (Probably closer to the education theorists. The AKC has been doing wonders with spaniels.) If you think I'm kidding look at the GREs for education majors, whose scores are the lowest of all fields, and remember that these are the smart ones.'' -- http://www.FredOnEverything.net ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: The worst error message in history belongs to... BIND9!
On Tue, Jul 03, 2007 at 09:29:03PM -0700, Bill Campbell wrote: On Tue, Jul 03, 2007, [EMAIL PROTECTED] wrote: This is actually just the difference between sh and bash ... differences in, say, arithmetic handling and loops can sometimes mean rewriting parts of shell scripts depending on whether it is going to run in BSD or Linux. That's a major argument for doing things in python or perl as they are consistent across all platforms ... If one is going to require the installation of something that may not be part of a base system, that something might as well be bash :) One of the reasons I started using perl almost 20 years ago was that it was cleaner and more consistent than tying a bunch of utilities together with the shell (not to mention only having to master one type of regular expressions :-). I now use python for the vast majority of my development work instead of perl as I find it much cleaner with better object oriented features. I'm of a similar mind, except that for OOP stuff I prefer Ruby, and for non-OOP stuff I still generally use Perl. Python doesn't really whet my whistle, so to speak. When I write shell scripts, I use a very limited set of features which are /bin/sh compatible. As soon as I start having to do anything much more than run a program against a list of files, I switch to python. $language =~ s/python/Perl/ Otherwise, ditto what you said. Much like PHP, I find that shell languages as scripting syntaxes don't really scale well in terms of maintainability. YMMV, of course. -- CCD CopyWrite Chad Perrin [ http://ccd.apotheon.org ] Baltasar Gracian: A wise man gets more from his enemies than a fool from his friends. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: The worst error message in history belongs to... BIND9!
Jeffrey Goldberg writes: I still remember as a newcomer to Unix a long long time ago getting Bad magic number In retrospect, I suspect that I'd typed ld where I'd meant to type ls. I have been doing things on Unix systems since about 1990 and the thing I run across that makes me ready to split a brick with my bare hands to this very day is the not found message one can get in a badly written shell script such as the following: #! /bin/sh a = 5 that's enough to make it happen. Run that, and you get: a: not found Interestingly enough, if you run that same script in a Debian Linux environment, you get: ./testfile: line 2: a: command not found Most of you will probably instantly see what I did wrong in that there shouldn't be any spaces between the variable name, the = sign and the 5 which could be anything else. I just picked a 5 for the heck of it. If you are in a big messy shell script, just seeing a: not found Doesn't tell me much except I know it's not working. The problem could be either that there is a typo or it could be that $a is null. I usually find that I snuck a space in and didn't even think about it at the time. I don't know if error messages from other OS's are off limits, but some of the ones from the most widely-used OS on Earth are treasures. How about running a gigantic piece of commercial software that does God knows what on your computer, and getting an error like: The software has performed an illegal operation. I bet there is a second line that they had to print in text using the same forground and background color so as to keep from getting fired that reads: Now, try and find it. Ha ha ha ha! Then, there is the ultimate, the Check engine. light on the modern car. It would be so nice if it said some indication as to the seriousness of the problem so that one knows whether to get it fixed now and maybe save $5,000 worth of repair costs or let it slide a few days until a better time. I like the quotation I read once that said that Unix is a user-friendly operating system. It is just particular about who it makes friends with. Martin McCormick WB5AGZ Stillwater, OK Systems Engineer OSU Information Technology Department Network Operations Group ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: The worst error message in history belongs to... BIND9!
On Thursday 31 May 2007, Tom Wilson wrote: I always liked one of the messages from an old version of the VMS (4 or 5?) C compiler(may not be exactly it, but this was included): Bad Code Or the Level I BASIC error messages on a TRS-80. What? How? Sorry? And that's all folks. The entire repertoire of error reporting on Level I Basic :-) Of course, fitting a BASIC interpretor and OS into only 4K of ROM was quite an achievement in itself. I doubt there were many spare bytes for more informative error reports. -- Dave ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
