Random DNS Issues
Saltines
Newbie

Hello Verizon Community!

I'm currently having a bit of a bit of a problem with my internet connection. My browsers will randomly fail to load a webpage, every couple of minutes. If I'm lucky, the problem goes away for a few hours, but it comes back.

Here's what I've tried so far.:

Updated to the newest firmware

Restored Modem to Factory settings

Reinstalled Ethernet Adapter Drivers

Restarted Modem and Computer Several Times

Used a different browser.

Tried using different dns servers, from google, to open dns, to level 3.

My stats are as follows:


Model: GT704-WG-B
DSL Status
VPI: 0
VCI: 35
DSL Mode Setting: Auto
DSL Negotiated Mode: ADSL2+
Connection Status: Showtime
Speed (down/up): 7840/863 Kbps
ATM QoS class: UBR
Output Power (Downstream/Upstream): 12.1/5.1 dBm
Attainable Rate (Downstream/Upstream): 16500/1147 Kbps
HEC Errors (Downstream/Upstream): 356/1
OCD Errors (Downstream/Upstream): 62/0
LCD Errors (Downstream/Upstream): 0/0
SNR Margin (Downstream/Upstream): 9.9/16.4 dB
Attenuation (Downstream/Upstream): 27.5/10.4 dB

System Log:

(GMT-05:00)19:23:43 Sun Apr 01 2012 syslog info -- MARK --
(GMT-05:00)19:29:18 Sun Apr 01 2012 user info syslog: failed dns request len=130,srcip=8.8.8.8, url=G.Verizon
(GMT-05:00)19:35:04 Sun Apr 01 2012 user info syslog: failed dns request len=68,srcip=4.2.2.1, url=upload-va.synacast.com
(GMT-05:00)19:45:44 Sun Apr 01 2012 user info syslog: failed dns request len=133,srcip=8.8.8.8, url=wpad.Verizon
(GMT-05:00)19:52:20 Sun Apr 01 2012 user info syslog: failed dns request len=130,srcip=8.8.8.8, url=G.Verizon
(GMT-05:00)20:08:15 Sun Apr 01 2012 user info syslog: failed dns request len=133,srcip=8.8.4.4, url=wpad.Verizon
(GMT-05:00)20:18:28 Sun Apr 01 2012 user info syslog: failed dns request len=135,srcip=4.2.2.1, url=isatap.Verizon
(GMT-05:00)20:18:28 Sun Apr 01 2012 user info syslog: failed dns request len=135,srcip=4.2.2.2, url=isatap.Verizon
(GMT-05:00)20:18:32 Sun Apr 01 2012 user info syslog: failed dns request len=135,srcip=4.2.2.1, url=isatap.Verizon
(GMT-05:00)20:19:42 Sun Apr 01 2012 user info syslog: failed dns request len=134,srcip=4.2.2.1, url=nat.superbt.net
(GMT-05:00)20:19:42 Sun Apr 01 2012 user info syslog: failed dns request len=137,srcip=4.2.2.1, url=router.superbt.net
(GMT-05:00)20:20:32 Sun Apr 01 2012 user info syslog: failed dns request len=133,srcip=4.2.2.1, url=wpad.Verizon
(GMT-05:00)20:21:31 Sun Apr 01 2012 user info syslog: failed dns request len=68,srcip=4.2.2.1, url=upload-va.synacast.com
(GMT-05:00)20:23:43 Sun Apr 01 2012 syslog info -- MARK --
(GMT-05:00)20:57:12 Sun Apr 01 2012 user info syslog: failed dns request len=133,srcip=8.8.4.4, url=wpad.Verizon
(GMT-05:00)21:08:03 Sun Apr 01 2012 user info syslog: failed dns request len=135,srcip=4.2.2.1, url=isatap.Verizon
(GMT-05:00)21:08:03 Sun Apr 01 2012 user info syslog: failed dns request len=135,srcip=4.2.2.2, url=isatap.Verizon
(GMT-05:00)21:08:03 Sun Apr 01 2012 user crit udhcpd: DHCP LAN Connection: Hostname:****-PC, IP : 192.168.1.65, DNS1:192.168.1.1, DNS2:4.2.2.1, GTW:192.168.1.1, Subnet:255.255.255.0
(GMT-05:00)21:08:04 Sun Apr 01 2012 user info syslog: failed dns request len=135,srcip=4.2.2.1, url=isatap.Verizon
(GMT-05:00)21:08:06 Sun Apr 01 2012 user info syslog: failed dns request len=135,srcip=4.2.2.1, url=isatap.Verizon
(GMT-05:00)21:18:01 Sun Apr 01 2012 user info syslog: failed dns request len=141,srcip=8.8.4.4, url=ums.msn.com
(GMT-05:00)21:23:43 Sun Apr 01 2012 syslog info -- MARK --

Line Quality Tests:

http://www.dslreports.com/pingtest/38cab52393a3/2896625

http://www.dslreports.com/pingtest/5a44b7293573/2896622

Smokeping Test:

http://www.dslreports.com/r3/smokeping.cgi?target=network.812baa6a38cb517cd414caaf1d94fde8

It is currently raining, and the problem is also happening, but it also occurs when the weather is fine.

The weird thing is, some services work fine, while others do not. I frequently get disconnected when trying to play online games, yet I can remain in Teamspeak, without their breaking off. However, if I try to do both at the same time, I get periods of disconnects lasting approx. 20 secs.

The time of day appears to have no impact on this problem.

Both computers, connected physically, have this issue.

Any suggested would be appreciated, I'm at my wit's end here.

0 Likes
Re: Random DNS Issues
smith6612
Community Leader
Community Leader

I could have sworn I just posted to a very similar thread over at DSLReports. They're not identical though, so I can't just link to that unfortunately.

It seems part of the modem log was cut off, but it does get to the point with the DNS Failures taking place. Try this. Disable most of the extended features of the modems down to bare minimum. Disable UPnP, use only Port Forwarding, and disable the modem's Firewall. Set the Wireless Security to WPA2 instead of WEP to keep the encryption from running within the software entirely, and try setting up only one of your PCs to use one of the following DNS Servers:

4.2.2.1

4.2.2.2

4.2.2.3

4.2.2.4

8.8.8.8

8.8.4.4

See if you notice any improvements on the said PC with DNS servers set manually rather than through DHCP.

0 Likes
Re: Random DNS Issues
Saltines
Newbie

Well, UPnp and the Firewall were already disabled.

The wi-fi was up, so I disabled that as well.

I also installed a new router, which seemed to help.

From your reply to up to a few minutes from now, there have been no problems.

However, within a few minutes ago, the problem came back, and went away.

I'll consider this problem 3/4ths of the way solved. If you have any other ideas, that would be greatly appreciated, otherwise, I can just mark this as solved.

0 Likes
Re: Random DNS Issues
smith6612
Community Leader
Community Leader
There is not a lot I can think of short of what I suggested above. If the problem is much lessened, I would just ensure at this point that the problem is not from a connection failure or from a specific device causing a problem. You can try isolating the problem further by removing some devices from the network temporarily or even drinking a very long download and ensuring the transfer does not cut out when you are seeing DNS issues.
0 Likes