mirror of
https://github.com/fergalmoran/DnsServer.git
synced 2025-12-22 09:29:50 +00:00
updated readme
This commit is contained in:
12
README.md
12
README.md
@@ -11,13 +11,11 @@
|
|||||||
<img src="https://technitium.com/dns/ScreenShot1.png" alt="Technitium DNS Server" />
|
<img src="https://technitium.com/dns/ScreenShot1.png" alt="Technitium DNS Server" />
|
||||||
</p>
|
</p>
|
||||||
|
|
||||||
Technitium DNS Server is an open source tool that can be used for self hosting a DNS server for privacy & security or, used for experimentation/testing by software developers on their computer. It works out-of-the-box with no or minimal configuration and provides a user friendly web console accessible using any web browser.
|
Technitium DNS Server is an open source authoritative as well as recursive DNS server that can be used for self hosting a DNS server for privacy & security. It works out-of-the-box with no or minimal configuration and provides a user friendly web console accessible using any modern web browser.
|
||||||
|
|
||||||
Nobody really bothers about domain name resolution since it works automatically behind the scenes and is complex to understand. Most computer software use the operating system's DNS resolver that usually query the configured ISP's DNS server using UDP protocol. This way works well for most people but, your ISP can see and control what website you can visit even when the website employ HTTPS security. Not only that, some ISPs can redirect, block or inject content into websites you visit even when you use a different DNS provider like Google DNS or Cloudflare DNS. Having Technitium DNS Server configured to use DNS-over-TLS or DNS-over-HTTPS forwarders, these privacy & security issues can be mitigated very effectively.
|
Nobody really bothers about domain name resolution since it works automatically behind the scenes and is complex to understand. Most computer software use the operating system's DNS resolver that usually query the configured ISP's DNS server using UDP protocol. This way works well for most people but, your ISP can see and control what website you can visit even when the website employ HTTPS security. Not only that, some ISPs can redirect, block or inject content into websites you visit even when you use a different DNS provider like Google DNS or Cloudflare DNS. Having Technitium DNS Server configured to use [DNS-over-TLS](https://en.wikipedia.org/wiki/DNS_over_TLS) or [DNS-over-HTTPS](https://en.wikipedia.org/wiki/DNS_over_HTTPS) forwarders, these privacy & security issues can be mitigated very effectively.
|
||||||
|
|
||||||
Developers regularly use the hosts file for configuring an IP address for a domain under testing. However, using the hosts file is cumbersome at times and can only be used to resolve domain name to an IP address. With a fully configurable DNS server running on your local machine, you can configure not just simple A records (for IP address) but, also configure other types of records like CNAME or MX etc. This allow you to have more control and power when you want to do testing that simulates the exact configuration that you have running on production.
|
Be it a home network or an organization's network, having a locally running DNS server gives you more insights into your network and helps to understand it better using the DNS logs and stats. It improves overall performance since most queries are served from the DNS cache making web sites load faster by not having to wait for frequent DNS resolutions. It also gives you an additional control over your network allowing you to block domain names network wide and also allows you to route your DNS traffic securely using encrypted DNS protocols.
|
||||||
|
|
||||||
Applications of using a locally hosted DNS server is limited only by the user's imagination!
|
|
||||||
|
|
||||||
# Features
|
# Features
|
||||||
- Works on Windows, Linux, macOS and Raspberry Pi.
|
- Works on Windows, Linux, macOS and Raspberry Pi.
|
||||||
@@ -30,8 +28,8 @@ Applications of using a locally hosted DNS server is limited only by the user's
|
|||||||
- Advance caching with features like serve stale, prefetching and auto prefetching.
|
- Advance caching with features like serve stale, prefetching and auto prefetching.
|
||||||
- Supports working as an authoritative as well as a recursive DNS server.
|
- Supports working as an authoritative as well as a recursive DNS server.
|
||||||
- CNAME cloaking feature to block domain names that resolve to CNAME which are blocked.
|
- CNAME cloaking feature to block domain names that resolve to CNAME which are blocked.
|
||||||
- QNAME minimization support in recursive resolver [draft-ietf-dnsop-rfc7816bis-04](https://tools.ietf.org/html/draft-ietf-dnsop-rfc7816bis-04).
|
- QNAME minimization support in recursive resolver [draft-ietf-dnsop-rfc7816bis-04](https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-rfc7816bis-04).
|
||||||
- QNAME randomization support for UDP transport protocol [draft-vixie-dnsext-dns0x20-00](https://tools.ietf.org/html/draft-vixie-dnsext-dns0x20-00).
|
- QNAME randomization support for UDP transport protocol [draft-vixie-dnsext-dns0x20-00](https://datatracker.ietf.org/doc/html/draft-vixie-dnsext-dns0x20-00).
|
||||||
- DNAME record [RFC 6672](https://datatracker.ietf.org/doc/html/rfc6672) support.
|
- DNAME record [RFC 6672](https://datatracker.ietf.org/doc/html/rfc6672) support.
|
||||||
- ANAME propriety record support to allow using CNAME like feature at zone apex.
|
- ANAME propriety record support to allow using CNAME like feature at zone apex.
|
||||||
- APP propriety record support that allows custom DNS Apps to directly handle DNS requests and return a custom DNS response based on any business logic.
|
- APP propriety record support that allows custom DNS Apps to directly handle DNS requests and return a custom DNS response based on any business logic.
|
||||||
|
|||||||
Reference in New Issue
Block a user