Topic 'Failed DNS server' in forum 'FairPoint' - dslreports.com

Re: Failed DNS server

Fri, 27 Jul 2012 18:06:25 EDT

DiskoTroop posted : Ongoing problem, see my post of Nov 9 2011, this forum

Re: Failed DNS server

Thu, 26 Jul 2012 08:23:55 EDT

tschmidt posted : Looks like I declared victory too soon. Manchester DNS server is down again. As before it responds to Ping but fails to respond to DNS lookups.

Statically set DNS servers on my router.

/tom

Re: Failed DNS server

Sun, 01 Jul 2012 20:04:21 EDT

tschmidt posted : During the outage I simply statically set the working FairPoint server to primary in the router and used Google's 8.8.8.8 as backup. By and large the FairPoint DNS servers are the fastest external servers in my area.

I wanted to eliminate using any external DNS server so several years ago installed TreeWalk on our server but have had some issues so do not use it on client PCs. It is slightly faster then any of the external servers. By and large the FairPoint DNS servers have been fine. I removed the static assignment and am back to using the FairPoint servers.

I do not know if FairPoint has relationship with any Content Distribution Networks (CDN) if they do most likely using the FairPoint DNS server will improve streaming since it will point to the optimum content caching server based in geolocation.

/tom

Re: Failed DNS server

Thu, 28 Jun 2012 11:49:28 EDT

DrSmith posted : Try using google's namebench app. It will find the best performing DNS servers in your neighborhood. I have not used Verizon or Fairpoint DNS for many years now.

Re: Failed DNS server

Thu, 28 Jun 2012 11:45:00 EDT

DrSmith posted : Try using google's namebench app. It will find the best performing DNS servers in your neighborhood. I have not used Verizon or Fairpoint DNS for many years now.

Re: Failed DNS server

Wed, 27 Jun 2012 21:32:31 EDT

tschmidt posted : If anyone is interested it looks like the Manchester DNS server is working now.

/tom

Failed DNS server

Sat, 23 Jun 2012 08:54:41 EDT

tschmidt posted : I've been noticing DNS resolution has been very slow for the last few days. Finally got around to running some tests. Benchmark showed the Router with terrible DNS performance. It simply acts as a proxy for the two FairPoint DNS servers:
Pri 64.222.165.243
Sec 64.222.84.243

So I plugged both of those into the test and sure enough the Primary DNS server is not responding. Responds to Ping but not DNS queries. This causes the router to time out and switch to the secondary DNS server, hence the terrible DNS resolution time. The working server is fine. Temporally solved the problem by statically setting the DNS server address.

»www.grc.com/dns/benchmark.htm

Both the IPs are from Verizon, now assigned to FairPoint.

Judging from the names the primary server is in Manchester NH and the working secondary in Vermont.

Tracing route to irdns.manh.myfairpoint.net [64.222.165.243] over a maximum of 30 hops:   1    <1 ms    <1 ms    <1 ms  192.168.2.1  2    23 ms    23 ms    23 ms  10.20.6.1  3    23 ms    23 ms    23 ms  64.222.166.165  4    23 ms    23 ms    23 ms  irdns.manh.myfairpoint.net [64.222.165.243] Trace complete. Tracing route to irdns.sbvt.myfairpoint.net [64.222.84.243] over a maximum of 30 hops:   1    <1 ms    <1 ms    <1 ms  192.168.2.1  2    23 ms    23 ms    23 ms  10.20.6.1  3    29 ms    23 ms    23 ms  64.222.166.165  4    28 ms    28 ms    27 ms  pool-64-222-213-132.port.east.myfairpoint.net [64.222.213.132]  5    32 ms    33 ms    32 ms  pool-64-222-213-131.port.east.myfairpoint.net [64.222.213.131]  6    31 ms    31 ms    31 ms  burl-lnk-70-109-168-159.ngn.east.myfairpoint.net [70.109.168.159]  7    31 ms     *        *     burl-lnk-70-109-168-1.ngn.east.myfairpoint.net [70.109.168.1]  8    32 ms    33 ms    31 ms  irdns.sbvt.myfairpoint.net [64.222.84.243] Trace complete.

Anyone else notice this problem? I have to assume FairPoint is aware of it. I am reluctant to call support and go through the reboot your computer nonsense.

/tom