I'm in the process of configuring ISC dhcpd and Bind9 on SLES Linux in our office for internal DNS. I'd like to put everything in one zone, city.domain.tld for example. I can get the dhcpd server to update the zone, but if I add static records to the zone (a new file server with it's ip for example) Bind complains about the journal no longer matching.
Assigning fixed IPs via dhcp to the servers is not a solution because dhcpd doesn't send updates to the DNS for fix IPs.
I could use two separate zones, one with static IPs and one for the dynamic updates, but I'd rather not have to go all the work stations (80ish) and add the second search suffix.
Workstations are a mix of Windows, Linux and MAC. No domains or active directory.
Any suggestions? Is deleting the journal and letting DHCP re-update the dns the only solution? Searching Google didn't turn anything up.
2010.7.14 Update:
Here are the version numbers:
- bind-9.3.2-17.15
- dhcpcd-1.3.22pl4-223.2
- SLES 10 i386
Upgrading to a newer version of Bind/dhcpd is not out of the question if it solves the problems.
-
Are you running a recent version of bind later then 9.3.0?
If so you can use the command
rndc freeze zone.tld
to freeze the zone. Once it is in this state dynamic update requests will be rejected and you can manually edit the zone database. Use the commandrndc unfreeze zone.tld
to return the zone to a point that will allow dynamic updates. You do need to update the serial number if you manually make changes.Phil P : It's `thaw`, not `unfreeze`, but this is right.David : Agreed. Seems the docs and the actual command differ. Bv9.3 ARM says "unfreeze" but rndc's help command says "thaw".From Zoredache
0 comments:
Post a Comment