Changes between Version 6 and Version 7 of doc/DnsResolver/TestDnsResolving


Ignore:
Timestamp:
Sep 17, 2012, 1:22:24 PM (7 years ago)
Author:
Bry8Star
Comment:

adding acronym list links to other pages

Legend:

Unmodified
Added
Removed
Modified
  • doc/DnsResolver/TestDnsResolving

    v6 v7  
    1919<b>|</b> <a href="#NSLookup">NSLookup</a>
    2020<b>|</b> <a href="#DiG">DiG (dig)</a>
     21<b>|</b> <a href="#Get_DiG">Get DiG</a>
    2122<b>|</b> <a href="#Add_DiG_in_PATH">Add DiG in PATH</a>
    2223<b>|</b> <a href="#DiG_with_Unicode_Support">DiG with Unicode support</a>
     
    2728<b>|</b> <a href="#Load_Unicode_Font">Install Unicode Font</a>
    2829<b>|</b> <a href="#Type_Unicode">Type & Show Unicode Characters</a>
     30<b>|</b> <a href="#TLD_IDN_Numeric">TLDs, IDNs With Numeric Digits</a>
     31<b>|</b> <a href="#Test_Via_TCP_DNS">Test Using TCP DNS Query</a>
     32<b>|</b> <a href="#Test_Via_Specific_Nameserver">Test DNS Query On Specific DNS/Nameserver</a>
    2933<b>|</b> <a href="#Credits">Credits</a>
    3034<b>|</b>
     35<br />
     36<br />
     37Goto other pages if you need a short/brief info on these<b>:</b><br />
     38<b>|</b> <a href="../DnsResolver#DNS">DNS</a>
     39<b>|</b> <a href="../DnsResolver#DNSSEC">DNSSEC</a>
     40<b>|</b> <a href="../DnsResolver#TLD">TLD</a>
     41<b>|</b> <a href="../DnsResolver#SLD">SLD</a>
     42<b>|</b> <a href="../DnsResolver#ROOT">Root Zone</a>
     43<b>|</b> <a href="../DnsResolver#IDN">IDN</a>
     44<b>|</b> <a href="../DnsResolver#NIC">NIC</a>
     45<b>|</b> <a href="../DnsResolver#LtR">LtR</a>
     46<b>|</b> <a href="../DnsResolver#LMS">LMS</a>
     47<b>|</b> <a href="../DnsResolver#Punycode">Punycode</a>
     48<b>|</b> <a href="../DnsResolver#ICANN">ICANN</a>
     49<b>|</b> <a href="../DnsResolver#IANA">IANA</a>
     50<b>|</b> <a href="../DnsResolver#VeriSign">VeriSign</a>
     51<b>|</b> <a href="../DnsResolver#PIR">PIR</a>
     52<b>|</b> <a href="../DnsResolver#Root_Servers">Root Servers</a>
     53<b>|</b> <a href="../DnsResolver#Root_Operators">Root Operators</a>
     54<b>|</b> <a href="../DnsResolver#Root_Managers">Root Managers</a>
     55<b>|</b> <a href="../DnsResolver#gTLDs">gTLDs</a>
     56<b>|</b> <a href="../DnsResolver#ccTLDs">ccTLDs</a>
     57<b>|</b> <a href="../DnsResolver/PublicDnsResolvers">Public DNS Servers</a>
     58<b>|</b> <a href="../DnsResolver#Deadwood">Deadwood DNS Server</a>
     59<b>|</b> <a href="../DnsResolver/maraDeadwoodDns">Deadwood Configuration</a>
     60<b>|</b> <a href="../DnsResolver#Deadwood">MaraDNS DNS Server</a>
     61<b>|</b> <a href="../DnsResolver#Unbound">Unbound DNS Server</a>
     62<b>|</b> <a href="../DnsResolver/unbound">Unbound Configuration</a>
     63<b>|</b> <a href="../DnsResolver#BIND">BIND DNS Server</a>
     64<b>|</b> <a href="../DnsResolver#TLD_Providers">TLD Providers</a>
     65<b>|</b> <a href="../DnsResolver#Alt_Root_Operators">Alternative Root Operators</a>
     66<b>|</b>
    3167</td></tr></table><br />
    3268}}}
    3369
    34 
    3570{{{
    3671#!html
     
    3873}}}
    3974= DNS Test or Diagnostic Tools =
    40 Make sure DNS testing utility/tool software folder locations are included inside 'PATH' system variable/container, so that, testing utility software can be used under any directory inside the 'Command Prompt' like console windows.
     75Make sure [wiki:doc/DnsResolver#DNS DNS] testing utility/tool software folder locations are included inside 'PATH' system variable/container, so that, testing utility software can be used under any directory inside the 'Command Prompt' like console windows.
    4176
    4277Goto DNS test related tool, utility, font, software modification, etc section: [[#Console Command Prompt]], [[#ConEmu ConEmu]], [[#ping ping]], [[#NSLookup NSLookup]], [[#DiG DiG]], [[#DiG_with_Unicode_Support DiG (with Unicode support)]], [[#Wireshark Wireshark]], [[#Using_Unicode Using Unicode]], [[#Load_Unicode_Font Load Unicode Font]].
     
    213248{{{
    214249#!html
    215 <a name="Add_DiG_in_PATH"></a>
    216 }}}
    217 Add DiG in PATH: One of the simple way to get 'dig' (domain information groper) on Windows would be: goto BIND server developer ISC site (https://www.isc.org/), get BIND for Windows (filename may or may not be closer to 'BINDn.n.n-Pn.zip', where n is 0~9 digit, and match provided signature file (using GnuPG) if you have right zip file or not). Decompress it. Copy all files except the 'named.exe', (or, copy at least these files: 'dig.exe', 'dig.html', 'bindevt.dll', 'libdns.dll', 'libeay32.dll', 'libisc.dll', 'libisccfg.dll', 'liblwres.dll', 'libbind9.dll' into inside C:\dig folder, (change C: to your windows drive where you installed Windows). Add path C:\dig at the end of your system PATH environment variable, by adding ";C:\dig" at the end (without double quote symbols). Press and hold Windows Flag/Logo button on keyboard and then press '''R''' once, and let go both buttons. On 'Run' window, type: '''sysdm.cpl'''{{{⏎}}} and then goto 'Advanced' > 'Environment variables' > under the 'System variables' box, scroll down and find 'Path' and click on Path once > Edit > inside 'Variable value:' textbox go at the end (by pressing right arrow button or 'End' button) and then type: ''';C:\dig''' and then press on OK button > OK > OK. To see folder locations list inside PATH, in Command Promt, type: '''echo %PATH%'''
     250<a name="Get_DiG"></a><a name="Add_DiG_in_PATH"></a>
     251}}}
     252Get DiG and Add DiG in PATH: One of the simple way to get 'dig' (domain information groper) on Windows would be: goto BIND server developer ISC site (https://www.isc.org/), get BIND for Windows (filename may or may not be closer to 'BINDn.n.n-Pn.zip', where n is 0~9 digit, and match provided signature file (using GnuPG) if you have right zip file or not). Decompress it. Copy all files except the 'named.exe', (or, copy at least these files: 'dig.exe', 'dig.html', 'bindevt.dll', 'libdns.dll', 'libeay32.dll', 'libisc.dll', 'libisccfg.dll', 'liblwres.dll', 'libbind9.dll' into inside C:\dig folder, (change C: to your windows drive where you installed Windows). Add path C:\dig at the end of your system PATH environment variable, by adding ";C:\dig" at the end (without double quote symbols). Press and hold Windows Flag/Logo button on keyboard and then press '''R''' once, and let go both buttons. On 'Run' window, type: '''sysdm.cpl'''{{{⏎}}} and then goto 'Advanced' > 'Environment variables' > under the 'System variables' box, scroll down and find 'Path' and click on Path once > Edit > inside 'Variable value:' textbox go at the end (by pressing right arrow button or 'End' button) and then type: ''';C:\dig''' and then press on OK button > OK > OK. To see folder locations list inside PATH, in Command Promt, type: '''echo %PATH%'''
    218253
    219254{{{
     
    723758   The bold faced TLD '''中国.''' in above result box will be changed into '''xn--fiqs8s.''' (and the '''id''' value will also change) when you will try above command's punycode equivalent like this '''{{{dig  xn--fiqs8s.  any  +dnssec}}}''' in dig command-line.  If punycode form works and Unicode form does not, then you are not using a 'dig' capable of processing Unicode conversion.
    724759
    725  * Windows, by default refuses to resolve numeric TLD (it means, Windows refuses to resolve domain-names which has .N at end, here N is a numeric digit). If you will be using such a TLD which has numbers/digits, only then follow below step:[[BR]][[BR]]
     760{{{
     761#!html
     762<a name="TLD_IDN_Numeric"></a>
     763}}}
     764 * Use TLDs, IDNs Which Has Numeric Digits: Windows, by default refuses to resolve numeric TLD (it means, Windows refuses to resolve domain-names which has .N at end, here N is a numeric digit). If you will be using such a TLD which has numbers/digits, only then follow below step:[[BR]][[BR]]
    726765  * Click on "Start" menu, then in "Run" or "Execute" (of Windows XP) or in "Search" (of Windows Vista/Seven/7/8), type '''regedit''' and press {{{⏎}}}('Enter'). Goto/browse to this below registry location, and click on 'Parameters' in left side/pane:
    727766{{{
     
    753792 * Everytime you restart DNS resolver, you may also have to restart your web-browser, email-client software to be sure those are not using older mis-configured values.
    754793
    755  * When you have enabled using TCP traffic for resolving DNS in DNS Server/Resolver, then, or when you want to force 'dig' to use TCP DNS instead of default UDP DNS, then, in 'dig' command-line add ''' +tcp''' option at the end.
    756 
    757  * If you want to query for DNS info using 'dig' tool via using a very specific DNS/nameserver, then you can do so, by specifying that DNS/nameserver's ip address or hostname right after the 'dig' word in command-line and by using a leading '@' (at) symbol in front of the nameserver. Few examples:
     794{{{
     795#!html
     796<a name="Test_Via_TCP_DNS"></a>
     797}}}
     798 * Test Using TCP DNS Query: When you have enabled using TCP traffic for resolving DNS in DNS Server/Resolver, and When you want to force 'dig' to use TCP DNS (instead of default UDP DNS), then, in 'dig' command-line add ''' +tcp''' option at the end. See next section's example which uses +tcp option.  For this +tcp option to work successfully, you will have to pre-configure your DNS Server to allow TCP DNS query, see Unbound Tweak sections: [wiki:doc/DnsResolver#TCP_UDP_DNS this], and if you want to always connect with DNS/nameserver using TCP traffic, then configure your DNS Server further like [wiki:doc/DnsResolver#TCP_Only this].
     799
     800{{{
     801#!html
     802<a name="Test_Via_Specific_Nameserver"></a>
     803}}}
     804 * Test DNS Query On Specific DNS/Nameserver: If you want to query for DNS info using 'dig' tool via using a very specific DNS/nameserver, then you can do so, by specifying that DNS/nameserver's ip address or hostname right after the 'dig' word in command-line and by using a leading '@' (at) symbol in front of the nameserver. Few examples:
    758805{{{
    759806#!html