cadey/xesite
cadey
/
xesite
1
0
Fork 1
Code Issues Pull Requests 1 Projects Releases Wiki Activity

fixups

This commit is contained in:
Cadey Ratio 2019-04-07 14:37:13 -07:00
parent f2bda6c240
commit 406b8c265f
2 changed files with 21 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
blog/site-to-site-wireguard-part-1-2019-04-02.markdown
View File

@ -9,10 +9,10 @@ In this blogpost series I'm going to go over how I created a [site to site](http
This series is going to be broken up into multiple posts about as follows: This series is going to be broken up into multiple posts about as follows:
- Base core network setup and naming (this post) - Part 1 - Names and Numbers (this post)
- Setting up DNS (including reverse DNS) and custom endpoints - [Part 2 - DNS](https://christine.website/blog/site-to-site-wireguard-part-2-2019-04-07)
- Setting up a custom TLS Certificate Authority - Setting up a custom TLS Certificate Authority
- Setting up iOS, macOS, Android and Linux clients - Setting up additional iOS, macOS, Android and Linux clients
- Other future fun things (seamless tor2web routing, etc) - Other future fun things (seamless tor2web routing, etc)
By the end of this series you should be able to: By the end of this series you should be able to:

21
blog/site-to-site-wireguard-part-2-2019-04-07.markdown
View File

@ -8,12 +8,27 @@ date: 2019-04-07
This is the second in my Site to Site WireGuard VPN series. You can read the other articles here: This is the second in my Site to Site WireGuard VPN series. You can read the other articles here:
- [Part 1 - Names and Numbers](https://christine.website/blog/site-to-site-wireguard-part-1-2019-04-02) - [Part 1 - Names and Numbers](https://christine.website/blog/site-to-site-wireguard-part-1-2019-04-02)
- Part 2 - DNS (this post)
<!-- TODO(Xe): update the title of part 1 --> - Setting up a custom TLS Certificate Authority
- Setting up additional iOS, macOS, Android and Linux clients
## What is DNS and How Does it Work? ## What is DNS and How Does it Work?
DNS, or the [Domain Name Service](https://en.wikipedia.org/wiki/Domain_Name_System) is one of the core protocols of the internet. Its main job is to turn names like `google.com` into IP addresses for the lower layers of the networking stack to communicate. As an example of it in action, let's look up `google.com` with the `dig` tool (edited for clarity): DNS, or the [Domain Name Service](https://en.wikipedia.org/wiki/Domain_Name_System) is one of the core protocols of the internet. Its main job is to turn names like `google.com` into IP addresses for the lower layers of the networking stack to communicate. Semantically, clients ask questions to the DNS server (such as "what is the IP address for google.com") and get answers back ("the IP address for Google.com is 172.217.7.206"). This is a very simple protocol that predates the internet, and is tied into the core of nearly how every single program accesses the internet in some way or another. DNS allows users to not have to memorize IP addresses of services in order to connect to and use them. If anything on the internet is truly considered "infrastructure", it is DNS.
A common tool in Linux and macOS to query DNS is [`dig`](https://www.cyberciti.biz/faq/linux-unix-dig-command-examples-usage-syntax/). You can install it in Ubuntu with the following command:
```console
$ sudo apt install -y dnsutils
```
A side note for [Alpine Linux](https://alpinelinux.org) users: for some reason the `dig` tool is not packaged in Alpine. Instead you will need to use the basically identical `drill` tool. You can install it like this:
```console
# apk add drill
```
As an example of it in action, let's look up `google.com` with the `dig` tool (edited for clarity):
```console ```console
$ dig google.com $ dig google.com