> On 8/9/06, Robert Mortimer <[EMAIL PROTECTED]> wrote: > > Pfsense does not seem to add the RFC 2136 dynamic updates > configuration to > > the ISC DHCP config file. As a result I am assuming that > pfsense is using > > the another tool to provide this functionality (the same one > that is used > > for dynamic dns providers). Can someone tell me what it is and where the > > config file is? > > Look in /var/etc/ .. I have no idea what the configuration name is > as I don't use this feature. If it is broken we need to pull the > feature but I have heard from others that it works as it should. > I have seen reports that it works for dynamic dns providers on the internet (using a user name password combination). RFC 2136 allows you to configure DHCP to update your own internal bind/DNS using crypto keys. This is built into ISC DHCP. I have not found a confirmed working statement for RFC 2136 updates
I can see my keys in /var/etc/ and a config file called nsupdate nsupdate is part of bind and can be used (via hooks in DHCP to update DNS) but is no longer needed as ISC DHCP can now do this as native functionality. /var/named is empty and I can't run nsupdate at the console. I am prepared to accept that it may be a config problem my end but I do know the following to be true my old ISC dhcpd used to be able to update named using native functionality pfsense is not using dhcpd's native functionality to provide RFC 2136 updates I can't find what is being used for non RFC 2136 dynamic updates Regards Rob --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
