On Mon, 2009-01-26 at 11:06 -0500, Scott Lawrence wrote: > On Mon, 2009-01-26 at 10:26 +0000, Paul Mcdaid wrote: [...] > > So, we have two choices: > > > > 1. Only allow an IP address to be entered for NTP Server (as we do for > > DNS server, which we currently don't check for). > > 2. If an FQDN is entered, resolve this to an ip address, and store this > > in the database. Then we can use this ntpipaddress to populate > > dhcpd.conf and audiocodes ini files. > > > > > > I think option 2 is the better, although it comes with the problem that > > if we can't (for any reason) resolve the fqdn, then the ntp settings > > won't be configured for DHCP or audiocodes. > > I agree that of those 2 is the better choice, but there's a third > choice: > > 3) Always configure all phones and gateways to use the sipXecs system(s) > as their NTP server using the IP address of the server(s). Note that > this works even when NTP connectivity outside the LAN is constrained in > some way.
I like option 3. Sorry I didn't think of this in our discussion last week Paul :) If we were to go with option 2 instead though, when would be the appropriate time to resolve the fqdn to an IP address? My gut feeling is that we do it every time we need it, such as every time we send profiles to the phones. This shouldn't be all that often, and does help to maintain some liveness. Kevin _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
