|
|
 |  |
Re: CNAME to a CNAME? and DNS Expert crashFrom: Aaron Lynch Date: Tuesday, February 27, 2001
Time: 3:57:24 pmOn 02/27/2001 3:50 PM, The Defendant "Warren Michelsen"
<Warren@MDCCLXXVI.com> Confessed:
> I've been having trouble connecting to SETIatHome.Berkeley.edu and in poking
> around to find out why, I find that
>
> SETIatHome.Berkeley.edu is a CNAME for
> SETIatHome.ssl.Berkeley.edu
> but SETIatHome.ssl.Berkeley.edu is itself a CNAME for
> MilkyWay.ssl.Berkeley.edu
>
> It it "legal" in DNS land to have a CNAME pointing to another CNAME record? In
> the above instance, MilkyWay.ssl.Berkeley.edu does have an A record so I guess
> that SETIatHome.Berkeley.edu resolves OK, eventually. But is it proper?
No, it's specifically against the rules.
>
> Also, using the default memory partition in DNS Expert Pro 1.6, it ran out of
> memory before it was done analyzing the zone. It even listed the out-of-memory
> condition right in the "Results for Berkeley.edu" window. Cool, but when I
> went to quit DNS Expert Pro, it unexpectedly quit with an error 25
> (dsMemFullErr) so I rebooted just to be safe.
>
> You'd think that an application cool enough to even log its low memory
> condition could recover without an unexpected quit.
And make me coffee too dammit!
-- Aaron Lynch
System Administrator
NineWire Digital Solutions
|

Return to Digital Point Solutions' Home Page |