On Monday 12 November 2007 10:21:35 Johan Hendriks wrote:
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
HI
I am having problems with my zone file...
There used to be a command to run and check zone files/Named files..
I can't seem to locate it...??
Anyone have a clue??
TIA
User Iam
___
freebsd-questions@freebsd.org mailing list
http
I am having problems with my zone file...
There used to be a command to run and check zone files/Named files..
I can't seem to locate it...??
See named-checkzone(8) and named-checkconf(8)
David
--
David Robillard
UNIX systems administrator Oracle DBA
CISSP, RHCE Sun Certified Security
On Aug 29, 2007, at 7:56 PM, Wojciech Puchar wrote:
anyone here know a SMALL named and dhcpd servers?
small i mean no more than say 200kB both (just binaries). the
dumbest dhcpd would be enough (automatic assignment to all machines
on given interfaces), named just to keep single domain
anyone here know a SMALL named and dhcpd servers?
small i mean no more than say 200kB both (just binaries). the dumbest
dhcpd would be enough (automatic assignment to all machines on given
interfaces), named just to keep single domain and forward everything else
to master.
thank you
On Aug 29, 2007, at 10:56 AM, Wojciech Puchar wrote:
anyone here know a SMALL named and dhcpd servers?
small i mean no more than say 200kB both (just binaries). the
dumbest dhcpd would be enough (automatic assignment to all machines
on given interfaces), named just to keep single domain
Has Anyone tried to use Named under windows? What are results?
Regards,
Narek
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
On 8/25/07, Narek Gharibyan [EMAIL PROTECTED] wrote:
Has Anyone tried to use Named under windows? What are results?
I used bind on windows a couple years ago. Seemed to work as expected.
Official binary packages for Windows are available from isc.org
--
Noel Jones
I think this was it. I originally used sudo but second time I did it as su
and it went very well. Thank you!
I always build ports using sudo (I have not been using su for years).
Olivier
___
freebsd-questions@freebsd.org mailing list
Are you sure your run the make with sufficient priviledges?
I think this was it. I originally used sudo but second time
I did it as su and it went very well. Thank you!
If sudo to root does not give the same privs as su to root,
I'd guess sudo is either buggy or not configured properly.
Hello,
If sudo to root does not give the same privs as su to root,
I'd guess sudo is either buggy or not configured properly.
Not sure what to say. I had the same situation on two machines. It is
possible that my sudo is not configured properly but yet in a year's time
of living in UNIX world
I am using named version 9.3.3 which comes with FreeBSD system (i.e. was
not installed from ports).
I know that in order to upgrade bind, I should cvsup sources and then go
through the entire procudure of updating the system, installing kernel,
etc. However, I tend not to use cvsup any
Stop in /usr/ports/dns/bind9.
** Command failed [exit code 1]: /usr/bin/script -qa
/tmp/portinstall.12022.0 env make
** Fix the problem and try again.
** Listing the failed packages (*:skipped / !:failed)
! dns/bind9 (unknown build error)
--- Packages processed: 0 done, 0
Hello,
My question is: should I wait till freebsd-update tool includes an
update
of bind to 9.3.4 or should I update the system from sources? I can wait
but
I am just not sure what is the preferred method given that I use
freebsd-update on regular basis. This is FreeBSD 6.2-RELEASE-p5 #2
Hello,
On Wed, 1 Aug 2007 12:49:18 +0700 (ICT), Olivier Nicole [EMAIL PROTECTED]
wrote:
Stop in /usr/ports/dns/bind9.
** Command failed [exit code 1]: /usr/bin/script -qa
/tmp/portinstall.12022.0 env make
** Fix the problem and try again.
** Listing the failed packages (*:skipped /
Hello,
I am using named version 9.3.3 which comes with FreeBSD system (i.e. was
not installed from ports).
I know that in order to upgrade bind, I should cvsup sources and then go
through the entire procudure of updating the system, installing kernel,
etc. However, I tend not to use cvsup any
are not needed until the system is up multiuser, you
could specify the 'late' option on them in fstab, forcing them to be
delayed until /etc/rc.d/mountlate is run after /etc/rc.d/DAEMON has
completed. This will ensure that named is running prior to the mount,
since DAEMON requires SERVERS, which
Written by Tim Daneliuk on 07/13/07 17:29
While we're on the subject of dns ... I have nfs mounts configured in
/etc/fstab using the host *name*. When the system boots, it grumbles
about the name resolution because named has not yet been started. It
works fine because, by the time you have
While we're on the subject of dns ... I have nfs mounts configured in
/etc/fstab using the host *name*. When the system boots, it grumbles
about the name resolution because named has not yet been started. It
works fine because, by the time you have a fully booted system, named is
running
On Jul 13, 2007, at 3:29 PM, Tim Daneliuk wrote:
While we're on the subject of dns ... I have nfs mounts configured in
/etc/fstab using the host *name*. When the system boots, it grumbles
about the name resolution because named has not yet been started. It
works fine because, by the time you
Tim Daneliuk writes:
While we're on the subject of dns ... I have nfs mounts
configured in /etc/fstab using the host *name*. When the system
boots, it grumbles about the name resolution because named has
not yet been started. It works fine because, by the time you
have a fully booted
Hello,
This is interesting. I tried adding this to named.conf (adapted from man
named.conf)
/* logging {
channel namedlog {
file /var/log/named/nlog;
severity info;
print-time yes;
print
Hello,
On Wed, 11 Jul 2007 14:09:30 +0300, CK [EMAIL PROTECTED] wrote:
Zbigniew Szalbot wrote:
Now bind does not die but but it cannot find the log file:
logging channel 'simple_log' file '/var/log/named/nlog': file not found
ls /var/log/named/*
/var/log/named/nlog
Why would named
On Wed, 11 Jul 2007 at 13:16 +0200, [EMAIL PROTECTED] confabulated:
Hello,
On Wed, 11 Jul 2007 14:09:30 +0300, CK [EMAIL PROTECTED] wrote:
Zbigniew Szalbot wrote:
Now bind does not die but but it cannot find the log file:
logging channel 'simple_log' file '/var/log/named/nlog': file
Hello again,
Jul 11 13:06:03 szalbot named[3319]: logging channel 'simple_log' file
'/var/named/var/log/nlog': file not found
Jul 11 13:06:03 szalbot named[3319]: isc_log_open
'/var/named/var/log/nlog'
failed: file not found
I have it working with this:
logging {
channel
Zbigniew Szalbot wrote:
Now bind does not die but but it cannot find the log file:
logging channel 'simple_log' file '/var/log/named/nlog': file not found
ls /var/log/named/*
/var/log/named/nlog
Why would named not be able to find the log when it is there? The nlog file
is owned by user bind
Hello,
I am slowly trying various features of FBSD and I have just enabled named
to be my local caching DNS server. It works fine but I have one question.
I would like it to be a caching DNS server for my LAN.
So following the Handbook I tried setting a proper LAN IP address of the
named
:
Hello,
I am slowly trying various features of FBSD and I have just enabled named
to be my local caching DNS server. It works fine but I have one question.
I would like it to be a caching DNS server for my LAN.
So following the Handbook I tried setting a proper LAN IP address of the
named machine
After a recent disk failure, I left myself a note to add the DNS/DHCP
info to my backup.
I have a small, over-engineered for my education, network of 10
computers in my house. I run BIND with dynamic zones on my FreeBSD
server, I also use the DNS service on my Win2k-AD server. They both are
After a recent disk failure, I left myself a note to add the
DNS/DHCP info to my backup.
I have a small, over-engineered for my education, network of
10 computers in my house. I run BIND with dynamic zones on
my FreeBSD server, I also use the DNS service on my Win2k-AD
server.
On Mar 8, 2007, at 2:03 PM, Dan Nelson wrote:
[ ... ]
It would be nifty to make ndc/rndc smart enough to understand how to
find the pidfile under the chroot location.
rndc doesn't need to know where the pid is; it connects directly to
named over the control port (953) to do its magic. Try
HI there,
So I Have 6.2 install on my machine and restarting named gets the
following error.
any clues what is creating this?
# /etc/rc.d/named restart
Stopping named: rndc failed, trying killall: .
Starting named.
bind is starting just fine
Mar 8 13:34:47 named[52886]: starting BIND
On Mar 8, 2007, at 1:35 PM, Noah wrote:
So I Have 6.2 install on my machine and restarting named gets the
following error.
any clues what is creating this?
# /etc/rc.d/named restart
Stopping named: rndc failed, trying killall: .
By default, named runs in a chroot()ed environment under /var
In the last episode (Mar 08), Chuck Swiger said:
On Mar 8, 2007, at 1:35 PM, Noah wrote:
So I Have 6.2 install on my machine and restarting named gets the
following error.
any clues what is creating this?
# /etc/rc.d/named restart
Stopping named: rndc failed, trying killall
named is not starting when I reboot a FreeBSD 6.2 server and I cant figure
out why.
there are no error mesasges in /var/log/messages during the boot process.
even when I manually start there are no error messages.
# grep named /etc/rc.conf
named_enable=YES
# pkg_info | grep bind
bind9-9.3.4
In the newer versions of bind you need to add to /etc/rc.conf:
named_uid=username
you want to run named as.
-Derek
At 07:24 PM 2/26/2007, Noah Garrett Wallach wrote:
Hi there,
named is not starting when I reboot a FreeBSD 6.2 server and I cant figure
out why.
there are no error
Wojciech Puchar wrote:
named is not starting when I reboot a FreeBSD 6.2 server and I cant
figure
out why.
there are no error mesasges in /var/log/messages during the boot
process.
even when I manually start there are no error messages.
# grep named /etc/rc.conf
At 09:23 AM 02/27/2007, Noah Garrett Wallach wrote:
Wojciech Puchar wrote:
named is not starting when I reboot a FreeBSD 6.2 server and I cant
figure
out why.
there are no error mesasges in /var/log/messages during the boot
process.
even when I manually start there are no error
Hi there,
I am having troubles with named not starting on boot nor am I am able to
start it manually. I thought I have my chrootdir set correctly.
here are my settings in my rc.conf
s nip
named_enable=YES
named_uid=bind
named_program=/usr/local/sbin/named
named_flags=-c /etc
rolled my own version of Bind (9.4.0) and have it working
perfectly and starting under rc.conf
(I had to edit /etc/rc.d/named though)
hmm there's a port for 9.4, but since it doesnt have the options for DLZ
which i hear is now integrated i guess you need to roll your own for
that stuff. you could
Hi there,
I dont have a user name named. I have a user named bind. so bind is
what I am going with.
named_enable=YES
named_uid=bind
named_program=/usr/local/sbin/named
named_flags=-c /etc/namedb/named.conf
named_chrootdir=/var/named
cheers,
Noah
Derek Ragona wrote:
In the newer
Noah wrote:
Hi there,
I am having troubles with named not starting on boot nor am I am able to
start it manually. I thought I have my chrootdir set correctly.
here are my settings in my rc.conf
s nip
named_enable=YES
named_uid=bind
named_program=/usr/local/sbin/named
.
-Derek
At 11:21 AM 2/27/2007, Noah Garrett Wallach wrote:
Hi there,
I dont have a user name named. I have a user named bind. so bind is what
I am going with.
named_enable=YES
named_uid=bind
named_program=/usr/local/sbin/named
named_flags=-c /etc/namedb/named.conf
named_chrootdir=/var/named
Noah wrote:
Hi there,
I am having troubles with named not starting on boot nor am I am able to
start it manually. I thought I have my chrootdir set correctly.
here are my settings in my rc.conf
s nip
named_enable=YES
named_uid=bind
named_program=/usr/local/sbin/named
Vince wrote:
Noah wrote:
Hi there,
I am having troubles with named not starting on boot nor am I am able to
start it manually. I thought I have my chrootdir set correctly.
here are my settings in my rc.conf
s nip
named_enable=YES
named_uid=bind
named_program=/usr/local/sbin
Hi there,
named is not starting when I reboot a FreeBSD 6.2 server and I cant
figure out why.
there are no error mesasges in /var/log/messages during the boot process.
even when I manually start there are no error messages.
# grep named /etc/rc.conf
named_enable=YES
# pkg_info | grep bind
Noah Garrett Wallach wrote:
Hi there,
named is not starting when I reboot a FreeBSD 6.2 server and I cant
figure out why.
there are no error mesasges in /var/log/messages during the boot process.
even when I manually start there are no error messages.
Have you tried with -fg
Kevin,
those were manual restarts.
cheers,
Noah
Kevin Kinsey wrote:
Noah Garrett Wallach wrote:
Hi there,
named is not starting when I reboot a FreeBSD 6.2 server and I cant
figure out why.
there are no error mesasges in /var/log/messages during the boot
process.
even when I
Hello.
I'm getting this on several different 6.x servers:
# sh /etc/rc.d/named restart
Stopping named.
named already running? (pid=xxx).
and named won't restart; if I then
# sh /etc/rc.d/named start
Starting named.
it works fine.
Is this happening to other people? What could
Hi,
Andrea Venturoli schrieb:
I'm getting this on several different 6.x servers:
# sh /etc/rc.d/named restart
Stopping named.
named already running? (pid=xxx).
and named won't restart; if I then
# sh /etc/rc.d/named start
Starting named.
it works fine.
Is this happening
On 2007-02-16 22:56, Andrea Venturoli [EMAIL PROTECTED] wrote:
Hello.
I'm getting this on several different 6.x servers:
# sh /etc/rc.d/named restart
Stopping named.
named already running? (pid=xxx).
and named won't restart; if I then
# sh /etc/rc.d/named start
Starting named
/named restart
Stopping named.
named already running? (pid=xxx).
and named won't restart; if I then
# sh /etc/rc.d/named start
Starting named.
it works fine.
Is this happening to other people? What could be the reason?
It's nothing critical, only a bit
Hi,
I am getting a little mixed up here.
I am trying to place the proper switches in my rc.conf file so I can use
the script from /etc/rc.d/named to start my named process.
what do I have configured wrong?
# grep named /etc/rc.conf
named_enable=YES
named_program=/usr/local/sbin/named
On Feb 14, 2007, at 11:35 AM, Noah wrote:
[ ... ]
named_flags=-c /var/named/etc/namedb/named.conf
named_chrootdir=/var/named
here is the error from the script:
# /etc/rc.d/named start
Starting named.
named: config filename (-c /var/named/etc/namedb/named.conf)
contains chroot path (-t /var
Hi there,
I have a freeBSD 5.5 server not starting named upon reboot. any clues
how I can troubleshoot this issue?
# grep named /etc/rc.conf
named_enable=YES
named_program=/usr/local/sbin/named
# /usr/local/sbin/named -version
BIND 9.3.2-P2
# uname -a
FreeBSD ns2.ps.juniper.net 5.5-RELEASE
Noah wrote:
Hi there,
I have a freeBSD 5.5 server not starting named upon reboot. any clues
how I can troubleshoot this issue?
# grep named /etc/rc.conf
named_enable=YES
named_program=/usr/local/sbin/named
# /usr/local/sbin/named -version
BIND 9.3.2-P2
# uname -a
FreeBSD ns2
--On Tuesday, January 02, 2007 11:03:49 -0800 Noah [EMAIL PROTECTED]
wrote:
Hi there,
I have a freeBSD 5.5 server not starting named upon reboot. any clues
how I can troubleshoot this issue?
# grep named /etc/rc.conf
named_enable=YES
named_program=/usr/local/sbin/named
# /usr/local/sbin
On 02 Jan Paul Schmehl wrote:
Try adding this to /etc/rc.conf:
named_symlink_enable=YES
Never heard of this option. Never used it too. And named runs on my
FreeBSD-6.1 server like it should. for quite some time now ;-)
I guess the answer is in the logfile. Maybe an error of some sort
You need to add another option in rc.conf for the user you want named to
run as, otherwise it fails to start.
-Derek
At 01:03 PM 1/2/2007, Noah wrote:
Hi there,
I have a freeBSD 5.5 server not starting named upon reboot. any clues how
I can troubleshoot this issue?
# grep named
Hi list,
On Thu, Sep 21, 2006 at 09:31:10PM +0200, Jeremie Le Hen wrote:
Hi list,
please Cc: me in your replies, I am not subscribed to this list.
I have a jail in which named(8) runs. In order to make a possible bug
exploitation still more difficult, I would like to use
Hi list,
please Cc: me in your replies, I am not subscribed to this list.
I have a jail in which named(8) runs. In order to make a possible bug
exploitation still more difficult, I would like to use the named_chrootdir
variable for rc.conf(5).
Unfortunately, rc.d/named tries to mount devfs
to copy data from one of those directies to my
local drive suddenly my server crash again. The only strange thing I
found were these messages in /var/log/messages from the time my server
crashed:
Aug 14 15:52:22 FStaals named[541]: could not listen on UDP socket:
permission denied
Aug 14 15:52
At 03:29 28.06.2006, you wrote:
$ rndc reload
rndc: connection to remote host closed
This may indicate that the remote server is using an older version of
the command protocol, this host is not authorized to connect,
or the key is invalid.
Did you check that named was still listeing
Hello!
I just tried reloading my nameserver after adding a new domain (zonefile).
But then this happened:
$ rndc reload
rndc: connection to remote host closed
This may indicate that the remote server is using an older version of
the command protocol, this host is not authorized to connect,
or
$ rndc reload
rndc: connection to remote host closed
This may indicate that the remote server is using an older version of
the command protocol, this host is not authorized to connect,
or the key is invalid.
Did you check that named was still listeing on port tcp 953? What does
netstat -Sa
Kyrre Nygard wrote:
$ rndc reload
rndc: connection to remote host closed
This may indicate that the remote server is using an older version of
the command protocol, this host is not authorized to connect,
or the key is invalid.
su?
___
I'm cross posting this incase anyone knows the answer.
-- Forwarded message --
Hello List,
I was using darkice to write a [file] to a named pipe. This functioned
on linux but on FreeBSD 6.1 darkice fails to use the fifo as a file. Is
this a darkice issue? Or have I done
; } ;
options {
directory /etc/namedb;
allow-query { homenet; };
listen-on { 192.168.1.1; };
query-source address 192.168.1.1;
};
// Provide reverse mapping for the loopback IP
zone 0.0.127.in-addr.arpa {
type master;
file localhost.rev;
notify no;
};
When I execute named
Andy Greenwood wrote:
I'm trying to set up my first jail, and I've got the below named.conf.
However, even with the query-source line below, it always binds to the
wildcard address! Anyone seen this behavior before and what can I do
to fix it?
Yes, add the following under options:
listen-on
Oh, sorry. You already have that. It should work. It does for me.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
that didn't do it. I meant to include this with my first post, but
forgot to. I just now noticed that it's udp6, not udp4, so I'm
recompiling with --disable-ipv6
[EMAIL PROTECTED] ~]$ sockstat | grep \*:[0-9]
bind named 89293 23 udp6 *:58084 *:*
On 5/19/06, Fremlins
Hey all,
I have caching DNS servers running on two BSD 5.4 machines, and what
happens on both of them is that the processes will just lock up, and while
they may still answer some queries, they don't refresh or update, or
respond to proper signals.
For example:
s2# sh /etc/rc.d/named stop
something seems to have changed with named on 6.1 compared to 6.0
using defaults named cannot create the /var/run/named.pid file.
after changing permissions of /var/run to 777, THEN named runs and
creates a named.pid of: bind:wheel
upon reading I see a new rc.conf variable - named_uid
I added
Jim Pazarena wrote:
something seems to have changed with named on 6.1 compared to 6.0
using defaults named cannot create the /var/run/named.pid file.
after changing permissions of /var/run to 777, THEN named runs and
creates a named.pid of: bind:wheel
upon reading I see a new rc.conf variable
daniel [EMAIL PROTECTED] writes:
Yes, it was dumb, but while I have a backup of all of my domain info and have
restored it all, starting named gives me this error now:
devfs rule: ioctl DEVFSIO_RAPPLY: Inappropriate ioctl for device
devfs rule: ioctl DEVFSIO_RAPPLY: Inappropriate ioctl
Yes, it was dumb, but while I have a backup of all of my domain info and have
restored it all, starting named gives me this error now:
devfs rule: ioctl DEVFSIO_RAPPLY: Inappropriate ioctl for device
devfs rule: ioctl DEVFSIO_RAPPLY: Inappropriate ioctl for device
devfs rule: ioctl
Yes, it was dumb, but while I have a backup of all of my domain info and have
restored it all, starting named gives me this error now:
devfs rule: ioctl DEVFSIO_RAPPLY: Inappropriate ioctl for device
devfs rule: ioctl DEVFSIO_RAPPLY: Inappropriate ioctl for device
devfs rule: ioctl
/named/dev/ that I have untarred there. I tried doing a make
What I can see from my environment (4.11), you only need
/var/named/dev/null, copy it from /dev/null
Olivier
___
I have /var/named/dev/random in addition to /var/named/dev/null
Original Message
Subject:Re: Oops: Deleted /var/named
Date: Wed, 29 Mar 2006 13:58:45 +0200
From: Dimitar Vasilev [EMAIL PROTECTED]
To: Duane Whitty [EMAIL PROTECTED]
References: [EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
ev/null
Original Message
Subject:Re: Oops: Deleted /var/named
Date: Wed, 29 Mar 2006 14:35:52 +0200
From: Dimitar Vasilev [EMAIL PROTECTED]
To: Duane Whitty [EMAIL PROTECTED]
References: [EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED
Yes, it was dumb, but while I have a backup of all of my domain info and have
restored it all, starting named gives me this error now:
devfs rule: ioctl DEVFSIO_RAPPLY: Inappropriate ioctl for device
devfs rule: ioctl DEVFSIO_RAPPLY: Inappropriate ioctl for device
devfs rule: ioctl
--- daniel [EMAIL PROTECTED] wrote:
Yes, it was dumb, but while I have a backup of all of my domain info
and have
restored it all, starting named gives me this error now:
devfs rule: ioctl DEVFSIO_RAPPLY: Inappropriate ioctl for device
devfs rule: ioctl DEVFSIO_RAPPLY: Inappropriate
In the last episode (Mar 28), daniel said:
Yes, it was dumb, but while I have a backup of all of my domain info
and have restored it all, starting named gives me this error now:
devfs rule: ioctl DEVFSIO_RAPPLY: Inappropriate ioctl for device
devfs rule: ioctl DEVFSIO_RAPPLY
On Tuesday 28 March 2006 11:54, Dan Nelson wrote:
In the last episode (Mar 28), daniel said:
Yes, it was dumb, but while I have a backup of all of my domain info
and have restored it all, starting named gives me this error now:
devfs rule: ioctl DEVFSIO_RAPPLY: Inappropriate ioctl
devfs rule: ioctl DEVFSIO_RAPPLY: Inappropriate ioctl for device
devfs rule: ioctl DEVFSIO_RAPPLY: Inappropriate ioctl for device
devfs rule: ioctl DEVFSIO_RAPPLY: Inappropriate ioctl for device
I can only assume that it has something to do with the files
in /var/named/dev/ that I
recent call last):
File build/gen-build.py, line 12, in ?
import os
ImportError: No module named os
rebuilding rpm spec file
rebuilding srclib/apr-util/configure
Looking for apr source in ../apr
Creating include/private/apu_config.h ...
Creating configure ...
Generating 'make' outputs ...
Could
It's time to take on the uneviable task of trying to get named to work.
I'm running FreeBSD 5.4 SECURITY. I've installed the bind9 port.
When I try to start named using the rc.d script (/etc/rc.d/named start), I
get this:
Feb 1 05:30:00 stovebolt named[13084]: stopping command channel
On 2/2/06, Paul Schmehl [EMAIL PROTECTED] wrote:
It's time to take on the uneviable task of trying to get named to work.
I'm running FreeBSD 5.4 SECURITY. I've installed the bind9 port.
When I try to start named using the rc.d script (/etc/rc.d/named start), I
get this:
Feb 1 05:30:00
--On February 2, 2006 7:04:06 AM +0800 Daniel [EMAIL PROTECTED] wrote:
The biggest difference between running as root and the startup script
are the command line arguments given in either case.
Script flags: -u bind -t /var/named
CLI flags: -c /usr/local/etc/named.conf -u root
Yes, I know
If I understand this correctly, if I want to enable a cache name server,
all I have to do is the following:
In /etc/rc.conf enter:
named_enable=YES
Run this command:
# cd /etc/namedb
# sh make-localhost
I enter the address: 127.0.0.1 in the /etc/resolv.conf file ahead of any
other entries.
I
On Sat, 2005-11-12 at 15:52 -0500, Gerard Seibert wrote:
If I understand this correctly, if I want to enable a cache name server,
all I have to do is the following:
In /etc/rc.conf enter:
named_enable=YES
Run this command:
# cd /etc/namedb
# sh make-localhost
I enter the address:
from ports to update my DNS server, another FreeBSD machine
(now running 6.0-RELEASE) with new entries when machines register with the
DHCP server. The problem arises because by default named runs -u bind, however
/var/named/etc/namedb/master is owned by root. I believe this is caused by
/etc/mtree
-RELEASE of some patchlevel. It
uses ISC DHCPD from ports to update my DNS server, another FreeBSD machine
(now running 6.0-RELEASE) with new entries when machines register with the
DHCP server. The problem arises because by default named runs -u bind, however
/var/named/etc/namedb/master
machine runs FreeBSD-5.4-RELEASE of some patchlevel. It
uses ISC DHCPD from ports to update my DNS server, another FreeBSD machine
(now running 6.0-RELEASE) with new entries when machines register with the
DHCP server. The problem arises because by default named runs -u bind, however
/var/named/etc/namedb
because by default named runs -u bind,
however
/var/named/etc/namedb/master is owned by root. I believe this is caused by
/etc/mtree/BIND.chroot.dist, since I'm running bind chrooted (the default
setup). When the DNS machine reboots, I have to manually chown
/var/named/etc/namedb/master
machines register with the
DHCP server. The problem arises because by default named runs -u bind,
however
/var/named/etc/namedb/master is owned by root. I believe this is caused by
/etc/mtree/BIND.chroot.dist, since I'm running bind chrooted (the default
setup). When the DNS machine
Hi all,
Just a quick question... Will the following work for bind9:
acl myacl {
192.168.0.0/16;
};
view internal {
match-clients { myacl; !192.168.1.1; };
};
Basically, I'm trying to include a network into my view, except one address...
Thanks,
Chris.
and i start named, everything
works as expected. /etc/namedb/slave/w.x.y.z.db is populated with the values
on the master server.
However, if i change the values on the master and run
# rndc refresh w.x.y.z
on the slave, nothing is updated. I let it go overnight and still nothing
changed
daniel wrote:
[ ... ]
However, if i change the values on the master and run
# rndc refresh w.x.y.z
on the slave, nothing is updated. I let it go overnight and still nothing
changed. If I restart named on the slave, nothing is updated either. But if
delete /etc/namedb/slave/w.x.y.z.db
On September 1, 2005 11:50 am, Chuck Swiger wrote:
daniel wrote:
However, if i change the values on the master and run
# rndc refresh w.x.y.z
on the slave, nothing is updated. I let it go overnight and still
nothing changed. If I restart named on the slave, nothing is updated
201 - 300 of 514 matches
Mail list logo
