Telocity and DNS: Is it too much to ask?

[Feisters]

Title says it all.

 

[linuxboy]

actually, it doesn't. What do you need done?
Are you trying to run a website and need dns resolution?

 

[Feisters]

Sorry. I should have been specific. Actually, I was ranting about Telocity's sluggish name servers. I assumed there might be other Telocity users here who are experiencing the same thing. There's been talk about it over at a dslreports.com forum. The general consensus is that Telocity has a major DNS problem. I called their tech support about the slow lookups about two weeks ago. When I finally got through, I was given two new DNS ip's to use. I hung up before it hit me that I might still have a problem. Here's why:

The Telocity gateway modem is a DHCP server that is configured via whatever Telocity uploads to it. You can view the modem status in a browser. This shows the modem firmware info, bytes sent/received, line speed, etc. In addition, it shows the various pertinent ip's including that of the Primary and Secondary DNS servers. The ip's appear to be static (they never change) even though they are, I assume, assigned by the integrated DHCP server of the modem. DNS in Win98 TCP Properties is disabled for the Telocity gateway default setup, again, letting the DHCP server handle all the details. So when tech support gave me new DNS ip's to try, I could only assume that I should enable DNS for TCP and enter the ip's there. This I did, and with mixed results. Sometimes it works great, and other times it takes forever to find a site. Or known sites aren't even found at all. And I still don't know if the TCP DNS settings override the modem DNS settings, as the modem still reports to old DNS ip's. And here's something else: when I do a DNS records search on telocity.com, I get three completely different DNS ip's than that of what tech support told me and what the modem reports.

Telocity Gateway Modem Status Report
Primary DNS: 216.227.0.100
Secondary DNS: 209.159.144.20

Telocity Tech Support Suggested DNS IP's
Primary DNS: 216.227.0.68
Secondary DNS: 216.227.56.121

DNS Records Search on telocity.com
Answer records
telocity.com 1 A 216.227.62.81 14400s
telocity.com 1 MX preference: 10 14400s
exchange: inbound.telocity.com.criticalpath.net
telocity.com 1 NS ns1.telocity.net 14400s
telocity.com 1 NS ns2.telocity.net 14400s
telocity.com 1 NS ns3.telocity.net 14400s
telocity.com 1 SOA server: ns1.telocity.net 300s
email: dnsadmin@telocity.net
serial: 2000122000
refresh: 300
retry: 300
expire: 604800
minimum ttl: 300
Authority records
Additional records
inbound.telocity.com.criticalpath.net 1 A 209.228.4.167 116s
ns1.telocity.net 1 A 216.227.56.20 1200s
ns2.telocity.net 1 A 216.227.112.50 1200s
ns3.telocity.net 1 A 216.227.0.100 1200s

Note that ns3.telocity.net has the same ip as what my modem reports as being the primary DNS ip. ??? Why is it being reported as a tertiary DNS sever?

I've tried all of the above DNS ip's in the Win98 TCP DNS properties with mixed results. I don't know if they are actually being used or not as the modem always reports the same DNS ip's as from day one. And Telocity is so flaky anyhow, it's hard to gauge any changes I make. Also, if Telocity tech support tells me to use different DNS servers, why don't they send an update to my modem to reflect that change?

 

[ktwebb]

Been using Telocity for close to year now. While there have been a couple of service outages, I have never had any other problems, including name resolution. I have heard the horror stories about there support though, luckily have never had to use them. First I have heard about resolution problems, but I cannot relate to them, since I have never had any problems.