Craig, I'm a bit confused, and it is probably because I don't totally understand how the dynamic dns updates work.
192.168.100.100 is the windows machine that checked out the IP address from the dhcp server(srfs1-192.168.100.20). Should update requests be coming from a dhcp client? How is the windows 2k dhcp client requesting a dns update? Does this mean that I need to put the entire subnet range that I allow for dhcp checkout(192.168.100.100-255) in the acl? I thought that I only had to list the dhcp server(192.168.100.20) in the allow-update field? Thanks for the help. ---Dean. Craig Sanders wrote: > On Thu, Sep 06, 2001 at 11:02:00PM -0700, Dean A. Roman wrote: > > Sep 6 15:07:31 srfs1 named[1944]: denied update from > > [192.168.100.100].1097 for "mydomain.com" > > Sep 6 15:07:31 srfs1 named[1944]: denied update from > > [192.168.100.100].1103 for "100.168.192.in-addr.arpa" > > update requests are coming from 192.168.100.100 > > > ====================================== > > /ETC/BIND/NAMED.CONF > > ====================================== > > acl dyn-update { > > 127.0.0.1; > > 192.168.100.20; > > }; > > 192.168.100.100 isn't listed in that acl. > > craig > > -- > craig sanders <[EMAIL PROTECTED]> > > Fabricati Diem, PVNC. > -- motto of the Ankh-Morpork City Watch
begin:vcard n:Roman;Dean tel;work:707-527-8949 x-mozilla-html:FALSE org:Roman Systems adr:;;2116 Crosspoint Ave.;Santa Rosa;California;95403;USA version:2.1 email;internet:[EMAIL PROTECTED] title:Owner x-mozilla-cpt:;-31008 fn:Dean Roman end:vcard