Re: Mysterious CNAME record Pointing to Network Solutions

3 msg	Re: rndc stats query
3 msg	DNS rebinding partial workaround
5 msg	Can't resolve www.servergraph.org
7 msg	Can't resolve occ.com.mx
9 msg	Error querying a.gtld.biz.
2 msg	block some domain
8 msg	Debian vs SuSE
12 msg	Confused about what $ORIGIN does in relation to @
18 msg	Best GUI tool for managing BIND 9.x
2 msg	Version compatibility
4 msg	no more recursive clients: quota reached
1 msg	Rene Vasquez/U-Houston/ExxonMobil is out of the...
15 msg	memory leak or other problem
31 msg	Configuring BIND With Multiple Domains
5 msg	Ok for Views to use same Zone information?

Mysterious CNAME record Pointing to Network Sol...
\ Martin McCormick (6 Sep 2007)
. \ Stephane Bortzmeyer (6 Sep 2007)
. \ Martin McCormick (6 Sep 2007)
. \ Mark Andrews (7 Sep 2007)

7 msg	Building bind-9.4.1-P1 on sco
7 msg	Yahoo Mail servers can't find my domain hostname
1 msg	solution to answer to replace 'Non-existent dom...
1 msg	Allowing zone xfer to slave server --TYPO

Subject:	Re: Mysterious CNAME record Pointing to Network Solutions
Group:	Bind-users
From:	Mark Andrews
Date:	7 Sep 2007

> 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