software:dns
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
software:dns [2012/12/03 15:57] – superwizard | software:dns [2015/07/19 19:35] – [DNS servers] superwizard | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== Check DNS settings ====== | ||
+ | |||
+ | named-checkconf / | ||
+ | named-checkzone (needs parameters) | ||
+ | |||
====== Benchmark dns ====== | ====== Benchmark dns ====== | ||
http:// | http:// | ||
+ | ====== DNS servers ====== | ||
+ | |||
+ | === Unbound === | ||
+ | |||
+ | From: https:// | ||
+ | |||
+ | < | ||
+ | Unbound is a validating, recursive, and caching DNS resolver. | ||
+ | On pfSense 2.2, Unbound has been integrated into the base system. Unbound is also the default | ||
+ | DNS Resolver for new installations. | ||
+ | </ | ||
+ | |||
+ | |||
+ | From: https:// | ||
+ | |||
+ | < | ||
+ | Unbound is a validating, recursive, and caching DNS resolver. | ||
+ | |||
+ | The C implementation of Unbound is developed and maintained by NLnet Labs. It is based on ideas | ||
+ | and algorithms taken from a java prototype developed by Verisign labs, Nominet, Kirei and ep.net. | ||
+ | |||
+ | Unbound is designed as a set of modular components, so that also DNSSEC (secure DNS) validation and | ||
+ | stub-resolvers (that do not run as a server, but are linked into an application) are easily possible. | ||
+ | |||
+ | The source code is under a BSD License. | ||
+ | </ | ||
+ | |||
+ | === PowerDNS === | ||
+ | |||
+ | From: https:// | ||
+ | |||
+ | < | ||
+ | Both the PowerDNS Authoritative and the PowerDNS Recursive Servers are available in source form, | ||
+ | as well as installable Linux Packages. PowerDNS is shipped with many Linux and UNIX distributions, | ||
+ | including Debian, FreeBSD, Gentoo, NetBSD, SUSE and Ubuntu. | ||
+ | Users of these distributions may find they already have a copy of PowerDNS available, often in | ||
+ | the package called pdns, powerdns-server, | ||
+ | </ | ||
+ | |||
+ | === Bind === | ||
+ | |||
+ | From: http:// | ||
+ | |||
+ | 4.2: Add a zone for the local domain: | ||
+ | zone " | ||
+ | type master; | ||
+ | file "/ | ||
+ | }; | ||
+ | 4.3: Also add a zone for reverse dns lookups for the local network: | ||
+ | zone " | ||
+ | type master; | ||
+ | file "/ | ||
+ | }; | ||
+ | |||
+ | === Dual DHCP DNS Server === | ||
+ | |||
+ | From: http:// | ||
+ | |||
+ | DHCP Server allots the IP addresses to computers, while DNS server resolves them. | ||
+ | You need DHCP Server if you do not want to manually maintain IP Addresses or you have less IP | ||
+ | Addresses than number of machines you have, as dynamic DHCP Server will recycle IP Addresses on | ||
+ | machines. | ||
+ | DNS Server is needed for resolving hostnames to their IP addresses. Normally your ISP will provide you | ||
+ | with DNS Service. You may have your own DNS Server, which will resolve hostnames by forwarding them to | ||
+ | ISP's DNS Server and cache the addresses also. | ||
+ | If you have home/small office network with Unix/Linux machines, these machines will not be resolved from | ||
+ | each other, as Unix/Linux machines do not support NBNS protocol and you need your own DNS Server. But how | ||
+ | about resolving your local machines ?. Your ISP's DNS Server will not have this list and your own DNS | ||
+ | | ||
+ | use static IP addresses and manually enter them). | ||
+ | |||
+ | ====== DNS at the local area network level ====== | ||
+ | |||
+ | From: http:// | ||
+ | |||
+ | I start setting the first AD/DC — the angular stone for our network. After setting up the operating systemincluding updates and SPs, it was decided the machine will be hosting the domain luckyeyes.local. | ||
+ | To start, I open the network card properties/ | ||
+ | with network mask 255.255.255.0, | ||
====== linux named ====== | ====== linux named ====== | ||
- | ====== HOWTO dump/export the cache of a BIND DNS server ====== | + | From: http:// |
+ | Using the form below, you can create a zone file for use with the BIND DNS server. | ||
- | From: http:// | + | ====== Linux bind Log Format ====== |
- | Last night I spent about an hour looking around google for how to dump and view the cache of a bind dns server. I just wanted to post this thread on how to do it so maybe next time people search they will able to find it easier | + | From: http:// |
- | Bind 9 makes it fairly easy to dump and view the cache of a caching BIND DNS server. All you have to do is run under root: | + | More complete description |
- | **rndc dumpdb | + | From: http:// |
- | This will create a file called | + | logging { |
+ | | ||
+ | file "/ | ||
+ | versions 3 size 100M; | ||
+ | print-time yes; // timestamp log entries | ||
+ | }; | ||
+ | |||
+ | | ||
+ | | ||
+ | }; | ||
+ | }; | ||
+ | |||
+ | |||
+ | |||
+ | ====== HOWTO dump/export the cache of a BIND DNS server ====== | ||
+ | |||
+ | From: http:// | ||
+ | |||
+ | **rndc dumpdb -zones** | ||
+ | |||
+ | | ||
+ | |||
+ | From: http://ubuntuforums.org/ | ||
- | ** If your instance of BIND is chrooted, | + | Last night I spent about an hour looking around google |
+ | I just wanted to post this thread on how to do it so maybe next time people search they will able to find it easier | ||
+ | Bind 9 makes it fairly easy to dump and view the cache of a caching BIND DNS server. All you have to do is run under root: | ||
+ | |||
+ | **rndc dumpdb -cache** | ||
- | ** The dumpdb feature of rndc has other options including | + | This will create |
+ | favorite text editor. | ||
- | For more information you can check out this HOWTO i drafted. | + | If your instance of BIND is chrooted, for example to / |
+ | located in the / | ||
+ | The dumpdb feature of rndc has other options including a -all or -zone flag. Check 'rndc --help' | ||
+ | for more information. For more information you can check out this HOWTO i drafted. | ||
software/dns.txt · Last modified: 2019/09/10 23:19 by superwizard