Re: After BIND update owner changed and restart failed

[Kai Schaetzl <maillists@xxxxxxxxxxxxx>]

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 'bolera.lan/IN' denied

is just normal logging that I can't avoid?

> You would have to 'allow-update' within a specific zone definition to
> change default behavior.

good.

> 
> FWIW - I think that DHCP/BIND and having clients update DNS makes a lot
> of sense for an office intranet but hey, that's just me.

not in my case. Most clients do get fixed addresses and hostnames applied 
from dhcp, anyway.


Kai

-- 
Kai Schätzl, Berlin, Germany
Get your web at Conactive Internet Services: http://www.conactive.com



_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos