DNS Servers met P-2812HNU-F1

  • 27 maart 2012
  • 3 reacties
  • 5449 keer bekeken

Onder de DNS-instellingen van het P-2812HNU-F1 modem is de Local Network Nameserver als eerste DNS Server ingesteld en deze kan niet worden aangepast.
Graag zou ik deze willen aanpassen voor een andere (snellere, meer stabiele) DNS-server.
DNS Benchmark (van Gibson Research) geeft aan dat de Local Network Nameserver langzamer is dan enkele openbaar toegankelijke DNS-servers, w.o. ook die van Green ISP (KPN, Telfort etc.).
Graag zou ik zien dat ik deze instellingen vrijelijk kan instellen.

DNS Server 1: [From ISP] (aanpasbaar)
DNS Server 2: [From ISP] (aanpasbaar)
DNS Server 3: Local Network Nameserver (eventueel niet aanpasbaar)

3 reacties

Kan Webcare de DNS instellingen van het P-2812HNU-F1 vrijgegeven zodat ik deze handmatig kan aanpassen. Sinds de overgang naar een nieuwe abonnement ontvang ik relatief veel website time-outs. Met het oude Zyxel modem (P-2602R) had ik hier geen last van.

Ook kon ik op dit modem de DNS-instellingen handmatig aanpassen i.t.t. de P-2812HNU-F1. Nu wil ik graag testen of de geconstateerde problemen opgelost kunnen worden door de DNS-servers handmatig te wijzigen. Maar dat is met de huidige firmware niet mogelijk.
Hier zijn enkele gegevens m.b.t. de standaard DNS-serverinstellingen van het modem.

Test uitgevoerd met DNSBenchmark van Gibson Research.

DNS Benchmark Conclusions & Recommendations

[b]DNS Benchmark Conclusions & Recommendations[/b]
What the results you have just obtained mean to YOU
The results summary, conclusions, and recommendations from your most recent run of this DNS benchmark are provided below. Please carefully consider the implications of making any changes to your system's current configuration before doing so.
 System has multiple redundant nameservers configured.
This system is currently configured to use 3 separate nameservers for DNS name resolution. This is in keeping with recommended best practice (of having at least two different nameservers) so that the temporary failure of any single nameserver will not prevent all DNS name resolution.

 All system nameservers are alive & replying to queries.
All of this system's 3 nameservers are working and replying to queries. This is terrific because if the system's primary nameserver were to become overloaded or unavailable, even briefly, one or more backup nameservers are standing by ready to supply DNS lookup services.
 System's nameservers are probably optimally ordered.
Windows uses DNS servers in the order they are listed under the network adapter's properties, or when obtained automatically from an ISP, in the order provided by the ISP. Windows will fall back to using the second, third, and other nameservers only when the first listed nameserver fails to respond. So if the first nameserver happened to be very slow, but working, everything would be slowed down. Consequently, the order of nameserver listing should match their order of decreasing performance . . . which is probably how this system is currently configured:
Usage Order Nameserver IP Speed Rank
----------- --------------- ----------
1 192.168. 1.254 1 unreliable
2 195.241. 77. 54 2
3 195.241. 77. 58 3 Why only "probably" ?
Only "probably" because there wasn't enough of a statistically significant difference between their timings to be able to make any claims with at least 95% confidence. Here are the details:
When this benchmark is allowed to finish, it will have collected approximately one hundred and fifty (150) DNS performance samples from each nameserver being tested. Although this is sufficient to generate a good average performance estimate, if the collection of sampled values are too widely spread apart (in other words, not a lot of agreement among samples), it is impossible to know with "statistical certainty" (to be 95% sure) how individual nameservers compare to each other.
Therefore, even if the ranking shown above appears to be out of order, the differences are not statistically significant, and you should not be concerned. If you were to re-run the benchmark you might get a different outcome. This benchmark conclusion page will inform you when a problem exists that is statistically significant, and will then advise you that your DNS nameserver settings should be changed. But that is not the case with the benchmark results that were just obtained.

 System nameservers are faster than ALL public alternatives.
