the years, so
i don't think it's a hardware problem.
- the network/LAN named tries to sent UDP packet is somehow flooded.
Dns is probably fairly busy. It's the primary authorative dns for
some busy domains. Is there a setting I can do to increase the
limits of UDP packets to keep
on multiple servers over the years, so
i don't think it's a hardware problem.
- the network/LAN named tries to sent UDP packet is somehow flooded.
Dns is probably fairly busy. It's the primary authorative dns for
some busy domains. Is there a setting I can do to increase the
limits of UDP
on multiple servers over the years, so
i don't think it's a hardware problem.
- the network/LAN named tries to sent UDP packet is somehow flooded.
Dns is probably fairly busy. It's the primary authorative dns for
some busy domains. Is there a setting I can do to increase
On Tue, Jun 2, 2009 at 4:46 PM, Wojciech Puchar
woj...@wojtek.tensor.gdynia.pl wrote:
lot of searching and have found others with similar problems, but no
solutions.
named[69750]: client *ip removed*: error sending response: not
enough free resources
named[69750]: client *ip removed
snip
- the network/LAN named tries to sent UDP packet is somehow flooded.
Dns is probably fairly busy. It's the primary authorative dns for
some busy domains. Is there a setting I can do to increase the
limits of UDP packets to keep it from causing problems?
/snip
If you extend
Chris St Denis wrote:
Steve Bertrand wrote:
What type of device is em1 attached to? Is it a switch or a hub? Is it
possible to upgrade this? You should upgrade it to 100 (or 1000)
anyways. Does this device show any collisions?
This is a dedicated server in a datacenter. I don't know the
On Monday 20 April 2009 23:48:47 Tim Judd wrote:
I include the following ldd output in case it's helpful. What could
possibly
be the issue here?
Mark
###
# ldd /usr/sbin/named
/usr/sbin/named:
libcrypto.so.4 = /lib/libcrypto.so.4 (0x281ff000)
libxml2.so.5
We had problem with named starting on boot on a FreeBSD 6.1 server,
managed
by /etc/rc.conf.
The startup script failed with errors about shared library libm.so.2
failing
to load because of something related to libxml2.so.5.
Later, when I then tried starting it via /etc/rc.d/named
Mark Stosberg wrote:
We had problem with named starting on boot on a FreeBSD 6.1 server,
managed
by /etc/rc.conf.
The startup script failed with errors about shared library libm.so.2
failing
to load because of something related to libxml2.so.5.
Later, when I then tried starting it via
On Tuesday 21 April 2009 14:21:12 Manolis Kiagias wrote:
Mark Stosberg wrote:
We had problem with named starting on boot on a FreeBSD 6.1 server,
managed
by /etc/rc.conf.
The startup script failed with errors about shared library libm.so.2
failing
to load because of something
Agreed. Bind 9.5 and higher from ports has XML statistics support. That
explains the xml and iconv. ldd -a /usr/sbin/named should show you which one
wants libm.so.2 which is from the 4.x days.
If you don't need these statistics, I would suggest turning them off through
make config
We had problem with named starting on boot on a FreeBSD 6.1 server, managed
by /etc/rc.conf.
The startup script failed with errors about shared library libm.so.2 failing
to load because of something related to libxml2.so.5.
Later, when I then tried starting it via /etc/rc.d/named it worked fine
On Mon, Apr 20, 2009 at 2:20 PM, Mark Stosberg m...@summersault.com wrote:
We had problem with named starting on boot on a FreeBSD 6.1 server,
managed
by /etc/rc.conf.
The startup script failed with errors about shared library libm.so.2
failing
to load because of something related
On Mon, Apr 20, 2009 at 2:20 PM, Mark Stosberg m...@summersault.com wrote:
We had problem with named starting on boot on a FreeBSD 6.1 server,
managed
by /etc/rc.conf.
The startup script failed with errors about shared library libm.so.2
failing
to load because of something related
'ath_rx_tap':
../../../dev/ath/if_ath.c:3414: error: 'const struct ath_rx_status' has no
member named 'rs_flags'
../../../dev/ath/if_ath.c:3416: error: 'const struct ath_rx_status' has no
member named 'rs_flags'
*** Error code 1
Stop in /usr/src/sys/i386/compile/WITCH.
I read some mail and paper about
../../../dev/ath/if_ath.c: In function 'ath_rx_tap':
../../../dev/ath/if_ath.c:3414: error: 'const struct ath_rx_status' has no
member named 'rs_flags'
../../../dev/ath/if_ath.c:3416: error: 'const struct ath_rx_status' has no
member named 'rs_flags'
*** Error code 1
Stop in /usr/src/sys/i386/compile
/usr/src/sys/modules/ath/../../dev/ath/if_ath.c: In function 'ath_rx_tap':
/usr/src/sys/modules/ath/../../dev/ath/if_ath.c:3414: error: 'const struct
ath_rx_status' has no member named 'rs_flags'
/usr/src/sys/modules/ath/../../dev/ath/if_ath.c:3416: error: 'const struct
ath_rx_status' has no member
tethys ocean wrote:
thank a lot i found info in UPDATING just below
20090312:
The open-source Atheros HAL has been merged from HEAD
to STABLE.
The kernel compile-time option AH_SUPPORT_AR5416 has been
added to support certain newer Atheros parts, particularly
PCI-Express chipsets.
No, this is my first attempt with named and dhcpd. Each one seems
to be fine separately but getting them to talk has been a stumbling
block.
Then you'll have to share pieces of your configuration, so we can see
what is going on there.
Maybe also share the information that you used to set
I am getting the following messages on a bind server running Release-7.0:
Mar 11 23:05:56 nameserver named[674]: client 192.168.xxx.xxx#49165: update
'domain.local/IN' denied
Mar 11 23:05:56 nameserver dhcpd: if desktop.domain.local IN A rrset doesn't
exist add desktop.domain.local 1800
Hi Greg,
The desktops that grab an address from the DHCP pool are not getting
added in for named resolution. I am apparently missing something
with the communication between named and dhcpd. Any help would be
appreciated.
There are many reasons why the dhcpd cannot communicate with named
No, this is my first attempt with named and dhcpd. Each one seems to be fine
separately but getting them to talk has been a stumbling block.
Thanks,
Greg
Greg Stark -- Sent from my Windows Mobile® phone.
-Original Message-
From: Olivier Nicole o...@cs.ait.ac.th
Sent: Thursday, March
bind 9.4.2/FreeBSD 7.0 seems to be ignoring many settings I enter in
/etc/namedb/named.conf. zones are being properly served internally, but
can't query or transfer from the outside.
listen-on {216.154.117.227; 192.168.1.1;};
listen-on-v6 { none; };
tcp6 0 0 ::1.953
On Wednesday 31 December 2008 06:03:45 le...@edpausa.com wrote:
bind 9.4.2/FreeBSD 7.0 seems to be ignoring many settings I enter in
/etc/namedb/named.conf. zones are being properly served internally, but
can't query or transfer from the outside.
listen-on {216.154.117.227; 192.168.1.1;};
; 192.168.1.1;};
listen-on-v6 { none; };
I wonder if the spaces around curly braces that named examples always
use are mandatory? As in listen-on { 216.154.117.227; 192.168.1.1; };
tcp6 0 0 ::1.953*.*LISTEN
tcp4 0 0 127.0.0.1.953
On Fri, 21 Nov 2008 16:47:50 -0800
Nerius Landys [EMAIL PROTECTED] wrote:
I believe that the fix for this is to add a dependency
to /etc/rc.d/ntpd script, adding named to REQUIRE section in
comments. In your opinion, is this a robust fix? For example the
line in my /etc/rc.d/ntpd script
This shouldn't be needed as ntpd already requires ntpdate and in
turn ntpdate requires named. The issue is probably timing - that named
isn't ready.
Actually, the REQUIRE thing in the /etc/rc.d scripts means if the
required service is enabled, start it before this one. It does not
mean start
On Fri, 5 Dec 2008 13:22:29 -0800
Nerius Landys [EMAIL PROTECTED] wrote:
This shouldn't be needed as ntpd already requires ntpdate and in
turn ntpdate requires named. The issue is probably timing - that
named isn't ready.
Actually, the REQUIRE thing in the /etc/rc.d scripts means
understand why enabling ntpdate in
rc.conf fixed my problem of ntpd's DNS resolver child process not
completing (returning). My guess was that NETWORK and named were
guaranteed getting run before ntpd if I included ntpdate in rc.conf.
I thought that perhaps NETWORK and named were not getting run before
ntpd
RW wrote:
On Fri, 21 Nov 2008 16:47:50 -0800
Nerius Landys [EMAIL PROTECTED] wrote:
I believe that the fix for this is to add a dependency
to /etc/rc.d/ntpd script, adding named to REQUIRE section in
comments. In your opinion, is this a robust fix? For example the
line in my /etc/rc.d
On Sat, 06 Dec 2008 01:11:38 +0100
cpghost [EMAIL PROTECTED] wrote:
RW wrote:
I have a similar issue with PPP not having connected by the time
ntpdate runs , so I just have a script that runs between named and
ntpdate, and blocks waiting for access.
Those timing / start-order issues
processes remains, and the clock gets adjusted.
I have named running as a caching name server on my system. The contents of
my /etc/resolv.conf:
domain nerius.com
nameserver 127.0.0.1
My /etc/rc.conf:
...
named_enable=YES
ntpd_enable=YES
...
I believe that the problem with ntpd
processes remains, and the clock gets adjusted.
I have named running as a caching name server on my system. The contents of
my /etc/resolv.conf:
domain nerius.com
nameserver 127.0.0.1
My /etc/rc.conf:
...
named_enable=YES
ntpd_enable=YES
...
I believe that the problem with ntpd
I don't know why those processes are hung after boot, but in order to
troubleshoot the problem, I suggest that you modify the /etc/rc.d/ntpd
script to invoke ntpd from truss and log the output to a file, e.g.
/tmp/truss.log.$$. Once you've rebooted, kill the processes and post
the the log
When ntpd first starts up, it forks a child process to perform DNS
resolution of the timeservers listed in its config. If that fails, that
generally indicates that DNS was not working at the time, or something else
was going wrong with the network.
[ See ntpd/ntp_config.c, search for fork()
On Dec 3, 2008, at 1:01 PM, Nerius Landys wrote:
[ ... ]
Does anyone know why I'm getting 2 ntpd processes running after bootup
(and ntpd fails to adjust the clock as a result)? Any suggested fix
would be appreciated.
When ntpd first starts up, it forks a child process to perform DNS
on a running system it fixes the problem,
and only one of the ntpd processes remains, and the clock gets adjusted.
I have named running as a caching name server on my system. The contents of
my /etc/resolv.conf:
domain nerius.com
nameserver 127.0.0.1
My /etc/rc.conf
On Saturday 22 November 2008 01:47:50 Nerius Landys wrote:
Trying to reproduce problem. On a running system. I shut down named. Then
I restart ntpd, then I start named. I can reproduce the problem that
happens on bootup - ntpd has 2 processes and does not adjust the clock.
Restarting ntpd
remains, and the clock gets adjusted.
I have named running as a caching name server on my system. The contents of
my /etc/resolv.conf:
domain nerius.com
nameserver 127.0.0.1
My /etc/rc.conf:
...
named_enable=YES
ntpd_enable=YES
...
I believe that the problem with ntpd is that named
Thank you so much for this tip :)
it is just a simple syntax error in named.conf
it is running now
thank you so much!
2008/9/3 Sebastian Tymków [EMAIL PROTECTED]
Hello,
What is on logs ?
What do you have in your /etc/rc.conf for named ?
Best regards,
Shamrock
2008/9/3 Richard Yang
Hello,
What is on logs ?
What do you have in your /etc/rc.conf for named ?
Best regards,
Shamrock
2008/9/3 Richard Yang [EMAIL PROTECTED]
Hello,
When I tried /etc/rc.d/named forcestart, i got
./named: WARNING: run_rc_command: cannot run /etc/namedb/named
what does it mean and how do i
Hello,
When I tried /etc/rc.d/named forcestart, i got
./named: WARNING: run_rc_command: cannot run /etc/namedb/named
what does it mean and how do i fix this?
thanx
--
Best Regards
Richard Yang
[EMAIL PROTECTED]
[EMAIL PROTECTED]
___
freebsd
I build a 7.0 system from the CD and then updated it via cvs. The file
make-localhost (among) others is not in /etc/named.
So make sure I did not muck up mergemaster I did the following:
mkdir /var/tmp/root
cd /usr/src/etc
make DESTDIR=/var/tmp/root distrib-dirs distribution
and checked
On Sun, 10 Aug 2008, doug wrote:
I build a 7.0 system from the CD and then updated it via cvs. The file
make-localhost (among) others is not in /etc/named.
So make sure I did not muck up mergemaster I did the following:
mkdir /var/tmp/root
cd /usr/src/etc
make DESTDIR=/var/tmp/root
On Tue, 15 Jul 2008 12:22:06 +1000 jonathan michaels [EMAIL PROTECTED] wrote:
named now reports hourly
Jul 15 06:55:10 hid named[617]: could not listen on UDP socket: permission
denied
Jul 15 06:55:10 hid named[617]: creating IPv4 interface tun0 failed;
interface ignored
Jul 15
ian,
long time no scribble .. thanks much appreciated
On Tue, Jul 15, 2008 at 08:27:33PM +1000, Ian Smith wrote:
On Tue, 15 Jul 2008 12:22:06 +1000 jonathan michaels [EMAIL PROTECTED]
wrote:
named now reports hourly
Jul 15 06:55:10 hid named[617]: could not listen on UDP socket
On Tue, 15 Jul 2008, jonathan michaels wrote:
On Tue, Jul 15, 2008 at 08:27:33PM +1000, Ian Smith wrote:
On Tue, 15 Jul 2008 12:22:06 +1000 jonathan michaels [EMAIL PROTECTED]
wrote:
named now reports hourly
Jul 15 06:55:10 hid named[617]: could not listen on UDP
things different from 2.2.5 stuff that was taken for granted that never
tirned up as part of teh ansers to the few questions i'v managed to
ask. so frustrating .. moan mode off!
named now reports hourly
Jul 15 06:55:10 hid named[617]: could not listen on UDP socket: permission
denied
Jul 15 06
On Tue, Jul 15, 2008 at 12:22:06PM +1000, jonathan michaels wrote:
[...]
named now reports hourly
Jul 15 06:55:10 hid named[617]: could not listen on UDP socket: permission
denied
Jul 15 06:55:10 hid named[617]: creating IPv4 interface tun0 failed;
interface ignored
Jul 15 07:55:10 hid
Le Tue, 24 Jun 2008 21:48:42 +0300,
Manolis Kiagias [EMAIL PROTECTED] a écrit :
Nicolas Letellier wrote:
Hi.
I want to restart named in a script executed by a cron. My script
is:
#!/bin/sh
# verify named conf and restart it
/usr/sbin/named-checkconf
if [ ! $? -eq 0
Hi.
I want to restart named in a script executed by a cron. My script is:
#!/bin/sh
# verify named conf and restart it
/usr/sbin/named-checkconf
if [ ! $? -eq 0 ]; then
echo Errors when verifying named configuration
exit 1
else
/etc/rc.d/named restart /dev/null
fi
# Ok
On Tue, Jun 24, 2008 at 2:17 PM, Nicolas Letellier [EMAIL PROTECTED] wrote:
Hi.
I want to restart named in a script executed by a cron. My script is:
#!/bin/sh
# verify named conf and restart it
/usr/sbin/named-checkconf
if [ ! $? -eq 0 ]; then
echo Errors when verifying named
Nicolas Letellier wrote:
Hi.
I want to restart named in a script executed by a cron. My script is:
#!/bin/sh
# verify named conf and restart it
/usr/sbin/named-checkconf
if [ ! $? -eq 0 ]; then
echo Errors when verifying named configuration
exit 1
else
/etc/rc.d/named
On Tue, Jun 24, 2008 at 08:17:20PM +0200, Nicolas Letellier wrote:
Hi.
I want to restart named in a script executed by a cron. My script is:
#!/bin/sh
# verify named conf and restart it
/usr/sbin/named-checkconf
if [ ! $? -eq 0 ]; then
echo Errors when verifying named
Nicolas Letellier wrote:
Hi.
I want to restart named in a script executed by a cron. My script is:
#!/bin/sh
# verify named conf and restart it
/usr/sbin/named-checkconf
if [ ! $? -eq 0 ]; then
echo Errors when verifying named configuration
exit 1
else
/etc/rc.d/named
I have quite a bit of trouble with the /etc/rc.d/named script. The source
of the biggest issue was the rc_run_command was not issuing the run command
with /usr/sbin/named. It was just running the arguments w/o the executable.
e.g. -t /var/named vs. /usr/sbin/named -t /var/named
I have
At 02:19 PM 6/6/2008, Casey Scott wrote:
I have quite a bit of trouble with the /etc/rc.d/named script. The source
of the biggest issue was the rc_run_command was not issuing the run command
with /usr/sbin/named. It was just running the arguments w/o the executable.
e.g. -t /var/named vs
this behavior? Is the handbook wrong wrt setup
of named on a AMD64-system?
Thanks much in advance for any clue,
-ewald
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL
The handbook is slightly out of date and the 'make-localhost' script
is now history. Instead, the system comes with pre-installed
/etc/namedb/master/localhost-forward.db and .../localhost-reverse.db
zone files and the appropriate configuration shown in the example
named.conf file.
anybody else seen this behavior? Is the handbook wrong wrt setup
of named on a AMD64-system?
Thanks much in advance for any clue,
-ewald
The handbook is slightly out of date and the 'make-localhost' script
is now history. Instead, the system comes with pre-installed
/etc/namedb/master/localhost
On Wed, 9 Apr 2008 18:34:50 +0200, Ewald Jenisch [EMAIL PROTECTED] wrote:
The handbook is slightly out of date and the 'make-localhost' script
is now history. Instead, the system comes with pre-installed
/etc/namedb/master/localhost-forward.db and .../localhost-reverse.db
zone files and the
to a chroot of bind with
the tree owned by root. You can run bind in a sandbox as the
documentation says and have it chroot but if you do, and heres's
the confusion, you had better disable FreeBSD's attempt to make
sure the /var/named tree is always owned by root which would be
fine if named
, and heres's
the confusion, you had better disable FreeBSD's attempt to make
sure the /var/named tree is always owned by root which would be
fine if named ran as root.
When you run it in a sandbox with a lower-priority UID,
you must make sure that at least one more little line appears
as the
documentation says and have it chroot but if you do, and heres's
the confusion, you had better disable FreeBSD's attempt to make
sure the /var/named tree is always owned by root which would be
fine if named ran as root.
When you run it in a sandbox with a lower-priority UID,
you must make sure
in /var/named. When I do ls -ld on
/var/named, it's owned by root.
As I said, several systems do this and several more
don't and they are all running FreeBSD6.2 except for one which
is FreeBSD5.x.
I originally used the stock /etc/rc.d start script for
named. After getting the chown
and is owned by bind so it needs to
have write permission in /var/named. When I do ls -ld on
/var/named, it's owned by root.
As I said, several systems do this and several more
don't and they are all running FreeBSD6.2 except for one which
is FreeBSD5.x.
I originally used the stock /etc/rc.d
On Mar 20, 2008, at 4:30 PM, Martin McCormick wrote:
I reboot. Soon, I find that bind isn't running. It runs
as a low-priority process and is owned by bind so it needs to
have write permission in /var/named. When I do ls -ld on
/var/named, it's owned by root.
/var/named is owned
Chuck Swiger writes:
/var/named is owned by root on all of my newer (5.x and later)
systems; I found an old 4.11 box with it owned by bind, though. If
you're using named chroot'ed (as recommended), it will want /var/named/
var/{dump/log/run/stats} writable by bind.
That's pretty
At 08:59 PM 3/12/2008, jekillen wrote:
Hello:
I have named running as secondary server on v6.2
It will not start without a specific configuration file set
on the command line. After doing some investigation
it appears that that is because it runs chrooted and
there is not a symlink from /etc
On Thursday 13 March 2008 02:59:35 jekillen wrote:
I have named running as secondary server on v6.2
It will not start without a specific configuration file set
on the command line. After doing some investigation
it appears that that is because it runs chrooted and
there is not a symlink from
Hello:
I have named running as secondary server on v6.2
It will not start without a specific configuration file set
on the command line. After doing some investigation
it appears that that is because it runs chrooted and
there is not a symlink from /etc/namedb. Is that a correct
assumption? I
jekillen wrote:
Hello:
I have named running as secondary server on v6.2
It will not start without a specific configuration file set
on the command line. After doing some investigation
it appears that that is because it runs chrooted and
there is not a symlink from /etc/namedb. Is that a correct
People: please excuse me , but I tried another attempt to fix the issue
(I have installed the OS from the ISO image from which I installed
another box there named is running fine , but unfortunately in this
box its not running ), I can't trace it what went wrong ?
Named is not starting
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
dhaneshk k wrote:
|
| People: i have a strange issue with named services in my
freeBSD-6.2-Release Box
|
|
| (I have installed the OS from the ISO image from which I installed
another box there named is running fine , but unfortunately in this box
People: i have a strange issue with named services in my freeBSD-6.2-Release Box
(I have installed the OS from the ISO image from which I installed another box
there named is running fine , but unfortunately in this box its not running ),
I can't trace it what went wrong ?
Named
People:
I have a FreeBSD-6.2 installed fresh machine , I want this machine as my
Slave DNS server ,
here I can't start named service , Whats wrong with my box ? I cant find the
/usr/sbin/named executable in my machine ,
is it needed to install bind from ports collection ? just
host). One of the named record
database is for one of the sites. When I try to send
an E-mail from this message to list e-mail address. The messages
bounce for dns lookup failure.
The name that is being looked up is
mxhost.domainName.tld.targetDomainName.tld
Some how the two names are being
On Tue, Dec 11, 2007 at 18:23 , while impersonating an expert on
the internet, [EMAIL PROTECTED] sent this to stdout:
Date: Tue, 11 Dec 2007 06:09:11 -0600
From: Derek Ragona [EMAIL PROTECTED]
Subject: Re: named mystery
To: jekillen [EMAIL PROTECTED], User Questions
freebsd-questions
At 01:24 PM 12/11/2007, Bill Vermillion wrote:
On Tue, Dec 11, 2007 at 18:23 , while impersonating an expert on
the internet, [EMAIL PROTECTED] sent this to stdout:
Date: Tue, 11 Dec 2007 06:09:11 -0600
From: Derek Ragona [EMAIL PROTECTED]
Subject: Re: named mystery
To: jekillen [EMAIL
2007 06:09:11 -0600
From: Derek Ragona [EMAIL PROTECTED]
Subject: Re: named mystery
To: jekillen [EMAIL PROTECTED], User Questions
freebsd-questions@freebsd.org
At 12:57 AM 12/10/2007, jekillen wrote:
Hello:
[lots of stuff snipped - wjv]
I have two name servers for four domains
On Dec 11, 2007, at 11:24 AM, Bill Vermillion wrote:
On Tue, Dec 11, 2007 at 18:23 , while impersonating an expert on
the internet, [EMAIL PROTECTED] sent this to
stdout:
Date: Tue, 11 Dec 2007 06:09:11 -0600
From: Derek Ragona [EMAIL PROTECTED]
Subject: Re: named mystery
To: jekillen
have set up Postfix to act as a smart host
mail hub (the MX host). One of the named record
database is for one of the sites. When I try to send
an E-mail from this message to list e-mail address. The messages
bounce for dns lookup failure.
The name that is being looked up
Hello:
I have two name servers for four domains.
The primary name server is running FreeBSD v 6.0
and the secondary is running v 6.2.
I have an MX record for each of the four registered
domains. I have set up Postfix to act as a smart host
mail hub (the MX host). One of the named record
database
Hi:
I have recently tried to update to the latest snapshot, it appears that
named is not built/installed with build/installworld build targets:
The installed named depends on libcrypto.so.4 and libc.so.6, but
installworld, delete-old, delete-old-libs deletes these as they have
been
Hi list,
I've got the following.
Everytime when I start /etc/rc.d/named I get the following issue.
hulk# /etc/rc.d/named start
etc/namedb/master changed
user expected 0 found 53 modified
gid expected 0 found 53 modified
Starting named.
If I leave it like this I get the following
Erik Norgaard wrote:
Hi:
I have recently tried to update to the latest snapshot, it appears that
named is not built/installed with build/installworld build targets:
The installed named depends on libcrypto.so.4 and libc.so.6, but
installworld, delete-old, delete-old-libs deletes
Gelsema, P (Patrick) - FreeBSD wrote:
In /etc/rc.conf I got the following.
hulk# cat /etc/rc.conf | grep named
named_enable=YES
named_uid=bind
named_chrootdir=/var/named
grep named /etc/defaults/rc.conf
# named. It may be possible to run named in a sandbox, man security for
named_enable
When I change the ownership, problem goes away.
How can I get the problem away without changing the ownership?
in the options {} section
what do you have for:
options {
// Relative to the chroot directory
// named_chrootdir=/var/named
directory /etc/namedb
// named_chrootdir=/var/named
directory /etc/namedb;
pid-file/var/run/named/pid;
dump-file /var/dump/named_dump.db;
statistics-file /var/stats/named.stats;
.
acl home {10.202.77.0/24;127.0.0.1;};
options {
// Relative to the chroot directory
Check your make.conf
DOH! You're right, I was migrating from another system where I had build
of named disabled. If you ever pass by where I live, I'll invite you for
a beer ...
Cheers, Erik
___
freebsd-questions@freebsd.org mailing list
http
On Mon, December 3, 2007 23:03, Philip M. Gollucci wrote:
Gelsema, P (Patrick) - FreeBSD wrote:
In /etc/rc.conf I got the following.
hulk# cat /etc/rc.conf | grep named
named_enable=YES
named_uid=bind
named_chrootdir=/var/named
grep named /etc/defaults/rc.conf
# named. It may be possible
relative to the chroot, its
/var/named/var/dump
hulk# pwd
/var/named/var
hulk# ll
total 8
drwxr-xr-x 2 bind wheel 512 Aug 17 05:10 dump
drwxr-xr-x 2 bind wheel 512 Aug 17 05:10 log
drwxr-xr-x 3 bind wheel 512 Dec 3 15:46 run
drwxr-xr-x 2 bind wheel 512 Aug 17 05:10 stats
uhmpf
Philip M. Gollucci wrote:
Gelsema, P (Patrick) - FreeBSD wrote:
Ok.. In the /var directory there is no dump directory. So solving this I
should do the following:
hulk# mkdir /var/dump
hulk# chown bind:bind /var/dump
Well, if its relative to the chroot, its
/var/named/var/dump
/rc.d/named restart)
--
Philip M. Gollucci ([EMAIL PROTECTED])
o:703.549.2050x206
Senior System Admin - Riderway, Inc.
http://riderway.com / http://ridecharge.com
1024D/EC88A0BF 0DE5 C55C 6BF3 B235 2DAB B89E 1324 9B4F EC88 A0BF
Hello;
I am having some named problems:
The daemon will not start and run on system startup.
There is plenty of info on problems when named
is running, but not when it will not start.
I did get it to start after boot with
#named (su to root without - option)
It started and ran as demonstrated
Bind works perfectly out of the box on most FBSD recent versions.
You should not move things out of the path they have been setup to.
Specially on FBSD /etc is reserved for system files.
By default bind is installed in /var/named and should be kept there.
If I was you I would :
1. install
On Nov 25, 2007, at 1:58 PM, bsd wrote:
Bind works perfectly out of the box on most FBSD recent versions.
You should not move things out of the path they have been setup to.
Specially on FBSD /etc is reserved for system files.
By default bind is installed in /var/named and should be kept
To: freebsd-questions@freebsd.org
From: [EMAIL PROTECTED]
Date: Sun, 25 Nov 2007 11:19:27 -0800
Subject: named problems
Hello;
I am having some named problems:
The daemon will not start and run on system startup.
Add this line to the rc.conf
Hi;
I am getting the following messaged when named attempts to start
at system startup:
could not configure root hints from 'named.root': file not found
loading configuration: file not found
So what is supposed to tell this script where to find these files?
(in FreeBSD rc script context: i looked
In the handbook section 27.6.6.1 it tells me to use make-localhost.
27.6.6.1 Using make-localhost
To configure a master zone for the localhost visit the /etc/namedb
directory and run the following command:
# sh make-localhost
If all went well, a new file should exist in the master subdirectory.
101 - 200 of 514 matches
Mail list logo
