DNS Issues?
Closed
twizforpros
Posts
6
Registration date
Thursday September 26, 2013
Status
Member
Last seen
October 2, 2013
-
Sep 26, 2013 at 12:16 PM
twizforpros Posts 6 Registration date Thursday September 26, 2013 Status Member Last seen October 2, 2013 - Oct 2, 2013 at 06:42 PM
twizforpros Posts 6 Registration date Thursday September 26, 2013 Status Member Last seen October 2, 2013 - Oct 2, 2013 at 06:42 PM
Related:
- Verizon dns issues
- Dns address cannot be found android - Guide
- Verizon activation number 877 - Guide
- Dns benchmark - Download - Networks
- Dns jumper - Download - Other
- Switch from verizon to sprint - Guide
3 responses
Good Afternoon.
You mentioned that you changed DNS servers, from what to what?
On the PC, what is its IP address?
YOur DNS should be the same as your FIOS gateway. You can always put 4.2.2.2 in manually to see if it is a network problem. If traffic flows with 4.2.2.2, then the DNS admin is wrong.
You mentioned that you changed DNS servers, from what to what?
On the PC, what is its IP address?
YOur DNS should be the same as your FIOS gateway. You can always put 4.2.2.2 in manually to see if it is a network problem. If traffic flows with 4.2.2.2, then the DNS admin is wrong.
twizforpros
Posts
6
Registration date
Thursday September 26, 2013
Status
Member
Last seen
October 2, 2013
Sep 26, 2013 at 01:20 PM
Sep 26, 2013 at 01:20 PM
Thank you for this response.
1) The messages in my post were with primary 208.67.222.220 and secondary 205.171.2.65, which had been recommended by a netbench run ( https://code.google.com/archive/p/namebench ). BTW, these messages were shortly after a router power down/up cycle.
Since the messages and symptoms were the same as I'd gotten previously with the Verizon servers, I have switched back to them. They are primary 68.238.96.12 and secondary 68.238.112.12
2) According to the router, my desktop is 192.168.1.13
3) I am happy to try DNS primary 4.2.2.2. With respect, I don't understand what you mean by "...then DNS Admin is wrong." Do I need a different secondary DNS with primary 4.2.2.2?
Thanks again!
1) The messages in my post were with primary 208.67.222.220 and secondary 205.171.2.65, which had been recommended by a netbench run ( https://code.google.com/archive/p/namebench ). BTW, these messages were shortly after a router power down/up cycle.
Since the messages and symptoms were the same as I'd gotten previously with the Verizon servers, I have switched back to them. They are primary 68.238.96.12 and secondary 68.238.112.12
2) According to the router, my desktop is 192.168.1.13
3) I am happy to try DNS primary 4.2.2.2. With respect, I don't understand what you mean by "...then DNS Admin is wrong." Do I need a different secondary DNS with primary 4.2.2.2?
Thanks again!
twizforpros
Posts
6
Registration date
Thursday September 26, 2013
Status
Member
Last seen
October 2, 2013
Sep 26, 2013 at 02:27 PM
Sep 26, 2013 at 02:27 PM
Thanks, ac3mark!
I need to do some homework to sort out what "gateway" means, where/how I specify it, and how it's currently specificed in my config. I may have answered the quesion about the desktop ip incorrectly. I believe 192.168.1.13 was assigned to the desktop by the router.
The Verizon router is 192.168.1.1 and the Asus router is 192.168.1.2. I (think I) have things configured so that the Asus just hands requests for DNS services on to the Verizon router.
Thanks for helping me - stay tuned.
I need to do some homework to sort out what "gateway" means, where/how I specify it, and how it's currently specificed in my config. I may have answered the quesion about the desktop ip incorrectly. I believe 192.168.1.13 was assigned to the desktop by the router.
The Verizon router is 192.168.1.1 and the Asus router is 192.168.1.2. I (think I) have things configured so that the Asus just hands requests for DNS services on to the Verizon router.
Thanks for helping me - stay tuned.
twizforpros
Posts
6
Registration date
Thursday September 26, 2013
Status
Member
Last seen
October 2, 2013
Sep 30, 2013 at 06:19 PM
Sep 30, 2013 at 06:19 PM
Sorry to take so long.
I've gone over the router settings. DHCP is disabled in the Asus (192.168.1.2). The Asus is Ethernet cabled Lan-to-Lan to the Verizon router (192.168.1.1). The Verison router identifes the primary and secondary DNS server.
I changed the second DNS server to 4.2.2.2, but failures are the same. A failover to the 2ry router, then invalid PTR messages, then timeouts.
I doubt the DNS servers have as many bad PTR records as I get bad PTR record error messages. Is there a way to figure out what's causing the invalid PTR messages?
I've gone over the router settings. DHCP is disabled in the Asus (192.168.1.2). The Asus is Ethernet cabled Lan-to-Lan to the Verizon router (192.168.1.1). The Verison router identifes the primary and secondary DNS server.
I changed the second DNS server to 4.2.2.2, but failures are the same. A failover to the 2ry router, then invalid PTR messages, then timeouts.
I doubt the DNS servers have as many bad PTR records as I get bad PTR record error messages. Is there a way to figure out what's causing the invalid PTR messages?
Ok, The DNS settings in the verizon router, did you administer those settings? On your router DHCP Administration, you should have the first DNS as the router IP address you gave it own your network. Once again, do not adminster the CLIENTS with a DNS query address of anything outside your own network, they should query the gateway/or INternal DNS if you have one running.
OK. Is your network routing video to STB's?
So here is how it should look.....
ONT(optical Network terminal big box bolted to house!) to Verizon gateway.
Verizon Gateway DHCP Disabled. By the way, I used to deploy AT&T Uverse (same Product). (Side NOTE:I *used to* because I got sick of getting emails saying we were not efficient enough, and then get another Email saying that AT&T is going to clear Millions in profit for the quarter,and I wouldn't see anything but another ticket to go fix.) (Another SIDE NOTE: The AT&T computers have scoured this web looking for the key phrase AT&T and it has shown up on someones report; this person used to study the randomness of ocean waves and can determine swell, they have applied his algorythm to the social networking sphere. If you think I am joking, go do some research!)
Okay got side tracked, The first device off the ONT-disabled the DHCP and make certain it is set for IP address of 192.168.1.1 This is all of the administration that you should change in the gateway.
Now.
Wireless router-Static IP address of 192.168.1.10
wireless router-DCHP Enabled - access pool above 1.10
DHCP DNS settings 192.168.1.1, 4.2.2.2
Do not administer any settings in your Verizon gateway, except for the IP address of 192.168.1.1
You may have to build a static route from your second gateway, into your first, but unlessyou are bridging two seperate subnets, this should not have to be accomplished.
//ark
-Contributor
So here is how it should look.....
ONT(optical Network terminal big box bolted to house!) to Verizon gateway.
Verizon Gateway DHCP Disabled. By the way, I used to deploy AT&T Uverse (same Product). (Side NOTE:I *used to* because I got sick of getting emails saying we were not efficient enough, and then get another Email saying that AT&T is going to clear Millions in profit for the quarter,and I wouldn't see anything but another ticket to go fix.) (Another SIDE NOTE: The AT&T computers have scoured this web looking for the key phrase AT&T and it has shown up on someones report; this person used to study the randomness of ocean waves and can determine swell, they have applied his algorythm to the social networking sphere. If you think I am joking, go do some research!)
Okay got side tracked, The first device off the ONT-disabled the DHCP and make certain it is set for IP address of 192.168.1.1 This is all of the administration that you should change in the gateway.
Now.
Wireless router-Static IP address of 192.168.1.10
wireless router-DCHP Enabled - access pool above 1.10
DHCP DNS settings 192.168.1.1, 4.2.2.2
Do not administer any settings in your Verizon gateway, except for the IP address of 192.168.1.1
You may have to build a static route from your second gateway, into your first, but unlessyou are bridging two seperate subnets, this should not have to be accomplished.
//ark
-Contributor
twizforpros
Posts
6
Registration date
Thursday September 26, 2013
Status
Member
Last seen
October 2, 2013
Oct 2, 2013 at 06:42 PM
Oct 2, 2013 at 06:42 PM
Wow, thanks for all this, but frankly I'd be quite uncomfortable altering the settings in the ONT. I'm not even sure I can "see" or have access to the ONT settings.
There's a procedure for what I've done in the DSL Reports forum at http://www.dslreports.com/faq/verizonfios/3.0_Networking It shows how to "front -end" the Verizon router with a more modern wireless device. And, BTW, yes, the router manages four video set top boxes via MOCA, three of which are DVRs.
Again, my configuration works..., except when it doesn't. It's been behaving itself reasonably well over the last several days (maybe it knows you're on the case). I was hoping to determine how to troubleshoot the DNS, but I've changed DNS servers multiple times with no discernible result. Most of the "latency/loss of internet services" items I can find in various forums don't seem to get resolved, or rather they get resolved over and over again with replacement routers and/or other actions that make things better for a period of time. Verizon "bounced" the ONT for me several weeks ago, and things got better, but didn't go away. There's no single owner for issues once they are on the internet side of my router, I guess.
I'm reluctant to do anything that will be seen by Verizon as "not a supported configuration," but thanks all the same for all your suggestions.
Best...
There's a procedure for what I've done in the DSL Reports forum at http://www.dslreports.com/faq/verizonfios/3.0_Networking It shows how to "front -end" the Verizon router with a more modern wireless device. And, BTW, yes, the router manages four video set top boxes via MOCA, three of which are DVRs.
Again, my configuration works..., except when it doesn't. It's been behaving itself reasonably well over the last several days (maybe it knows you're on the case). I was hoping to determine how to troubleshoot the DNS, but I've changed DNS servers multiple times with no discernible result. Most of the "latency/loss of internet services" items I can find in various forums don't seem to get resolved, or rather they get resolved over and over again with replacement routers and/or other actions that make things better for a period of time. Verizon "bounced" the ONT for me several weeks ago, and things got better, but didn't go away. There's no single owner for issues once they are on the internet side of my router, I guess.
I'm reluctant to do anything that will be seen by Verizon as "not a supported configuration," but thanks all the same for all your suggestions.
Best...