All of the DNS resolvers your system is using are responding faster than any of the 100% reliable publicly available alternative DNS nameservers this benchmark utility just tested. Therefore, there would be no performance benefit from replacing any of this system's current nameservers with any of those publicly available alternatives. However, this best performance appraisal assumes that this system's nameservers are 100% reliable. See the next item below for an appraisal of your nameservers' reliability.Note: If there appeared to be one or more faster public alternative nameservers, there was enough uncertainty created by the spread of benchmark timing results that it was not possible to be at least 95% confident that any of those faster-seeming nameservers really were reliably faster than the nameservers this system is currently using. So it made no sense to alarm you about the need to change things when there was insufficient evidence.

 One or more system nameservers is NOT 100% reliable!
DNS reliability is extremely important, since lookup requests that are dropped and ignored by nameservers cause significant delays in Internet access while the querying system waits for a reply. The system is then finally forced to reissue the query to the same or to backup nameservers. While your system is patiently waiting for a reply, you are impatiently waiting to get on with your Internet access.During this benchmark test, the nameservers being tested did not reply to some of the DNS queries they were sent.
So the question now is: Did the benchmark discover alternative nameservers having superior performance and reliability to which you could switch in order to obtain more performance and reliability?Important Note:
• Incorrect warnings of low reliability nameservers can arise if (1) DNS benchmarking is being performed while the local network is busy performing other work such as file downloading, or (2) the benchmark is running over a wireless (WiFi) link with low signal strength or high interference. Please try to minimize any other local network activity while the benchmark is running, and use a wired (not wireless) LAN connection if possible.Recommended Actions:
• Before you make any changes, you should probably run the benchmark a few more times at differing times of day to make sure that the troubling reliability is an ongoing problem and not just a brief occurrence.• You may also wish to consult the "Tabular Data" page which summarizes all benchmark results in numeric tables. The numbers make it easier to see exactly how unreliable your system's nameservers are compared with the available alternatives. (And also how the alternatives' performance compares.)

 All of this system nameservers return errors.
This is a GOOD thing! Some DNS providers, such as OpenDNS and even the Earthlink, Roadrunner and Comcast ISPs, redirect incorrectly entered URLs to their own advertising-laden marketing-driven interception page instead of simply returning an error to the web browser. But this system's nameservers are returning errors when asked to lookup non-existent domain names.
 System nameservers are replying to all query types.
During the development of this DNS Benchmark we discovered that the routers used by some pre-release testers were not returning results for the benchmark's Uncached and/or Dotcom testing queries. Even though these queries are admittedly unusual, they are completely valid. So the only conclusion was that those few routers were inherently defective. The good news here is that your nameservers are replying to these unusual but valid queries.

____________________________________________________________________REMEMBER TO CHECK SPOOFABILITY !!
Whether you make any changes to your nameservers or not, but
especially if you do, be sure to verify the security of your final DNS
resolver set by using GRC's free "DNS Spoofability" testing service!
If you require assistance . . .
If you require assistance with the implementation any of the suggested changes to your system's DNS configuration, several sources of help are available:• For help with the operation and use of this DNS Benchmark program, please reference the extensive DNS Benchmark pages at the GRC website:
http://www.GRC.com/dns/benchmark.htm • For help with any of the specific conclusions or recommendations above, please see the DNS Benchmark FAQ (Frequently Asked Questions) page:
http://www.GRC.com/dns/benchmark-faq.htm • Knowledge of the DNS domain name system is widespread among those in public technical Internet forums. You will very likely be able to obtain answers to any specific questions you may have by asking knowledgeable inhabitants of online communities.
• GRC maintains and operates a comprehensive online "newsgroup" community and has a specific newsgroup - grc.dns - dedicated to the discussion of DNS issues including this DNS benchmark program (where it was developed) and GRC's online DNS Spoofability testing service. Please see the following web page for help with joining and participating in GRC's terrific newsgroups: http://www.GRC.com/discussions.htm
GRC's technical support services are limited to the support of licensees of our commercial software products and do not extend to the support of our freely available software or online services. Please do not write to us (GRC / Gibson Research Corporation) for assistance in connection with this freeware utility.You will find that ample help is freely available
within the Internet community. Thank you!
- Steve GibsonPlease Note: This program is Copyright (c) 2010 by Gibson Research Corporation -- ALL RIGHTS RESERVED. This program is FREEWARE. Although it may not be altered in any way, it MAY BE FREELY COPIED AND DISTRIBUTED onto and through any and all computer media in ANY form or fashion. You are hereby granted the right to do so.
• • •
Gedetailleerde gegevens m.b.t. bovenstaande DNS-serverinstellingen.

