Differences between version 7 and predecessor to the previous major change of DHCPNotes.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 7 | Last edited on Friday, February 6, 2004 9:49:06 am | by PerryLorier | Revert |
| Older page: | version 6 | Last edited on Sunday, September 14, 2003 7:21:48 pm | by MarianFlor | Revert |
@@ -115,4 +115,15 @@
Restart both dhcpd3-server and named.
You should see log entries in syslog talking about 'if rrset for ... does not exist then create ...'
And doing nslookups on $MACHINENAME.yourdomain should now work. Note that this machinename is the Netbios name in case of windows machines. The reverse zone should also be updated, so that 'nslookup 10.0.0.151' for example, will return '$MACHINENAME.mydomain.something' correctly, instead of '10.0.0.151.dhcp.mydomain.something' which is what it was set to previously :)
+
+{Not really PerryLorier}
+Note that after you've set up DDNS, you mustn't edit the dynamically updated zones manually. Instead, use the 'nsupdate' command to add and delete records. The man page for 'nsupdate' says this:
+
+
+ Zones that are under dynamic control via nsupdate or a DHCP server
+ should not be edited by hand. Manual edits could conflict with dynamic
+ updates and cause data to be lost.
+
+
+Unfortunately, 'nsupdate' is about as much fun to use as 'nslookup'. More on 'nsupdate' once I've figured out how to use it, and what to do with those pesky .jnl (journal) files getting out of synch with the zone.
