commit ae8627e2a4af31d076d9142ff6ae7a5bb3d61f71 Author: zer Date: Sat Jul 6 21:02:43 2024 -0700 add diff --git a/DNS-header-Kelvin-Ang(background)BG-(Chads).jpg b/DNS-header-Kelvin-Ang(background)BG-(Chads).jpg new file mode 100644 index 0000000..39554c1 Binary files /dev/null and b/DNS-header-Kelvin-Ang(background)BG-(Chads).jpg differ diff --git a/README.md b/README.md new file mode 100644 index 0000000..2e33789 --- /dev/null +++ b/README.md @@ -0,0 +1,20 @@ +# DNS_Blog + +This is the supporting repo for the corresponding blog that can be found [here](https://bgsysadmin.site/posts/DNS/ "DNS") + + +![header](https://gitea-bg.site/zer/DNS_Blog/raw/branch/main/DNS-header-Kelvin-Ang%28background%29BG-%28Chads%29.jpg "(Kevin Ang Background Final edits by BG)") + +Today we are talking about *DNS*. The one and only, up there with, turning it off and on again. It's always *DNS*. The thing is, your *DNS* records can be wiped out without a second thought. By a team member, on a late-night development session, or even worse, your provider. + +Due to the recent news about *Cloudflare*, I decided to make my own *DNS* more secure and understand my options. You see, there are about 4 types of *DNS* providers. There are name server level providers. You can often get your *DNS* needs met in the same place you purchase your domain name, like *Namecheap*. + +This is just fine, and you should scale your needs due to ease of use. Not just what is popular at the time. You can use your *VPS*, like *DigitalOcean*. Often, you can use your *VPS* itself to serve up your *DNS*. This is also fine. It can be an easy way to go. These two options often leave you a little less protected. You may need to use your own proxies and any other external protection from *DDOS*, or just the use of firewalls in general. + +The next level would be something like *Cloudflare*. They do offer a lot of free services as of the time of writing this blog. Making them great for new users. Just make sure you keep an eye on the terms of service. Below, I have included an image of a way to download your *Cloudflare* *DNS*. If you are expanding rapidly or have a reason to safeguard your records, as a good system administrator, you should always be prepared. + +![image 01](https://gitea-bg.site/zer/DNS_Blog/raw/branch/main/bg-original-img.jpg "( BG original )") + +This can help you migrate to *DigitalOcean* or you can upgrade to something on *AWS* where the terms are very clear. To be very clear. *Cloudflare* has not done me wrong so far. But There are some stories going around that might alarm a buisness owner that depends on the *DNS* working, ALWAYS! Otherwise, what are we getting paid for. + +Here is a [Link](https://www.youtube.com/watch?v=6KHB2F8R4o8 "Theo - t3․gg YouTube Channel") to help you understand why having backups of your records will make redeployment that much faster. One way or another. You need control. Next time we will talk about the importance of backing up your SSL records. Till then, shore it up and cable down. \ No newline at end of file diff --git a/bg-original-img.jpg b/bg-original-img.jpg new file mode 100644 index 0000000..2912354 Binary files /dev/null and b/bg-original-img.jpg differ