warichard
Well-Known Member
Hi Guys,
We are currently running a test with the Verizon service in an attempt to determine whether there is an issue with the general functioning of the service that has been brought to our attention.
If any of you are currently running on Verizon (such as by using wadsl.unshaped.v if you're with us) can you please let us know (in this thread is fine) if you are experiencing problems connecting to sites or resolving hostnames?
If you seem to frequently get "site not found" or "site unavailable" errors or otherwise broken pages (such as site styles not loading, etc.) when attempting to browse, especially for sites you know should exist, please can you provide us with the IP address(es) of both the primary and secondary DNS servers that have been assigned to your router, as well as for how long you have been experiencing the problem, additionally (if at all possible) can you provide us with the result of a nslookup (windows nslookup preferably), providing the name of the site you are attempting to get to, the host name/ip address of the dns server the nslookup was done on as well as what the result was for the specific address you were doing an nslookup on.
To use nslookup on windows, open up a command prompt by either (a) clicking 'Start' and 'Run' and typing 'cmd' in the textbox (without quotes) and pressing enter (Windows version prior to Vista) or (b) by pressing start and typing 'cmd' (without quotes) and pressing enter (Windows Vista). Once you have a command prompt open, type:
nslookup <domain>
and press enter. For example to look up the IP address of www.google.com you would type:
nslookup www.google.com
The output when it works should look something like:
Server: wblv-ip-dns-3.saix.net
Address: 196.25.1.11
Non-authoritative answer:
Name: www.l.google.com
Addresses: 66.249.93.104
66.249.93.147
66.249.93.99
Aliases: www.google.com
Once you have done an nslookup on the address causing issues, please paste the result in your response as well so we can see if there is an error, and if so, which DNS server specifically is causing the problem.
Thanks.
We are currently running a test with the Verizon service in an attempt to determine whether there is an issue with the general functioning of the service that has been brought to our attention.
If any of you are currently running on Verizon (such as by using wadsl.unshaped.v if you're with us) can you please let us know (in this thread is fine) if you are experiencing problems connecting to sites or resolving hostnames?
If you seem to frequently get "site not found" or "site unavailable" errors or otherwise broken pages (such as site styles not loading, etc.) when attempting to browse, especially for sites you know should exist, please can you provide us with the IP address(es) of both the primary and secondary DNS servers that have been assigned to your router, as well as for how long you have been experiencing the problem, additionally (if at all possible) can you provide us with the result of a nslookup (windows nslookup preferably), providing the name of the site you are attempting to get to, the host name/ip address of the dns server the nslookup was done on as well as what the result was for the specific address you were doing an nslookup on.
To use nslookup on windows, open up a command prompt by either (a) clicking 'Start' and 'Run' and typing 'cmd' in the textbox (without quotes) and pressing enter (Windows version prior to Vista) or (b) by pressing start and typing 'cmd' (without quotes) and pressing enter (Windows Vista). Once you have a command prompt open, type:
nslookup <domain>
and press enter. For example to look up the IP address of www.google.com you would type:
nslookup www.google.com
The output when it works should look something like:
Server: wblv-ip-dns-3.saix.net
Address: 196.25.1.11
Non-authoritative answer:
Name: www.l.google.com
Addresses: 66.249.93.104
66.249.93.147
66.249.93.99
Aliases: www.google.com
Once you have done an nslookup on the address causing issues, please paste the result in your response as well so we can see if there is an error, and if so, which DNS server specifically is causing the problem.
Thanks.