Craig, I did find this error in /var/log/messages and looked it up, the mails I've read seem to indicate that the name server can't find this domain? However, everything(nslookup) seems to work fine. The messages log file is listed below if you feel like looking at it.
===>>> "Sep 8 04:00:07 srfs1 named[8222]: sysquery: findns error (NXDOMAIN) on dns1.mydomain.com?" Do you think this message is related to dhcp-dns not being able to update the domain? The DNS server setup scenario I'm running is: ========================================= 1) I have an internal(on a private IP address subnet only connected to internet via NAT/MASQ) DNS name server acting as a master for mydomain.com. 2) I have an external(on the internet)DNS server acting as a master for mydomain.com. 3) The internal DNS server serves all the internal clients, and has forwarding setup so that it can forward requests to an outside name server. 4) The external DNS server serves the internet clients, and does not do any forwarding, and does not know about the internal machine. 5) The way I understand it, is that the internal DNS name server should never query the up level .com server for mydomain.com because it is the master for that domain. Does the info. below help? Is there any specific file or log that could help to come to a conclusion? Is there any where else besides /var/syslog or /var/messages that I can find logs for dhcp-dns? Can you point me to anyone/anyplace else that might be able to help? Can you think of anything else that might help me out? Thanks for the help... ---Dean. srfs1:/var/log# tail -f daemon.log Sep 8 01:00:01 srfs1 named[2398]: NSTATS 999936001 999817201 A=1936 Sep 8 01:00:01 srfs1 named[2398]: XSTATS 999936001 999817201 RR=416 RNXD=11 RFwdR=279 RDupR=1 RFail=3 RFErr=0 RErr=0 RAXFR=0 RLame=0 ROpts=0 SSysQ=121 SAns=1916 SFwdQ=297 SDupQ=121 SErr=0 RQ=1936 RIQ=0 RFwdQ=297 RDupQ=17 RTCP=0 SFwdR=279 SFail=0 SFErr=0 SNaAns=1693 SNXD=26 RUQ=0 RURQ=0 RUXFR=0 RUUpd=0 Sep 8 02:00:01 srfs1 named[2398]: Cleaned cache of 46 RRsets Sep 8 02:00:01 srfs1 named[2398]: USAGE 999939601 999817201 CPU=0.49u/0.1s CHILDCPU=0u/0s Sep 8 02:00:01 srfs1 named[2398]: NSTATS 999939601 999817201 A=1936 Sep 8 02:00:01 srfs1 named[2398]: XSTATS 999939601 999817201 RR=416 RNXD=11 RFwdR=279 RDupR=1 RFail=3 RFErr=0 RErr=0 RAXFR=0 RLame=0 ROpts=0 SSysQ=121 SAns=1916 SFwdQ=297 SDupQ=121 SErr=0 RQ=1936 RIQ=0 RFwdQ=297 RDupQ=17 RTCP=0 SFwdR=279 SFail=0 SFErr=0 SNaAns=1693 SNXD=26 RUQ=0 RURQ=0 RUXFR=0 RUUpd=0 Sep 8 03:00:01 srfs1 named[2398]: Cleaned cache of 7 RRsets Sep 8 03:00:01 srfs1 named[2398]: USAGE 999943201 999817201 CPU=0.49u/0.1s CHILDCPU=0u/0s Sep 8 03:00:01 srfs1 named[2398]: NSTATS 999943201 999817201 A=1936 Sep 8 03:00:01 srfs1 named[2398]: XSTATS 999943201 999817201 RR=416 RNXD=11 RFwdR=279 RDupR=1 RFail=3 RFErr=0 RErr=0 RAXFR=0 RLame=0 ROpts=0 SSysQ=121 SAns=1916 SFwdQ=297 SDupQ=121 SErr=0 RQ=1936 RIQ=0 RFwdQ=297 RDupQ=17 RTCP=0 SFwdR=279 SFail=0 SFErr=0 SNaAns=1693 SNXD=26 RUQ=0 RURQ=0 RUXFR=0 RUUpd=0 Sep 8 03:50:17 srfs1 dhcpd-2.2.x: DHCPDISCOVER from 00:00:86:45:48:0c via eth0 Sep 8 03:50:18 srfs1 dhcpd-2.2.x: DHCPOFFER on 192.168.100.100 to 00:00:86:45:48:0c via eth0 Sep 8 03:50:18 srfs1 dhcpd-2.2.x: DHCPREQUEST for 192.168.100.100 from 00:00:86:45:48:0c via eth0 Sep 8 03:50:18 srfs1 dhcpd-2.2.x: DHCPACK on 192.168.100.100 to 00:00:86:45:48:0c via eth0 Sep 8 03:51:20 srfs1 named[2398]: denied update from [192.168.100.100].1030 for "mydomain.com" Sep 8 03:51:20 srfs1 named[2398]: denied update from [192.168.100.100].1036 for "100.168.192.in-addr.arpa" Sep 8 03:56:20 srfs1 named[2398]: denied update from [192.168.100.100].1043 for "mydomain.com" Sep 8 03:56:20 srfs1 named[2398]: denied update from [192.168.100.100].1049 for "100.168.192.in-addr.arpa" Sep 8 04:00:01 srfs1 named[2398]: named shutting down Sep 8 04:00:01 srfs1 named[2398]: USAGE 999946801 999817201 CPU=0.49u/0.1s CHILDCPU=0u/0s Sep 8 04:00:01 srfs1 named[2398]: NSTATS 999946801 999817201 A=1945 NS=4 SOA=8 Sep 8 04:00:01 srfs1 named[2398]: XSTATS 999946801 999817201 RR=416 RNXD=11 RFwdR=279 RDupR=1 RFail=3 RFErr=0 RErr=0 RAXFR=0 RLame=0 ROpts=0 SSysQ=121 SAns=1941 SFwdQ=297 SDupQ=121 SErr=0 RQ=1969 RIQ=0 RFwdQ=297 RDupQ=17 RTCP=12 SFwdR=279 SFail=0 SFErr=0 SNaAns=1697 SNXD=32 RUQ=0 RURQ=0 RUXFR=0 RUUpd=4 Sep 8 04:00:01 srfs1 named[8221]: starting (/etc/bind/named.conf). named 8.2.3-REL-NOESW Sat Jan 27 01:46:37 MST 2001 [EMAIL PROTECTED]:/home/bdale/debi an/bind-8.2.3/src/bin/named Sep 8 04:00:01 srfs1 named[8221]: hint zone "" (IN) loaded (serial 0) Sep 8 04:00:01 srfs1 named[8221]: master zone "localhost" (IN) loaded (serial 1) Sep 8 04:00:01 srfs1 named[8221]: master zone "127.in-addr.arpa" (IN) loaded (serial 1) Sep 8 04:00:01 srfs1 named[8221]: master zone "0.in-addr.arpa" (IN) loaded (serial 1) Sep 8 04:00:01 srfs1 named[8221]: master zone "255.in-addr.arpa" (IN) loaded (serial 1) Sep 8 04:00:01 srfs1 named[8221]: dynamic zone file '/etc/bind/db.mydomain' is writable Sep 8 04:00:01 srfs1 named[8221]: master zone "mydomain.com" (IN) loaded (serial 2001090603) Sep 8 04:00:01 srfs1 named[8221]: dynamic zone file '/etc/bind/db.192.168.100' is writable Sep 8 04:00:01 srfs1 named[8221]: master zone "100.168.192.in-addr.arpa" (IN) loaded (serial 2001090603) Sep 8 04:00:01 srfs1 named[8221]: dynamic zone file '/etc/bind/db.192.168.110' is writable Sep 8 04:00:01 srfs1 named[8221]: master zone "110.168.192.in-addr.arpa" (IN) loaded (serial 2001090404) Sep 8 04:00:01 srfs1 named[8221]: dynamic zone file '/etc/bind/db.209.204.148.62' is writable Sep 8 04:00:01 srfs1 named[8221]: master zone "62.148.204.209.in-addr.arpa" (IN) loaded (serial 2001090403) Sep 8 04:00:01 srfs1 named[8221]: listening on [127.0.0.1].53 (lo) Sep 8 04:00:01 srfs1 named[8221]: listening on [192.168.100.20].53 (eth0) Sep 8 04:00:01 srfs1 named[8221]: Forwarding source address is [0.0.0.0].1228 Sep 8 04:00:01 srfs1 named[8222]: Ready to answer queries. Sep 8 04:00:07 srfs1 named[8222]: sysquery: findns error (NXDOMAIN) on dns1.mydomain.com? Sep 8 04:00:17 srfs1 last message repeated 3 times Sep 8 04:06:20 srfs1 named[8222]: denied update from [192.168.100.100].1055 for "mydomain.com" Sep 8 04:06:20 srfs1 named[8222]: denied update from [192.168.100.100].1061 for "100.168.192.in-addr.arpa" Craig Sanders wrote: > On Fri, Sep 07, 2001 at 08:47:10PM -0700, Dean A. Roman wrote: > > Will turning this "feature??" off in Win2K allow the dhcp-dns scripts > > in linux to update bind? > > no, it's unrelated. it'll just stop the w2k clients from attempting to > update the dns server. > > > How do I fix the problem of dhcp-dns not updating bind? > > no idea. the log extracts you sent didn't show any problem...they only > showed your w2k client being denied access. > > > Is it related to the win2K "feature??" > > completely unrelated. > > 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