N.B. Verkort overzicht i.v.m. maximaal aantal van 10.000 tekens per bericht.

 Final benchmark results, sorted by nameserver performance:
(average cached name retrieval speed, fastest to slowest)
192.168. 1.254 | Min | Avg | Max |Std.Dev|Reliab%|
+ Cached Name | 0,000 | 0,001 | 0,001 | 0,000 | 100,0 |
+ Uncached Name | 0,025 | 0,124 | 0,536 | 0,133 | 94,0 |
+ DotCom Lookup | 0,027 | 0,050 | 0,113 | 0,028 | 97,9 |
Local Network Nameserver

82.201. 33. 5 | Min | Avg | Max |Std.Dev|Reliab%|
- Cached Name | 0,018 | 0,018 | 0,019 | 0,000 | 100,0 |
- Uncached Name | 0,020 | 0,082 | 0,305 | 0,086 | 100,0 |
- DotCom Lookup | 0,019 | 0,020 | 0,021 | 0,000 | 100,0 |
IS Interned Services
195.241. 77. 54 | Min | Avg | Max |Std.Dev|Reliab%|
+ Cached Name | 0,018 | 0,018 | 0,019 | 0,000 | 100,0 |
+ Uncached Name | 0,019 | 0,099 | 0,404 | 0,104 | 100,0 |
+ DotCom Lookup | 0,024 | 0,066 | 0,200 | 0,053 | 100,0 |
Green ISP B.V.

195.241. 77. 53 | Min | Avg | Max |Std.Dev|Reliab%|
- Cached Name | 0,018 | 0,018 | 0,019 | 0,000 | 100,0 |
- Uncached Name | 0,021 | 0,100 | 0,396 | 0,110 | 100,0 |
- DotCom Lookup | 0,025 | 0,057 | 0,184 | 0,050 | 100,0 |
Green ISP B.V.
62.204. 64.101 | Min | Avg | Max |Std.Dev|Reliab%|
- Cached Name | 0,018 | 0,018 | 0,019 | 0,000 | 100,0 |
- Uncached Name | 0,023 | 0,127 | 0,595 | 0,133 | 100,0 |
- DotCom Lookup | 0,022 | 0,034 | 0,138 | 0,027 | 100,0 |
Flatbox Facilities BV

195.241. 77. 58 | Min | Avg | Max |Std.Dev|Reliab%|
+ Cached Name | 0,017 | 0,018 | 0,019 | 0,000 | 100,0 |
+ Uncached Name | 0,019 | 0,133 | 1,159 | 0,183 | 100,0 |
+ DotCom Lookup | 0,021 | 0,056 | 0,107 | 0,032 | 100,0 |
Green ISP B.V.
195. 18.114. 5 | Min | Avg | Max |Std.Dev|Reliab%|
- Cached Name | 0,019 | 0,019 | 0,020 | 0,000 | 100,0 |
- Uncached Name | 0,020 | 0,081 | 0,296 | 0,086 | 100,0 |
- DotCom Lookup | 0,021 | 0,027 | 0,143 | 0,021 | 100,0 |
QINIP Internal Network

