Scott Mazur wrote on Wed, 14 Jan 2009 13:15:52 -0600:
> "the server can be configured either to honor the client's intentions or
> ignore them. This is done with the statement allow client-updates; or the
> statement ignore client-updates;"
>
> This refers to the client updating its own A record.
On Wed, 14 Jan 2009 17:31:26 +0100, Kai Schaetzl wrote
> Scott Mazur wrote on Tue, 13 Jan 2009 08:08:22 -0600:
>
> > AFAIK the DHCP client has no authority to register dynamic dns regardless of
> > how the client machines are configured. It's the DHCP server that decides
> > to
> > update BIND a
Scott Mazur wrote on Tue, 13 Jan 2009 08:08:22 -0600:
> AFAIK the DHCP client has no authority to register dynamic dns regardless of
> how the client machines are configured. It's the DHCP server that decides to
> update BIND and this can be turned on or off. My guess is your DHCP server is
> co
On Mon, 12 Jan 2009 23:31:19 +0100, Kai Schaetzl wrote
> Craig White wrote on Mon, 12 Jan 2009 07:45:22 -0700:
>
> > by default, BIND will ignore attempts by clients to register dynamic dns
> > after getting an ip address from dhcp - that is what is being logged.
>
> so, the
> Jan 11 16:38:00 ch
Craig White wrote on Mon, 12 Jan 2009 07:45:22 -0700:
> by default, BIND will ignore attempts by clients to register dynamic dns
> after getting an ip address from dhcp - that is what is being logged.
so, the
Jan 11 16:38:00 chacha named[11307]: client 192.168.1.228#1994: view
internal:
update
On Mon, 2009-01-12 at 09:35 -0700, Craig White wrote:
> On Mon, 2009-01-12 at 10:05 -0600, Les Mikesell wrote:
> > Craig White wrote:
> > >
> > > by default, BIND will ignore attempts by clients to register dynamic dns
> > > after getting an ip address from dhcp - that is what is being logged.
> >
On Mon, 2009-01-12 at 10:05 -0600, Les Mikesell wrote:
> Craig White wrote:
> >
> > by default, BIND will ignore attempts by clients to register dynamic dns
> > after getting an ip address from dhcp - that is what is being logged.
> >
> > You would have to 'allow-update' within a specific zone def
Craig White wrote:
>
> by default, BIND will ignore attempts by clients to register dynamic dns
> after getting an ip address from dhcp - that is what is being logged.
>
> You would have to 'allow-update' within a specific zone definition to
> change default behavior.
>
> FWIW - I think that DHCP
Mogens Kjaer wrote:
> Ralph Angenendt wrote:
> ...
> > Which really is strange, as only rndc.key gets "chowned" by the scripts
> > in the bind package.
>
> Maybe it's because I have bind-chroot installed?
>
> The script calls:
>
> /usr/sbin/bind-chroot-admin --enable > /dev/null 2>&1;
>
> as pa
On Mon, 2009-01-12 at 15:16 +0100, Mogens Kjaer wrote:
> Ralph Angenendt wrote:
> ...
> > Which really is strange, as only rndc.key gets "chowned" by the scripts
> > in the bind package.
>
> Maybe it's because I have bind-chroot installed?
>
> The script calls:
>
> /usr/sbin/bind-chroot-admin --
On Mon, 2009-01-12 at 14:19 +0100, Kai Schaetzl wrote:
> Ralph Angenendt wrote on Sun, 11 Jan 2009 18:59:37 +0100:
>
> > You have a windows machine on the network and it gets its address by dhcp?
>
> Yeah, I knew that ;-)
>
> > If so it now tries to tell the name server that it has a new fancy s
Ralph Angenendt wrote:
...
> Which really is strange, as only rndc.key gets "chowned" by the scripts
> in the bind package.
Maybe it's because I have bind-chroot installed?
The script calls:
/usr/sbin/bind-chroot-admin --enable > /dev/null 2>&1;
as part of postinstall, and /usr/sbin/bind-chroot
Mogens Kjaer wrote:
> Robert Moskowitz wrote:
> ...
> > Oh, I remember this from the last update... So off to
> > /var/named/chroot/etc and do a 'chown named:named *' then named started.
>
> I see the same problem every time bind is updated.
>
> My /var/named/chroot/var/named files are writable
Robert Moskowitz wrote:
...
> Oh, I remember this from the last update... So off to
> /var/named/chroot/etc and do a 'chown named:named *' then named started.
I see the same problem every time bind is updated.
My /var/named/chroot/var/named files are writable by named because
I have a DDNS setu
Ralph Angenendt wrote on Sun, 11 Jan 2009 18:59:37 +0100:
> You have a windows machine on the network and it gets its address by dhcp?
Yeah, I knew that ;-)
> If so it now tries to tell the name server that it has a new fancy shiny
> address!
I thought I had configured the client not to do this
On Saturday 10 January 2009 9:37:43 pm Robert Moskowitz wrote:
> I just applied the BIND updates.
>
> Then I fixed the one file that had a second include of named.ca
> (remembered that from last time) and did a 'service named restart', and
> it failed. In messages I found:
>
> Jan 10 21:31:17 z9m9
Kai Schaetzl wrote:
> I didn't notice that before but I see that there are a lot of errors already
> before the update:
>
> Jan 11 16:38:00 chacha named[11307]: client 192.168.1.228#1994: view
> internal:
> update 'bolera.lan/IN' denied
You have a windows machine on the network and it gets its
Kai Schaetzl wrote:
> I had named.conf with root.root (and it was working). That
> got changed by the
> update to root.named. Which apparently is the correct
> ownership according to
> you and it still works. When I installed bind just a few
> weeks ago I had to
> create all the files manuall
Ralph Angenendt wrote on Sun, 11 Jan 2009 11:10:54 +0100:
> The files under there belong to root:named and are 644 (except rndc.conf
> which is 640). No file there belongs to named:named. named.acl isn't shipped
> with bind.
I had named.conf with root.root (and it was working). That got changed
Robert Moskowitz wrote:
> I just applied the BIND updates.
>
> Then I fixed the one file that had a second include of named.ca
> (remembered that from last time) and did a 'service named restart', and
> it failed.
Never heard about someone having to apply that fix - do you have a bug entry
fr
I just applied the BIND updates.
Then I fixed the one file that had a second include of named.ca
(remembered that from last time) and did a 'service named restart', and
it failed. In messages I found:
Jan 10 21:31:17 z9m9z named[31001]: loading configuration from
'/etc/named.conf'
Jan 10 21:3
21 matches
Mail list logo
