You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: tutorials/abort-multipart-upload-minio/index.mdx
+1-3Lines changed: 1 addition & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,12 +9,10 @@ tags: minio multipart-uploads
9
9
categories:
10
10
- object-storage
11
11
dates:
12
-
validation: 2024-05-13
12
+
validation: 2024-11-18
13
13
hero: assets/scaleway_minio.webp
14
14
---
15
15
16
-
## Object Storage - Multipart Upload Overview
17
-
18
16
[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.
19
17
20
18
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).
3. On the primary machine, restart the service to verify that the zone replication works properly.
130
+
<Messagetype="note">
131
+
Replace `example.com` and the IP address of your primary server.
132
+
</Message>
133
+
134
+
3. Restart the BIND service.
114
135
```
115
136
service bind9 restart
116
137
```
117
138
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.
119
168
120
-
```
121
-
tail /var/log/syslog
122
169
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
128
171
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.
130
173
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