Mysterious CNAME record Pointing to Network Solutions

[Mark Andrews]

> 	I am trying to figure out why one of our remote campuses
> had the following occur:
> 
> 	They attempt to lookup the CNAME claims.okstate.edu and get
> 
>    claims.okstate.edu. 3600    IN  CNAME   www.networksolutions.com.
>    claims.okstate.edu. 3600    IN  CNAME   www.networksolutions.com.
> 
> 	It seems to resolve properly everywhere else:
> 
> $ host claims.okstate.edu
> 
> claims.okstate.edu is an alias for claims.osu-tulsa.okstate.edu.
> claims.osu-tulsa.okstate.edu has address 192.234.12.10
> 
> The individual who sent the complaint to me is the administrator
> for the DNS at 139.78.239.152. As of today, it correctly
> resolves the CNAME as does another DNS in our remote campus
> system that might have been involved. Basically, I can't
> duplicate the problem.
> 
> 	Are there any indications that Network Solutions is
> doing anything sneaky again similar to the wild card A record
> debacle of 2003 or so?
> 
> 	Thanks for any ideas that would explain this CNAME
> record with the 3600-second TTL.
> 
> Martin McCormick WB5AGZ  Stillwater, OK 
> Systems Engineer
> OSU Information Technology Department Network Operations Group

	I would also point out that if DNSSEC was in use this sort
	of thing is impossible.  This is exactly what DNSSEC was
	designed to prevent.

	Mark
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews at isc.org