213.133. 33. 2 | Min | Avg | Max |Std.Dev|Reliab%|
- Cached Name | 0,018 | 0,019 | 0,022 | 0,001 | 100,0 |
- Uncached Name | 0,020 | 0,086 | 0,319 | 0,086 | 100,0 |
- DotCom Lookup | 0,020 | 0,041 | 0,105 | 0,022 | 100,0 |
IS Interned Services
192.168. 1. 1 | DNS queries are not answered at this IP.
Non-routable local internet address
Local Network Nameserver
UTC: 2012-04-27, from 09:27:47 to 09:31:11, for 03:23,453
Interpreting your benchmark results above:The following guide is only intended as a quick
"get you going" reference and reminder.
To obtain a working understanding of this program's operation, and to familiarize yourself with its many features, please see the main DNS Benchmark web page by clicking on the "Goto DNS Page" button below.Referring to this sample:
64. 81.159. 2 | Min | Avg | Max |Std.Dev|Reliab%
- Cached Name | 0.001 | 0.001 | 0.001 | 0.000 | 100.0
- Uncached Name | 0.021 | 0.033 | 0.045 | 0.016 | 100.0
- DotCom Lookup | 0.021 | 0.022 | 0.022 | 0.001 | 100.0
SpeakeasyThe Benchmark creates a table similar to the one above for each DNS resolver (nameserver) tested. The top line specifies the IP address of the nameserver for this table.
• The first three numeric columns provide the minimum, average, and maximum query-response times in seconds. Note that these timings incorporate all network delays from the querying computer, across the Internet, to the nameserver, the nameserver's own processing, and the return of the reply. Since the numbers contain three decimal digits of accuracy, the overall resolution of the timing is thousandths of a second, or milliseconds.• The fourth numeric column shows the "standard deviation" of the collected query-response times which is a common statistical measure of the spread of the values - a smaller standard deviation means more consistency and less spread.
• The fifth and last numeric column shows the reliability of the tested nameserver's replies to queries. Since lost, dropped, or ignored queries introduce a significant lookup delay (typically a full second or more each) a nameserver's reliability is an important consideration.The labels of the middle three lines are colored red, green, and blue to match their respective bars on the response time bar chart.
• The "Cached Name" line presents the timings for queries that are answered from the server's own local name cache without requiring it to forward the query to other name servers. Since the name caches of active public nameservers will always be full of the IPs of common domains, the vast majority of queries will be cached. Therefore, the Benchmark gives this timing the highest weight.• The "Uncached Name" line presents the timings for queries which could not be answered from the server's local cache and required it to ask another name server for the data. Specifically, this measures the time required to resolve the IP addresses of the Internet's 30 most popular web sites. The Benchmark gives this timing the second highest weight.
• The "DotCom Lookup" line presents the timings for the resolution of dot com nameserver IP addresses. This differs from the Cached and Uncached tests above, since they measure the time required to determine a dot com's IP, whereas the DotCom Lookup measures the time required to resolve the IP of a dot com's nameserver, from which a dot com's IP would then be resolved. This test presents a measure of how well the DNS server being tested is connected to the dot com nameservers.The lower border of the table contains a set of eight indicators (O and -) representing non-routable networks whose IP addresses are actively blocked by the resolver to protect its users from DNS rebinding attacks: <O-OO---->. The "O" character indicates that blocking is occurring for the corresponding network, whereas the "-" character indicates that non-routable IP addresses are being resolved and rebinding protection is not present. The first four symbols represent the four IPv4 networks beginning with 10., 127., 172., and 192. respectively, and the second four symbols are the same networks but for IPv6.
The final two lines at the bottom of each chart duplicate the information from the Name and Owner tabs on the Nameserver page: dns.chi1.speakeasy.net
The first line displays the "Reverse DNS" name of the server, if any. (This is the name looked up by the nameserver's IP address.) The second line displays the Ownership information, if any, of the network containing the nameserverThe final line of the automatically generated chart is a timestamp that shows the date and time of the start, completion, and total elapsed time of the benchmark:
UTC: 2009-07-15 from 16:41:50 to 16:44:59 for 03:08.703All times are given in Universal Coordinated Time (UTC) which is equivalent to GMT. In the sample shown above, the entire benchmark required 3 minutes, 8.703 seconds to run to completion.
All, or a marked portion, of the Tabular Data results on this page may be copied to the Windows' clipboard or saved to a file for safe keeping, sharing, or later comparison.
• • •