dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
26805
share rss forum feed

ajcherry

join:2006-10-28
Woodridge, IL

1 edit

Motorola NVG510 owners - any DNS problems?

Hello-

Just putting out a query to any Motorola NVG510 owners to see if anyone else has had issues when using the gateway's caching DNS proxy (which is the default configuration if you're configuring your client devices using DHCP). The most obvious symptom of the problem is that web pages don't load completely (especially failing to load images), but eventually load correctly after several refresh attempts.

I switched from 6 Mbit ADSL to 12 Mbit UVerse (IP-DSLAM, not VDSL) a few weeks ago and have had this issue from day one. AT&T has tried replacing my gateway once, but the replacement gateway seemed to have the same issue. The problem is accompanied by a lot of "no responses from nameserver '68.94.156.1' / nameserver '68.94.156.1' is now responding" messages in the gateway's diagnostics log (I get them for both DNS servers). The workaround that has worked for me is to configure my machines to talk directly to AT&T's DNS servers instead of using the gateway's IP for DNS. Aside from this one issue, everything else works great -- decent ping latency, good bandwidth, no packet loss, etc. I'm still working with AT&T support on the issue, but I figure that any additional data points from other customers would be useful to have.

When I capture a packet dump of the DNS traffic, what I see is that the DNS server on the NVG510 is actually returning 'query refused' for some of the DNS queries. This typically happens when the there's some network load and multiple simultaneous DNS queries are being performed. I've been able to reproduce the problem reliably with a test script that I can run while imposing load on the network (I use speedtest.vudu.com for the network load, since it runs for quite some time, and the script picks random hostnames from a long list to avoid getting results from the modem's cache).

I've already corresponded with one other person that has encountered the same issue, and like me, his gateway was replaced to no avail. Just wanted to do a quick survey to see how widespread this issue might be, and what firmware revisions folks are running if they do/don't have the issue.

I'm at software version 9.0.6h0d48, datapump version A2pD035b.d23i. Replacement modem was at 9.0.6h0d34, same datapump. Software rev is displayed in the System Information link in the modem's web-based GUI.

-Andrew



hmph

@sbcglobal.net

Andrew,

I used to have the same issue (and many other issues).
Moving the router to a forced "bridge" mode (it doesn't really exist inside, you configure it that way manually) and putting a normal Netgear router behind it solved most of the issues.
The description of the steps is here: »forums.att.com/t5/Features-and-H···1/page/2

In the Netgear router I setup the modem as the primary DNS, but Google's public DNS as the secondary.

This seems to mostly work so far.

- Ron


ajcherry

join:2006-10-28
Woodridge, IL

Yup, I pretty much have the same sort of setup here (using IP passthrough to my main router, a Cisco/Linksys E2000 running DD-WRT). I still had issues when my E2000 was using the modem for DNS. I finally configured the main router to not get DNS from the modem at all, which has been working well for me.

I've found the NVG510 to be an exercise in frustration, mostly due to the complete lack of publicly available documentation. I could perhaps understand this for a modem that is leased month to month and remains the property of AT&T, but not for something I was required to buy for $100.

I actually did manage to find a PDF manual of sorts, as part of the documentation for the modem's FCC certification at the FCC web site. You can go to »transition.fcc.gov/oet/ea/fccid/ and look up the modem's FCC ID (GZ5 NVG510) to find it. Be warned that this manual is labeled DRAFT, MAY BE INACCURATE, NOT FOR PRODUCTION USE, etc, but it's better than nothing.

The manual describes a rather tantalizing CLI, which is apparently either not implemented or disabled on these units. :-(



wayjac
Premium,MVM
join:2001-12-22
Indy
kudos:1

Can you post the pdf file


ajcherry

join:2006-10-28
Woodridge, IL

2 edits

I don't have a downloaded copy, I just viewed it on the FCC web site. If you search on the FCC ID and click on Details, it's right there under User Manuals.

Technically it's copyrighted, and AT&T/Motorola has apparently not seen fit to distribute it to the public (except for providing it to the FCC), so I'm not sure it's legal to post it as an attachment on the forum. I wanted to post a direct link, but it doesn't seem to work.

-Andrew



wayjac
Premium,MVM
join:2001-12-22
Indy
kudos:1

Ok



hmph

@sbcglobal.net
reply to ajcherry

Andrew,

I've been in touch with U-Verse Tier 2 support. It appears there is a DNS issue somewhere.

When you open the NVG510 under "Diagnostics", under the "Logs" tab, does the Log have lots of messages about the DNS not answering?

My log shows the following lines:

2011-11-22T22:59:33-08:00 L3 dnsmasq[3033]: no responses from nameserver '68.94.157.1'
2011-11-22T22:59:33-08:00 L3 dnsmasq[3033]: nameserver '68.94.157.1' is now responding


They appear quite a lot, and it appears either the DNS server is low or that the NVG510 is not waiting long enough for an answer.

What I did was set up in the router behind the NVG510 the NVG510 as the primary DNS, while the Google DNS (8.8.8.8) as the secondary DNS. This seems to have solved these issues.

I would appreciate it if you could let us know if you experience the same issues.

Thanks,

- Ron


ajcherry

join:2006-10-28
Woodridge, IL

4 edits

Yes, those are exactly the messages in my diagnostics log.

However, both of those DNS servers (68.94.156.1 and 68.94.157.1) respond with no issues if my machines are configured to talk directly to them instead of using the modem's IP for DNS (have to configure DNS manually on each machine to do that). As a test, I've also tried configuring a standalone dnsmasq server with the same servers, and it has no issues either. In any case, my preferred setup is to use a second router (it runs dd-wrt and is way more useful/functional than the Motorola), so I just configured that to talk to Google DNS, much as you've done.

I too been in touch with Tier 2 support, including one of their DNS guys. Right now the direction things seem to be leaning toward is a possible software/firmware bug in the dnsmasq server running on the Motorola device, since there are no obvious issues when configuring clients to talk directly to the AT&T DNS servers. The DNS guy said he would pass my information (including packet traces) to the AT&T people that handle these devices, and hopefully they can work with Motorola to figure out what the problem is. Guess we'll see if that goes anywhere. I haven't pursued it much since that last interaction, since I have a workaround.

It's worth noting that these dnsmasq error messages are apparently something Motorola or AT&T added to the code -- it has never been present in any of the "real" versions of dnsmasq. My request to Motorola for their dnsmasq source code (which we are legally entitled to, as dnsmasq is licensed under the GPL) have so far been met with no response.

One of the things I notice about a lot of these log messages is that the "now responding" happens within the same second as the "no responses". My personal suspicion is the same as yours -- that there's a timeout that's been set internally in the modem's dnsmasq code that is giving up too soon when talking to the AT&T DNS servers. That's just an educated guess, though.

By the way, I ran namebench, and from my location the AT&T servers were among the slower ones, but not the slowest of all the public servers. Google did come up as quite a bit faster.


ajcherry

join:2006-10-28
Woodridge, IL

Incidentally, has anyone else had their NVG510 reboot itself when attempting to open up the diagnostics page, after the modem has been running for a few days? That has happened to me several times now.



hmph

@sbcglobal.net

Not to me (that I noticed).

I do have random link drops throughout the day, which is quite annoying. Is your NVG510 able to maintain the link up for more than 24 hours?


ajcherry

join:2006-10-28
Woodridge, IL

I have had no dropouts -- mine has persistently maintained link with no issues for many days. The DNS issue has really been my only problem.

What do your signal levels (SNRM, attenuation, etc) look like?



hmph

@sbcglobal.net

These are the details. I never really managed to understand what good values are for ADSL2+.

The details are for a 36 hour period, which already had 14 link drops according to the logs.

Any help would be appreciated.


Downstream and Upstream Statistics

Downstream Upstream
SN Margin (dB) 8.1 13.6
Line Attenuation (dB) 29.0 19.2
Output Power(dBm) 19.0 11.9
Errored Seconds 375 0
Loss of Signal 0 0
Loss of Frame 0 0
FEC Errors 0 0
CRC Errors 1146 0


- Ron


ajcherry

join:2006-10-28
Woodridge, IL

Yeah, I don't really know what the appropriate values for ADSL2+ are either; I've just kind of assumed that the ADSL guidelines still apply, which suggests you're at the "fair" level. But who knows. My downstream SN Margin is around 10.5 even though I have similar attenuation to yours (mine is 30). My CRC error count is kinda useless right now since I was recently reset (hence my above "does anyone else" question). Maybe someone who knows more about ADSL2+ could say if your numbers look OK.

Out of curiosity, are you at 12Mbit or 18? I'm only at 12 (didn't want to pay for the professional installation, and I'm pretty sure I couldn't get the full 18Mbit sync with my 30 dB attenuation).


ajcherry

join:2006-10-28
Woodridge, IL

Oh, also out of curiosity, what do your link drop log messages look like?



hmph

@sbcglobal.net

I'm at 12mbps. Same story with not wanting to pay $150 for being told I can probably only have 12mbps. :)

Here's one of the more troubled reconnect attempts I found on the log:


2011-11-23T18:30:36-08:00 L3 sdb[305]: DSL: Last Retrain Reason: 0x1 RDI Detector
2011-11-23T18:30:37-08:00 L3 sdb[305]: DSL: Link drop counter since boot 10
2011-11-23T18:30:37-08:00 L3 sdb[305]: dns_lan_redirect_notify. DOWN. restart proxy
The last message was repeated 2 times.
2011-11-23T18:30:55-08:00 L3 sdb[305]: DSL: Filters may be missing: Yes
2011-11-23T18:30:55-08:00 L3 sdb[305]: DSL: Echo level: 0 dB
2011-11-23T18:30:55-08:00 L3 sdb[305]: DSL: Affected tones: 208
2011-11-23T18:31:01-08:00 L3 sdb[305]: DSL: Last Retrain Reason: 0x8000 Reason Unknown 2
2011-11-23T18:31:19-08:00 L3 sdb[305]: DSL: Filters may be missing: Yes
2011-11-23T18:31:19-08:00 L3 sdb[305]: DSL: Echo level: 0 dB
2011-11-23T18:31:19-08:00 L3 sdb[305]: DSL: Affected tones: 306
2011-11-23T18:31:26-08:00 L3 sdb[305]: DSL: Mode ADSL2+ (PTM)
2011-11-23T18:31:26-08:00 L3 sdb[305]: DSL: Sync Rate in kbps D/S 11788 U/S 1021
2011-11-23T18:31:26-08:00 L3 sdb[305]: DSL: Latency path Fast
2011-11-23T18:31:26-08:00 L3 sdb[305]: DSL: Trellis D/S:ON U/S:ON
2011-11-23T18:31:26-08:00 L3 sdb[305]: DSL: CO Vendor BDCM
2011-11-23T18:31:26-08:00 L3 sdb[305]: DSL: Link showtime counter since boot 11
2011-11-23T18:31:26-08:00 L3 sdb[305]: dns_lan_redirect_notify. DOWN. restart proxy
2011-11-23T18:31:30-08:00 L5 supp1x[1301]: Sending START Packet
2011-11-23T18:31:51-08:00 L4 sdb[305]: no WAN IP address detected
2011-11-23T18:32:00-08:00 L3 sdb[305]: DSL: Last Retrain Reason: 0x1 RDI Detector
2011-11-23T18:32:01-08:00 L3 sdb[305]: DSL: Link drop counter since boot 11
2011-11-23T18:32:01-08:00 L3 sdb[305]: dns_lan_redirect_notify. DOWN. restart proxy
The last message was repeated 2 times.
2011-11-23T18:32:20-08:00 L3 sdb[305]: DSL: Filters may be missing: No
2011-11-23T18:32:20-08:00 L3 sdb[305]: DSL: Echo level: 0 dB
2011-11-23T18:32:20-08:00 L3 sdb[305]: DSL: Affected tones: 14
2011-11-23T18:32:26-08:00 L3 sdb[305]: DSL: Last Retrain Reason: 0x8000 Reason Unknown 2
2011-11-23T18:32:44-08:00 L3 sdb[305]: DSL: Filters may be missing: No
2011-11-23T18:32:44-08:00 L3 sdb[305]: DSL: Echo level: 0 dB
2011-11-23T18:32:44-08:00 L3 sdb[305]: DSL: Affected tones: 6
2011-11-23T18:32:50-08:00 L3 sdb[305]: DSL: Mode ADSL2+ (PTM)
2011-11-23T18:32:50-08:00 L3 sdb[305]: DSL: Sync Rate in kbps D/S 0 U/S 0
2011-11-23T18:32:50-08:00 L3 sdb[305]: DSL: Latency path Unknown
2011-11-23T18:32:50-08:00 L3 sdb[305]: DSL: Trellis D/S:ON U/S:ON
2011-11-23T18:32:50-08:00 L3 sdb[305]: DSL: CO Vendor BDCM
2011-11-23T18:32:50-08:00 L3 sdb[305]: DSL: Link showtime counter since boot 12
2011-11-23T18:32:51-08:00 L3 sdb[305]: dns_lan_redirect_notify. DOWN. restart proxy
2011-11-23T18:32:54-08:00 L5 supp1x[1301]: Sending START Packet
2011-11-23T18:32:56-08:00 L5 supp1x[1301]: Supplicant event = SUCCESS
2011-11-23T18:35:39-08:00 L3 sdb[305]: DSL: Last Retrain Reason: 0x1 RDI Detector
2011-11-23T18:35:40-08:00 L3 sdb[305]: DSL: Link drop counter since boot 12
2011-11-23T18:35:41-08:00 L3 sdb[305]: dns_lan_redirect_notify. DOWN. restart proxy
The last message was repeated 2 times.
2011-11-23T18:35:59-08:00 L3 sdb[305]: DSL: Filters may be missing: Yes
2011-11-23T18:35:59-08:00 L3 sdb[305]: DSL: Echo level: 0 dB
2011-11-23T18:35:59-08:00 L3 sdb[305]: DSL: Affected tones: 70
2011-11-23T18:36:04-08:00 L3 sdb[305]: DSL: Filters may be missing: No
2011-11-23T18:36:04-08:00 L3 sdb[305]: DSL: Echo level: 0 dB
2011-11-23T18:36:04-08:00 L3 sdb[305]: DSL: Affected tones: -1
2011-11-23T18:36:04-08:00 L3 sdb[305]: DSL: Last Retrain Reason: 0x8000 Reason Unknown 2
2011-11-23T18:36:23-08:00 L3 sdb[305]: DSL: Filters may be missing: No
2011-11-23T18:36:23-08:00 L3 sdb[305]: DSL: Echo level: 0 dB
2011-11-23T18:36:23-08:00 L3 sdb[305]: DSL: Affected tones: 25
2011-11-23T18:36:30-08:00 L3 sdb[305]: DSL: Mode ADSL2+ (PTM)
2011-11-23T18:36:30-08:00 L3 sdb[305]: DSL: Sync Rate in kbps D/S 11998 U/S 1021
2011-11-23T18:36:30-08:00 L3 sdb[305]: DSL: Latency path Fast
2011-11-23T18:36:30-08:00 L3 sdb[305]: DSL: Trellis D/S:ON U/S:ON
2011-11-23T18:36:30-08:00 L3 sdb[305]: DSL: CO Vendor BDCM
2011-11-23T18:36:30-08:00 L3 sdb[305]: DSL: Link showtime counter since boot 13
2011-11-23T18:36:30-08:00 L3 sdb[305]: dns_lan_redirect_notify. DOWN. restart proxy
2011-11-23T18:36:34-08:00 L5 supp1x[1301]: Sending START Packet
2011-11-23T18:36:36-08:00 L5 supp1x[1301]: Supplicant event = SUCCESS
2011-11-23T18:37:01-08:00 L3 sdb[305]: DSL: Last Retrain Reason: 0x1 RDI Detector
2011-11-23T18:37:02-08:00 L3 sdb[305]: DSL: Link drop counter since boot 13
2011-11-23T18:37:02-08:00 L3 sdb[305]: dns_lan_redirect_notify. DOWN. restart proxy
The last message was repeated 2 times.
2011-11-23T18:37:20-08:00 L3 sdb[305]: DSL: Filters may be missing: No
2011-11-23T18:37:20-08:00 L3 sdb[305]: DSL: Echo level: 0 dB
2011-11-23T18:37:20-08:00 L3 sdb[305]: DSL: Affected tones: 11
2011-11-23T18:37:26-08:00 L3 sdb[305]: DSL: Last Retrain Reason: 0x8000 Reason Unknown 2
2011-11-23T18:37:44-08:00 L3 sdb[305]: DSL: Filters may be missing: No
2011-11-23T18:37:44-08:00 L3 sdb[305]: DSL: Echo level: 0 dB
2011-11-23T18:37:44-08:00 L3 sdb[305]: DSL: Affected tones: 18
2011-11-23T18:37:51-08:00 L3 sdb[305]: DSL: Mode ADSL2+ (PTM)
2011-11-23T18:37:51-08:00 L3 sdb[305]: DSL: Sync Rate in kbps D/S 11998 U/S 1021
2011-11-23T18:37:51-08:00 L3 sdb[305]: DSL: Latency path Fast
2011-11-23T18:37:51-08:00 L3 sdb[305]: DSL: Trellis D/S:ON U/S:ON
2011-11-23T18:37:51-08:00 L3 sdb[305]: DSL: CO Vendor BDCM
2011-11-23T18:37:51-08:00 L3 sdb[305]: DSL: Link showtime counter since boot 14
2011-11-23T18:37:52-08:00 L3 sdb[305]: dns_lan_redirect_notify. DOWN. restart proxy
2011-11-23T18:37:55-08:00 L5 supp1x[1301]: Sending START Packet
2011-11-23T18:37:58-08:00 L5 supp1x[1301]: Supplicant event = SUCCESS


I like it that it says filters might be missing - there are no phones on the line. :)


ajcherry

join:2006-10-28
Woodridge, IL

Yeah, it's great that it... guesses.



wpb5k

@intel.com

Thanks for all the info. Having the same issue and sort of get what you are doing for a work around.

One other piece of info that might be interesting is that when this happens I can still connect to https secured connections.

Not sure if that matters but thought I'd pass it along


rimmi2002

join:2004-01-06
Los Angeles, CA
reply to ajcherry

Add me to the list of people with these exact same issues at OP. Can't beleive AT&T is charging so much for such a crappy router/modem.

My other problem is my speed is suppose to be 12mbp and all I get is 2.5 mbs...I asked AT&T to take a look and a line tech is suppose to come...but it 2 days late for his appointment now...I wish I could get a different internet provider that AT&T in my area. Not sure what to make of it either. My modem snr..etc stats are below.

Downstream Upstream
SN Margin (dB) 11.5 6.9
Line Attenuation (dB) 36.5 24.2
Output Power(dBm) 18.1 12.1
Errored Seconds 2745 230
Loss of Signal 0 0
Loss of Frame 0 0
FEC Errors 0 0
CRC Errors 4392 229



wayjac
Premium,MVM
join:2001-12-22
Indy
kudos:1

said by rimmi2002:

My other problem is my speed is suppose to be 12mbp and all I get is 2.5 mbs...

Your downstream line attenuation needs to be below 28 to support 12Mbps
You should connect the modem at the nid test jack and record the dsl line stats

silverwolf0

join:2006-04-30
reply to ajcherry

Hi. I am having similar problems with websites not loading. I will get a dozen "page not found" errors on any given day. Refreshing a few times will eventually get the page to finally load. Occasionally a site will load without pictures. Also, on most videos on Hulu, it will say there was a problem and I should try clearing my cache. Usually on the third refresh, the error message goes away and the video finally loads. Is there a simple fix I can do to solve these problems? I don't know much about DNS or any of that sort of stuff.



texasrebel

@sbcglobal.net
reply to ajcherry

I've had this happen to me many times.. The service light is blinking green for hours and never goes solid. Hit the Diagnostics link and the modem will reset itself..

I've also noticed that I'm getting a high rate or Errored Seconds along with CRC errors on the downstream.



MeInDallas

join:2001-08-17
Dallas, TX
reply to ajcherry

I got the same thing. I had no idea what was going on until I read about yall having the same issue

2011-12-10T14:34:48-06:00 L3 dnsmasq[2399]: no responses from nameserver '99.99.99.53'
2011-12-10T14:34:48-06:00 L3 dnsmasq[2399]: nameserver '99.99.99.53' is now responding
2011-12-10T14:42:03-06:00 L3 dnsmasq[2399]: no responses from nameserver '99.99.99.153'
2011-12-10T14:42:03-06:00 L3 dnsmasq[2399]: nameserver '99.99.99.153' is now responding
2011-12-10T14:42:04-06:00 L3 dnsmasq[2399]: no responses from nameserver '99.99.99.153'
2011-12-10T14:42:04-06:00 L3 dnsmasq[2399]: nameserver '99.99.99.153' is now responding
2011-12-10T14:42:05-06:00 L3 dnsmasq[2399]: no responses from nameserver '99.99.99.153'
2011-12-10T14:42:05-06:00 L3 dnsmasq[2399]: nameserver '99.99.99.153' is now responding
2011-12-10T14:42:08-06:00 L3 dnsmasq[2399]: no responses from nameserver '99.99.99.153'
2011-12-10T14:42:08-06:00 L3 dnsmasq[2399]: nameserver '99.99.99.153' is now responding
2011-12-10T14:43:06-06:00 L3 dnsmasq[2399]: no responses from nameserver '99.99.99.153'
2011-12-10T14:43:06-06:00 L3 dnsmasq[2399]: nameserver '99.99.99.153' is now responding
2011-12-10T14:43:06-06:00 L3 dnsmasq[2399]: no responses from nameserver '99.99.99.153'
2011-12-10T14:43:07-06:00 L3 dnsmasq[2399]: nameserver '99.99.99.153' is now responding
2011-12-10T14:43:54-06:00 L3 dnsmasq[2399]: no responses from nameserver '99.99.99.153'
2011-12-10T14:43:54-06:00 L3 dnsmasq[2399]: nameserver '99.99.99.153' is now responding
2011-12-10T14:43:55-06:00 L3 dnsmasq[2399]: no responses from nameserver '99.99.99.153'
2011-12-10T14:43:55-06:00 L3 dnsmasq[2399]: nameserver '99.99.99.153' is now responding
2011-12-10T14:43:56-06:00 L3 dnsmasq[2399]: no responses from nameserver '99.99.99.53'
2011-12-10T14:44:23-06:00 L3 dnsmasq[2399]: no responses from nameserver '99.99.99.153'
2011-12-10T14:44:23-06:00 L3 dnsmasq[2399]: nameserver '99.99.99.153' is now responding
2011-12-10T14:44:53-06:00 L3 dnsmasq[2399]: Timer expired. Retry on nameserver '99.99.99.53'
2011-12-10T14:45:30-06:00 L3 dnsmasq[2399]: no responses from nameserver '99.99.99.53'
2011-12-10T14:45:30-06:00 L3 dnsmasq[2399]: nameserver '99.99.99.53' is now responding
2011-12-10T14:45:34-06:00 L3 dnsmasq[2399]: no responses from nameserver '99.99.99.53'
2011-12-10T14:45:34-06:00 L3 dnsmasq[2399]: nameserver '99.99.99.53' is now responding
2011-12-10T14:47:11-06:00 L3 dnsmasq[2399]: no responses from nameserver '99.99.99.53'
2011-12-10T14:47:11-06:00 L3 dnsmasq[2399]: no responses from nameserver '99.99.99.153'
2011-12-10T14:47:11-06:00 L3 dnsmasq[2399]: nameserver '99.99.99.53' is now responding
2011-12-10T14:48:33-06:00 L3 dnsmasq[2399]: no responses from nameserver '99.99.99.53'
2011-12-10T14:48:33-06:00 L3 dnsmasq[2399]: nameserver '99.99.99.53' is now responding
2011-12-10T14:48:34-06:00 L3 dnsmasq[2399]: Timer expired. Retry on nameserver '99.99.99.153'
2011-12-10T14:48:34-06:00 L3 dnsmasq[2399]: no responses from nameserver '99.99.99.53'
2011-12-10T14:48:34-06:00 L3 dnsmasq[2399]: nameserver '99.99.99.53' is now responding
2011-12-10T14:48:34-06:00 L3 dnsmasq[2399]: no responses from nameserver '99.99.99.153'
2011-12-10T14:48:34-06:00 L3 dnsmasq[2399]: no responses from nameserver '99.99.99.53'
2011-12-10T14:48:34-06:00 L3 dnsmasq[2399]: nameserver '99.99.99.53' is now responding
2011-12-10T14:48:34-06:00 L3 dnsmasq[2399]: no responses from nameserver '99.99.99.53'
2011-12-10T14:48:34-06:00 L3 dnsmasq[2399]: nameserver '99.99.99.53' is now responding
2011-12-10T14:48:37-06:00 L3 dnsmasq[2399]: nameserver '99.99.99.153' is now responding
2011-12-10T14:48:42-06:00 L3 dnsmasq[2399]: no responses from nameserver '99.99.99.153'
2011-12-10T14:48:42-06:00 L3 dnsmasq[2399]: no responses from nameserver '99.99.99.53'

It just goes on and on and on forever!



sadATTpatron

@sbcglobal.net
reply to texasrebel

Actually TexR I think that's a different problem. The DNS thing happens despite rock solid physical connections. I have exactly this problem with the same log output even though I am literally kitty corner across the street from the telephone switching office and my lights are always solid green. It is apparently some firmware glitch inside the NVG510 modems, which might or might not involve the modem just timing out on waiting for the DNS servers to provide an IP address. You can't control the the name server defaults and it probably wouldn't help if you could since all DNS servers are going to have occasional delays.



kernel

@sbcglobal.net
reply to silverwolf0

If you have 2nd router behind the NVG510, you should add the opendns ip addresses:

208.67.222.222

208.67.220.220

I don't have page load issues with my setup.



MeInDallas

join:2001-08-17
Dallas, TX
reply to ajcherry

Is there any other way to fix this other then going out and buying another router that you dont need? This is getting really annoying



MeInDallas

join:2001-08-17
Dallas, TX

I called Uverse yesterday and they are sending me a new one but from what you guys are saying here its just the same old thing. I hope maybe it has a newer firmware installed but the one I have now is only like a month old so I doubt it.



David
hours are m-th 1130-10p central
Premium,VIP
join:2002-05-30
Granite City, IL
kudos:98
Reviews:
·DIRECTV
·AT&T Midwest
·magicjack.com
·Google Voice
reply to MeInDallas

said by MeInDallas:

Is there any other way to fix this other then going out and buying another router that you dont need? This is getting really annoying

from what I got from DNSguy See Profile just hard code the DNS info in your PC if you can. For tablets and such, I am not so sure.


MeInDallas

join:2001-08-17
Dallas, TX

I hadnt seen that post but I just found it. That totally fixed it! Thanks!



dddane

join:2002-01-10
Chicago, IL
reply to texasrebel

i'm on AT&T with this model and posted in the ATT direct forum... someone responded saying they think this is a known issue with this motorola and they are awaiting a fix.

seems absurd that they don't know more about this issue. they're wasting my time and theirs. at this point i've been downgraded in speed and i have to wonder if that was even necessary

it was getting sub-par connectivity before but now seems OK... but oddly the connection wasn't ever "down" it was just getting less than provisioned speeds so everything would come to a standstill because the modem forces you to click override in the browser... so regardless of if the connection is having issues they're causing their own issues with this software it's running

this modem seems horrible..



MeInDallas

join:2001-08-17
Dallas, TX

Since I put the DNS numbers in mine its been flying and no errors.