At 5:46 PM +0200 2000/7/13, Daniel Karrenberg wrote:
if you detect probems it is best to alert the people concerned rather than broadcasting as widely and indiscriminately as you have done. DNS SOA RRs provide excellent reference points here.
Unfortunately, it's been my experience that these labels typically age and are not kept up-to-date in many places. However, perhaps this is my memory of the multitude of problems I had when I was at AOL and posting daily "lamers" reports to comp.protocols.tcp-ip.domains, and mailing off a copy of the notice to the address claimed in the SOA records. Maybe this experience with the information in the SOA records is less applicable to the higher-level domains, although I can say that in the case of the .be ccTLD, this would not have done anything more than what we had already done in the past.
There are no problems we can detect with 193.in-addr.arpa name service at this point. We will follow up to a smaller audience.
I'm still very concerned about the number of SERVFAIL errors that I previously saw which have since been mysteriously fixed, and I am very, very concerned about the safety of any of the zones served by any of these machines that are both authoritative and caching/recursive. -- These are my opinions -- not to be taken as official Skynet policy ====================================================================== Brad Knowles, <blk@skynet.be> || Belgacom Skynet SA/NV Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124 Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels http://www.skynet.be || Belgium