?

Log in

No account? Create an account
Computer

DNS

Posted on 2013.05.13 at 00:00
Current Location: 67114

Every six months or so, COX DNS stops resolving hostnames. And I can't just change the DNS on the router to update every ipod, iphone, computer, server, virtual machine, game console, coffee maker and embeded video device. So on top of not understanding why DNS stops responding in the first place, I also don't understand why I can't just update the DNS in the router. All my DHCP devices are set to get their address and DNS from it.

No, I have to update each device manually. I use OpenDNS when I do. I have NS1 and NS2 IPs memorized. So two dozen or so device changes. Then, around six months time, OpenDNS stops resolving hostnames. I have to touch all devices again and point them at the router. This has happened, on average, every 6-months since I moved here in 2010.

I used to call COX. Funny thing, COX employs no network engineers. They would send some cable guys out and tell me, "Yep, dB levels are strong."
"That's not the problem I'm having," I would say, and explain domain name resolution. None of that mattered to them, because the dB levels were strong. Once they suggested I replace the router. I did. No change.

Its not the fact that it happens every six months, its that I don't know why, and that no one can explain it to me.

Comments:


Jobu
jobu121 at 2013-05-13 14:57 (UTC) (Link)
I know that Time Warner fails over to Chicago from TX - I believe it is for maintenance, since like you they say that is not true. Yet my speed takes a hit.

Try updating the router with this solution: dd-wrt DD-WRT is a Linux based alternative OpenSource firmware suitable for a great variety of WLAN routers and embedded systems.

Also they have a cool privacy tool.

I use it on mine,works solid.




Edited at 2013-05-13 03:02 pm (UTC)
ehowton
ehowton at 2013-05-14 22:00 (UTC) (Link)
While I like the idea behind that, I am reticent to destroy my carefully cultivated hardware-address-restricted wireless access list :/

Edited at 2013-05-14 10:00 pm (UTC)
anisity
anisity at 2013-05-13 23:04 (UTC) (Link)

Locally caching server, a la BIND?

Maybe I am not understanding your issue, but why not run a caching DNS server locally, from a real computer?

If it were me, I would also dump the DHCP on the router and go for ISCs DHCP on a real box. With a little bit of work you would be able to administer the changes to all your devices without needing to touch each device every time DNS quit resolving, assuming you continued to see issues after switching to a locally cached server.

In addition to that, since you've replaced the router and the problem persists, I would think that the issue would lie on the cable modem or possibly on Cox's equipment. Perchance there is a log file on the modem of whats going on.

Beyond that, it's anyone's guess as to what the real problem is... even harder to address when Cox wont play nice.
ehowton
ehowton at 2013-05-14 22:02 (UTC) (Link)

Re: Locally caching server, a la BIND?

I like where this is going. I could create a gateway virtual machine...Yes, excellent idea! And honestly, I don't know how to set one up, so that makes it even more fun. Thanks for the suggestion!
(Deleted comment)
ehowton
ehowton at 2013-05-15 20:47 (UTC) (Link)

Re: Locally caching server, a la BIND?

That site frightens me.
Previous Entry  Next Entry