dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
18537
share rss forum feed

DirtDigler

join:2008-06-23
Falls Church, VA

[VA] What are my Cox DNS Servers?

The dslreports cox dns list is not current and I can't ping what it says is my dns server: 68.1.16.101

I'm currently using:
68.105.28.11
68.105.29.11

According to google, those are West coast servers. I'm in Northern VA.

Anyone have the correct IP's?



danielk

join:2009-02-01
Greenwood, MO

I would recommend OpenDNS's DNS servers (208.67.222.222 and 208.67.220.220) since switching it's been almost night and day.

www.opendns.com



jsimmons
Premium,MVM
join:2000-04-24
Falls Church, VA

2 edits
reply to DirtDigler

I second that. I use OpenDNS: 208.67.222.222 as my primary, but keep 68.105.28.12 and 68.105.29.12 as secondary servers.
--

BTW, 68.105.28.11 returns a ping time of 8-11 ms. So it can't possibly be on the west coast. Its really close with those times. 68.105.28.12 returns ping of 45 ms. So it is a bit further away, as the bits fly.

28.12 responds to ping in 8 ms for me, and 29.12 responds in 45 ms.

"Everything should be made as simple as possible, but not one bit simpler."
- Albert Einstein


ajwees41
Premium
join:2002-05-10
Omaha, NE
reply to DirtDigler

they are different for each area. I use DHCP and get the auto assigned by cox and never have had a problem.


DirtDigler

join:2008-06-23
Falls Church, VA
reply to DirtDigler

Thanks, I'll switch to OpenDNS and give them a try. The tracert's on Cox's servers get way too high. first hop will be like 40, second jumps to 300's, third is like 60, fourth ranges around the 200's. It's consistent like that too.


Rob_
Premium
join:2008-07-16
Mary Esther, FL
kudos:1

or for a non redirect free zone, try 4.2.2.2 and 4.2.2.3


Net_Neutral

join:2009-01-29

I use Cox's DNS with out any trouble... ever... and I trust them more than OpenDNS. If you want to "opt-out" of their enhanced error page (getting re-directed) use these dns servers: 68.105.28.13, 68.105.29.13

»support.cox.com/sdccommon/asp/co···rect.asp



MineCoast
Premium
join:2004-10-06
127.0.0.1
reply to DirtDigler

As of late, I have been having a lot of issues with OpenDNS. I wasn't able to hit a bunch of websites (including Google) on any of my PC's that were setup to use OpenDNS. As soon as I changed those PC's back to Auto (Cox) I was able to hit all those sites without any issues. I've also noticed a lot of stalls using OpenDNS.

Usually I have issues with Cox's DNS Servers, but as of late, the opposite has been true.



tubbynet
reminds me of the danse russe
Premium,MVM
join:2008-01-16
Chandler, AZ
kudos:1
reply to DirtDigler

if you have a spare pc you can always load up a copy of your favorite linux distro, install bind and then webmin. centos 5.x is really clean for that. minimal install with gnome and then yum bind and webmin. very painless configuration that allows for local dns resolution, dns caching, and root server lookup (or forwarding to your favorite external dns service).

q.
--
those who forget the past are doomed to repeat it...


daveinpoway
Premium
join:2006-07-03
Poway, CA
kudos:2
reply to MineCoast

Interesting- I haven't seen any OpenDNS problems.



NoVA_CoxUser
Stand back from the cage -- The RF bites
Premium
join:2004-07-06
Alexandria, VA

3 edits
reply to DirtDigler

Cox's DNS "local" DNS servers generally follow the naming convention ns1(2).aa.cox.net; with the "aa" being the local network's 2-letter designation.

See: FAQ Listing of Cox 2-Letter Local Codes

Cox NoVA's servers are therefore:
ns1.dc.cox.net - 68.100.16.30
ns2.dc.cox.net - 68.100.16.25

(Not sure where those two servers you listed are physically located -- although a tracert to that 2nd one goes thru Dallas)

That said, I too use OpenDNS; w/o any problems to-date.


Net_Neutral

join:2009-01-29

said by NoVA_CoxUser:

(Not sure where those two servers you listed are physically located -- although a tracert to that 2nd one goes thru Dallas)
I'm not sure where your getting Dallas TX from:

traceroute to ns1.dc.cox.net (68.100.16.30), 30 hops max, 40 byte packets
1 172.16.x.x (172.16.x.x) 0.499 ms 0.465 ms 0.322 ms
2 10.1.x.x (10.1.x.x) 22.855 ms 22.814 ms 22.584 ms
3 provsysc01-gex0101000.ri.ri.cox.net (68.9.8.49) 22.452 ms 22.401 ms 22.144 ms
4 ip68-9-7-128.ri.ri.cox.net (68.9.7.128) 21.444 ms 21.336 ms 28.439 ms
5 provdsrj01-ge500.0.rd.ri.cox.net (68.9.14.113) 28.387 ms 28.256 ms 27.687 ms
6 * * *
7 nyrkbbrj01-so000.r2.ny.cox.net (68.1.1.173) 22.343 ms 54.978 ms 64.656 ms
8 nyrkbbrj02-ae0.0.r2.ny.cox.net (68.1.0.253) 64.520 ms 64.244 ms 63.881 ms
9 68.1.2.240 (68.1.2.240) 69.319 ms 69.302 ms 69.032 ms
10 ashbbbrj02-ae0.0.r2.as.cox.net (68.1.0.221) 68.726 ms 68.188 ms 68.445 ms
11 * * *
12 mrfddsrj02-ge710.rd.dc.cox.net (68.1.1.7) 23.182 ms * mrfddsrj02-so010.rd.dc.cox.net (68.1.1.13) 51.704 ms
13 ns1.dc.cox.net (68.100.16.30) 59.014 ms 58.483 ms 58.410 ms
--
My crime is that of curiosity. My crime is that of judging people by what they say and think, not what they look like. My crime is that of outsmarting you, something that you will never forgive me for.


NoVA_CoxUser
Stand back from the cage -- The RF bites
Premium
join:2004-07-06
Alexandria, VA

4 edits

said by Net_Neutral:

... I'm not sure where your getting Dallas TX from ...
I said the "2nd one" referring to the two DNS servers listed by the OP (specifically the 29.11 DNS server)

As you can see below, when hitting that server from Northern VA -- hop 8 is in Atlanta while hop 10 is in Dallas.

C:\tracert 68.105.29.11
 
Tracing route to cdns6.cox.net [68.105.29.11]
over a maximum of 30 hops:
 
  1    32 ms    39 ms     7 ms  192.168.x.x
  2    11 ms     7 ms     8 ms  10.7.xxx.x
  3    57 ms    10 ms    20 ms  ip72-219-223-101.dc.dc.cox.net [72.219.223.101]
 
  4    32 ms    17 ms    46 ms  mrfddsrj01-ge110.rd.dc.cox.net [68.100.0.161]
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8    91 ms    14 ms    77 ms  lkhndsrc02-fe0432.rd.at.cox.net [68.1.0.17]
  9     *        *        *     Request timed out.
 10    78 ms    49 ms    63 ms  dalsbbrj02-ae3.0.r2.dl.cox.net [68.1.0.186]
 11    66 ms    47 ms    71 ms  cdns6.cox.net [68.105.29.11]
 
Trace complete.