Harlan, No; I never said that or you misunderstood me on another matter. The ntpq implementer Dennis Fergusson had his reasons for using DNS on refclock addresses, but I never asked him about why and have had no problem with that on any server over the life of the program. It certainly could be a problem should the local DNS be very slow and I have no problem should somebody take the trouble to remove the feature. There is a macro somewhere that recognizes whether the address is a refclock.
Dave Harlan Stenn wrote: >>>>In article <[EMAIL PROTECTED]>, "Richard B. Gilbert" <[EMAIL PROTECTED]> >>>>writes: > > > Richard> The bug is that ntpq should not be interpreting the refid at all! > Richard> It's a text string, not an IP address and should not be treated as > Richard> one. Yes, sometimes the refid IS an IP address but it still should > Richard> be treated as a simple text string! > > How can the code tell the difference between a refid that is a string and > one that is an IP address? > > I want to stop doing this resolution altogether, but the last time I asked > Dave about this he said he wanted to keep the lookup in place, even though > it is only useful for IPv4. > > H _______________________________________________ questions mailing list [email protected] https://lists.ntp.isc.org/mailman/listinfo/questions
