Updating zone update unsuccessful

$TTL 600 ; 10 minutes myserver A 10.2.2.5 ns1 A 10.2.2.5 test A 10.2.2.45 www A 1.32 // externally hosted www server ; ; BIND data file for ; $TTL 10m @ IN SOA ns1. ( 2 ; Serial 604800 ; Refresh 86400 ; Retry 2419200 ; Expire 604800 ) ; Negative Cache TTL ; 2.2.10. Failing that, give Now, the funny thing is, I am 99.999% sure that the permissions were already set correctly (owner/group named, with 660 permissions). has to guess what zone the update applies to when you omit that ("based on the rest of the input" according to the manpage), and I see lots of room for that assumption to be wrong given how many quads deep this zone is. But after testing DDNS and DHCP with anohter Linux machine, the results are the same. Of course in each boot the DHCP server PC2 assigns a different IP to PC1 upon boot.So under RH9, home1 is assigned 192.168.0.129 and under Windows XP, home1 is assigned 192.168.0.128. subnet 10.50.0.0 netmask 255.255.0.0 subnet 10.100.0.0 netmask 255.255.0.0 Sep 3 alfred named[7393]: client 127.0.0.1#7429/key rndc-key: signer "rndc-key" approved Sep 3 alfred named[7393]: client 127.0.0.1#7429/key rndc-key: updating zone 'lan.bat/IN': adding an RR at 'bat' A .100 Sep 3 alfred named[7393]: client 127.0.0.1#7429/key rndc-key: updating zone 'lan.bat/IN': adding an RR at 'bat' TXT "00b1a718622197bea9dacc93e33fb507f8" Sep 3 alfred dhcpd[7367]: DHCPREQUEST for .100 (10.50.0.1) from :d:2e:69 (batmobil) via eth0 Sep 3 alfred dhcpd[7367]: DHCPACK on .100 to :d:2e:69 (batmobil) via eth0 Sep 3 alfred dhcpd[7367]: Added new forward map from bat to .100 Sep 3 alfred named[7393]: client 127.0.0.1#7429/key rndc-key: updating zone '10. ARPA/IN': update failed: not authoritative for update zone (NOTAUTH) Sep 3 alfred dhcpd[7367]: DDNS: bad zone information, repudiating zone 50.10. The servers are running on a Fedora 7 PC and the clients are a mixture of desktops and laptops running Windows XP Home SP2. However, I have one problem and I hope I can explain it in this scenario.

However, named evaluates the update’s prerequisites (checking that a record of the specified name does not exist) before checking whether the zone would accept the update; it then might log that the prerequisites are not satisfied, rather than that the zone does not accept updates.

ddns-updates on; ddns-update-style interim; include "/etc/bind/rndc.key"; authoritative; zone bat. So my question is: How do I configure the dhcp/bind to get reverse mappings?

Even though I believe to have identified the problem (please tell me if I am wrong), I cannot get it fixed.

You can either configure all clients in “example.com” to not send updates (much work), or simply remove the logging category “update” from your nameserver logging configuration (then your log files will not be cluttered by these messages).

bathroom-blowjob

Microsoft Knowledgebase Article 246804 describes the step to disable dynamic updates on a Windows 2000/2003 client. I'm baffled for the exact reason it's working, but I'll take it! EDIT: It looks as if my reverse zone file got updated somehow (I'm assuming via nsupdate). Note the difference from my originally posted 2.2.10.zone in my original question.

isb-technology.ru

54 Comments

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>