Cox seems to be up to some sort of shenanigans regarding DNS lookups, I co-run a small IRC network (less than 250 users at any one time), and I'm recieving complaints that Cox subscribers are being redirected when they try to connect to the network (Aniverse) to a Cox-owned IRC server with the purpose of removing bots:
23:37:22 joins: Xeno (Mibbit@ani-76k.sue.cox.net) [8 users]
23:38:00 Seem to be having a bit of a strange issue connecting to the network with my client.
23:38:31 Anytime I try to connect I'm being forced into a channel named #martian_ with a user named marvin who is the op, this same person is appearing as an op in every other channel I happen to go into
23:38:43 The regular MOTD is also gone
23:38:54 Anyone have an idea on what is going on there?
I remember this happening a long time ago back when I used to use Cox's DNS servers, I do not recall if it was ever resolved because I switched away from their DNS servers and started using OpenDNS (now use google). Basically, this post describes what is happening to the user:
https://lists.sans.org/pipermail/list/2007-July/026488.html
Also, this is what users *should* be getting:
nslookup irc.aniverse.com
Server: 8.8.8.8
Address: 8.8.8.8#53
Non-authoritative answer:
Name: irc.aniverse.com
Address: 66.207.167.12
Name: irc.aniverse.com
Address: 65.23.153.236
this is what they *are* getting:
nslookup irc.aniverse.com 68.6.16.30
Server: ns1.sd.cox.net
Address: 68.6.16.30
[1:04:52 AM] Daniel: Name: irc.aniverse.com
Address: 70.168.70.5
Unbelievable.
--
A battle has been fought, and is now over.
Place your sword upon the ground, and rest in the temporal peace.
After dozing in the warmth of a dream, a new day will begin.
The days keep passing by..
And we still chase the same star we once saw.
↧