OmniWeb timebomb (not a bug, a suggestion)

[Louis A. Mamakos]

> 
> 	I would like to make a suggestion, however.  When I logged in this  
> morning and found that I couldn't use OmniWeb I immediately tried to ftp the  
> new version.  However, there are a lot of people probably doing the same thing,  
> because I couldn't get on.  Is it possible to let us know a day or two in  
> advance?  Then we wouldn't be falling all over each other to upgrade.  

You might have also had a problem due to the broken DNS configuration:

louie at wa3ymh[439] $ dig ftp.omnigroup.com

; <<>> DiG 2.0 <<>> ftp.omnigroup.com 
;; ->>HEADER<<- opcode: QUERY , status: NOERROR, id: 6
;; flags: qr rd ra ; Ques: 1, Ans: 3, Auth: 9, Addit: 9
;; QUESTIONS: 
;;      ftp.omnigroup.com, type = A, class = IN

;; ANSWERS:
ftp.omnigroup.com.      28577   CNAME   ftp.titan.org.
ftp.titan.org.  28591   CNAME   gaea.titan.org.
gaea.titan.org. 28591   A       198.151.161.97

It's not legal for a CNAME record to point to another name that is
itself a CNAME record.  This apparently causes heartburn to the DNS
resolver/lookupd on my 3.3 system.

louie