Skip to content

Commit 475427e

Browse files
bene2k1nerda-codes
andauthored
feat(tutorial): content refresh tutorials (#3994)
* feat(tutorial): content refresh tutorials * Update tutorials/deploy-angular-application/index.mdx * fix(gen): typo * Apply suggestions from code review Co-authored-by: nerda-codes <[email protected]> --------- Co-authored-by: nerda-codes <[email protected]>
1 parent db3572b commit 475427e

File tree

19 files changed

+426
-449
lines changed

19 files changed

+426
-449
lines changed

tutorials/abort-multipart-upload-minio/index.mdx

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -9,12 +9,10 @@ tags: minio multipart-uploads
99
categories:
1010
- object-storage
1111
dates:
12-
validation: 2024-05-13
12+
validation: 2024-11-18
1313
hero: assets/scaleway_minio.webp
1414
---
1515

16-
## Object Storage - Multipart Upload Overview
17-
1816
[Multipart Uploads](/storage/object/api-cli/multipart-uploads/) allows you to upload large files (up to 5 TB) to the Object Storage platform in multiple parts. This allows faster, more flexible uploads.
1917

2018
If you do not complete a multipart upload, all the uploaded parts will still be stored and counted as part of your storage usage. Multipart uploads can be aborted manually [via the API and CLI](/storage/object/api-cli/multipart-uploads/#aborting-a-multipart-upload) or automatically using a [Lifecycle rule](/storage/object/api-cli/lifecycle-rules-api/#setting-rules-for-incomplete-multipart-uploads).

tutorials/backup-synology-nas-s3-hyper-backup/index.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ categories:
1010
tags: synology backup hyperbackup nas
1111
hero: assets/scaleway-hyper-backup.webp
1212
dates:
13-
validation: 2024-05-13
13+
validation: 2024-11-18
1414
posted: 2019-12-03
1515
---
1616

tutorials/bind-dns-server/index.mdx

Lines changed: 93 additions & 54 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ tags: dns bind
99
categories:
1010
- domains-and-dns
1111
dates:
12-
validation: 2024-05-13
12+
validation: 2024-11-18
1313
posted: 2018-12-05
1414
---
1515

@@ -26,12 +26,21 @@ DNS (Domain Name System) is a service that translates the IP address of computer
2626

2727
## Installing BIND
2828

29-
Install BIND and its related tools.
29+
1. Install the latest version of BIND 9.20 and related tools:
3030
```
3131
apt-get install bind9 bind9utils bind9-doc dnsutils
3232
```
33+
2. Verify the installed version:
34+
```
35+
named -v
36+
```
37+
The expected output should be:
38+
```
39+
BIN 9.20.x
40+
```
41+
3342

34-
## Configuring BIND on the primary Instance
43+
## Configuring the primary DNS server
3544

3645
1. Edit the `name.conf.local` file:
3746
```
@@ -48,52 +57,61 @@ Install BIND and its related tools.
4857
// organization
4958
//include "/etc/bind/zones.rfc1918";
5059
51-
zone "scw-domain.ml" IN {
52-
type master;
53-
file "/etc/bind/db.scw-domain.ml";
54-
allow-update { 51.15.250.21; };
55-
allow-transfer { 51.15.250.21; };
56-
notify yes;
57-
};
60+
zone "example.com" IN {
61+
type master;
62+
file "/etc/bind/db.example.com";
63+
allow-update { 192.0.2.2; };
64+
allow-transfer { 192.0.2.2; };
65+
notify yes;
66+
};
5867
```
5968
3. Create your zone file. A zone file must contain at least an SOA, an NS, and an A record or CNAME.
6069
```
61-
nano db.scw-domain.ml
70+
sudo nano /etc/bind/db.example.com
6271
```
6372
4. Paste the following:
6473
```
65-
;
66-
; BIND data file for local loopback interface
67-
;
6874
$TTL 10800
69-
scw-domain.ml. IN SOA ns1.scw-domain.ml. admin.scw-domain.ml. (
70-
2018120615 ; Serial
71-
10800 ; Refresh
72-
3600 ; Retry
73-
2419200 ; Expire
74-
604800 ) ; Negative Cache TTL
75-
;
75+
@ IN SOA ns1.example.com. admin.example.com. (
76+
2024111801 ; Serial
77+
10800 ; Refresh
78+
3600 ; Retry
79+
604800 ; Expire
80+
86400 ) ; Negative Cache TTL
7681
77-
; Nameserver
82+
; Name servers
83+
@ IN NS ns1.example.com.
84+
@ IN NS ns2.example.com.
85+
86+
; A and AAAA records
87+
ns1 IN A 192.0.2.1
88+
ns2 IN A 192.0.2.2
89+
90+
; Example host
91+
www IN A 192.0.2.3
92+
www IN AAAA 2001:db8::1
93+
```
94+
95+
5. Enable DNSSEC (optional but recommended):
96+
```
97+
sudo dnssec-keygen -a RSASHA256 -b 2048 -n ZONE example.com
98+
sudo dnssec-signzone -o example.com /etc/bind/db.example.com-
99+
```
78100

79-
scw-domain.ml. IN NS ns1.scw-domain.ml.
80-
scw-domain.ml. IN NS ns2.scw-domain.ml.
81-
ns1 86400 IN A 51.15.242.21
82-
ns1 86400 IN AAAA 2001:bc8:4400:2c00::14:229
83-
ns2 86400 IN A 51.15.250.21
84-
ns2 86400 IN AAAA 2001:bc8:4400:2c00::2c:1f
85-
www 86400 IN A 51.15.242.21
86-
www 86400 IN AAAA 2001:bc8:4400:2c00::14:229
101+
6. Restart the BIND server:
102+
```
103+
systemctl restart bind9
87104
```
88105

89-
## Configuring Bind on the secondary Instance
106+
## Configuring the secondary DNS server
90107

91108
1. Edit the `name.conf.local` file:
92109
```
93110
cd /etc/bind
94111
nano named.conf.local
95112
```
96-
2. Paste the following:
113+
114+
2. Add the slave zone definition:
97115
```
98116
//
99117
// Do any local configuration here
@@ -102,34 +120,55 @@ Install BIND and its related tools.
102120
// Consider adding the 1918 zones here, if they are not used in your
103121
// organization
104122
//include "/etc/bind/zones.rfc1918";
105-
zone "scw-domain.ml" IN {
106-
type slave;
107-
file "/etc/bind/db.scw-domain.ml";
108-
masters { 51.15.242.21; };
109-
allow-transfer { none; };
110-
allow-notify { 127.0.0.1; 51.15.242.21; 51.15.250.21; 2001:bc8:4400:2c00::14:229; };
111-
};
123+
zone "example.com" IN {
124+
type slave;
125+
file "/etc/bind/db.example.com";
126+
masters { 192.0.2.1; };
127+
allow-transfer { none; };
128+
};
112129
```
113-
3. On the primary machine, restart the service to verify that the zone replication works properly.
130+
<Message type="note">
131+
Replace `example.com` and the IP address of your primary server.
132+
</Message>
133+
134+
3. Restart the BIND service.
114135
```
115136
service bind9 restart
116137
```
117138

118-
The following output displays in the syslog file of the secondary machine:
139+
### Testing the Configuration
140+
141+
1. Check the primary DNS server:
142+
```bash
143+
dig @192.0.2.1 www.example.com
144+
```
145+
146+
2. Verify the secondary DNS server:
147+
```bash
148+
dig @192.0.2.2 www.example.com
149+
```
150+
151+
Expected output for both:
152+
```
153+
;; ANSWER SECTION:
154+
www.example.com. 86400 IN A 192.0.2.3
155+
```
156+
157+
3. Test zone replication:
158+
Restart the primary DNS server and check the logs on the secondary server:
159+
```bash
160+
sudo tail -f /var/log/syslog
161+
```
162+
163+
## Security and best Practices
164+
165+
- Use `allow-transfer` and `allow-update` directives to limit who can query or modify your DNS zones.
166+
- Sign your zones using DNSSEC to protect against DNS spoofing and man-in-the-middle attacks.
167+
- Use `rndc` or log analysis tools to monitor DNS queries and server performance.
119168

120-
```
121-
tail /var/log/syslog
122169

123-
Jan 11 17:24:22 bind-client named[11492]: client @0x7fa0d00c7260 51.15.242.21#42782: received notify for zone 'scw-domain.ml'
124-
Jan 11 17:24:22 bind-client named[11492]: zone scw-domain.ml/IN: notify from 51.15.242.21#42782: zone is up to date
125-
Jan 11 17:24:22 bind-client named[11492]: client @0x7fa0d003b900 2001:bc8:4400:2c00::14:229#53121: received notify for zone 'scw-domain.ml'
126-
Jan 11 17:24:22 bind-client named[11492]: zone scw-domain.ml/IN: notify from 2001:bc8:4400:2c00::14:229#53121: zone is up to date
127-
```
170+
## Conclusion
128171

129-
You can try to resolve hostnames on both servers by typing `dig www.scw-domain.ml @ns1.scw-domain.ml` & `dig www.scw-domain.ml @ns2.scw-domain.ml`
172+
You have successfully configured a DNS server using BIND 9.20. You can now resolve domain names within your infrastructure or serve DNS queries to external clients.
130173

131-
You should see in the answer section the following:
132-
```
133-
;; ANSWER SECTION:
134-
www.scw-domain.ml. 86400 IN A 51.15.242.21
135-
```
174+
For more advanced configurations and features, refer to the [official BIND 9.20 documentation](https://kb.isc.org/docs/isc-bind-9).

0 commit comments

Comments
 (0)