diff --git a/sources/tech/20180322 Simple Load Balancing with DNS on Linux.md b/sources/tech/20180322 Simple Load Balancing with DNS on Linux.md
deleted file mode 100644
index f08b67b6e7..0000000000
--- a/sources/tech/20180322 Simple Load Balancing with DNS on Linux.md	
+++ /dev/null
@@ -1,140 +0,0 @@
-Translating by qhwdw
-Simple Load Balancing with DNS on Linux
-======
-
-![](https://www.linux.com/sites/lcom/files/styles/rendered_file/public/american-robin-920.jpg?itok=_B_RRbfj)
-When you have server back ends built of multiple servers, such as clustered or mirrowed web or file servers, a load balancer provides a single point of entry. Large busy shops spend big money on high-end load balancers that perform a wide range of tasks: proxy, caching, health checks, SSL processing, configurable prioritization, traffic shaping, and lots more.
-
-But you don't want all that. You need a simple method for distributing workloads across all of your servers and providing a bit of failover and don't care whether it is perfectly efficient. DNS round-robin and subdomain delegation with round-robin provide two simple methods to achieve this.
-
-DNS round-robin is mapping multiple servers to the same hostname, so that when users visit foo.example.com multiple servers are available to handle their requests.
-
-Subdomain delegation with round-robin is useful when you have multiple subdomains or when your servers are geographically dispersed. You have a primary nameserver, and then your subdomains have their own nameservers. Your primary nameserver refers all subdomain requests to their own nameservers. This usually improves response times, as the DNS protocol will automatically look for the fastest links.
-
-### Round-Robin DNS
-
-Round-robin has nothing to do with robins. According to my favorite librarian, it was originally a French phrase, _ruban rond_ , or round ribbon. Way back in olden times, French government officials signed grievance petitions in non-hierarchical circular, wavy, or spoke patterns to conceal whoever originated the petition.
-
-Round-robin DNS is also non-hierarchical, a simple configuration that takes a list of servers and sends requests to each server in turn. It does not perform true load-balancing as it does not measure loads, and does no health checks, so if one of the servers is down, requests are still sent to that server. Its virtue lies in simplicity. If you have a little cluster of file or web servers and want to spread the load between them in the simplest way, then round-robin DNS is for you.
-
-All you do is create multiple A or AAAA records, mapping multiple servers to a single host name. This BIND example uses both IPv4 and IPv6 private address classes:
-```
-fileserv.example.com. IN A 172.16.10.10
-fileserv.example.com. IN A 172.16.10.11
-fileserv.example.com. IN A 172.16.10.12
-
-fileserv.example.com. IN AAAA fd02:faea:f561:8fa0:1::10
-fileserv.example.com. IN AAAA fd02:faea:f561:8fa0:1::11
-fileserv.example.com. IN AAAA fd02:faea:f561:8fa0:1::12
-
-```
-
-Dnsmasq uses _/etc/hosts_ for A and AAAA records:
-```
-172.16.1.10 fileserv fileserv.example.com
-172.16.1.11 fileserv fileserv.example.com
-172.16.1.12 fileserv fileserv.example.com
-fd02:faea:f561:8fa0:1::10 fileserv fileserv.example.com
-fd02:faea:f561:8fa0:1::11 fileserv fileserv.example.com
-fd02:faea:f561:8fa0:1::12 fileserv fileserv.example.com
-
-```
-
-Note that these examples are simplified, and there are multiple ways to resolve fully-qualified domain names, so please study up on configuring DNS.
-
-Use the `dig` command to check your work. Replace `ns.example.com` with your name server:
-```
-$ dig @ns.example.com fileserv A fileserv AAA
-
-```
-
-That should display both IPv4 and IPv6 round-robin records.
-
-### Subdomain Delegation and Round-Robin
-
-Subdomain delegation combined with round-robin is more work to set up, but it has some advantages. Use this when you have multiple subdomains or geographically-dispersed servers. Response times are often quicker, and a down server will not respond, so clients will not get hung up waiting for a reply. A short TTL, such as 60 seconds, helps this.
-
-This approach requires multiple name servers. In the simplest scenario, you have a primary name server and two subdomains, each with its own name server. Configure your round-robin entries on the subdomain servers, then configure the delegations on your primary server.
-
-In BIND on your primary name server, you'll need at least two additional configurations, a zone statement, and A/AAAA records in your zone data file. The delegation looks something like this on your primary name server:
-```
-ns1.sub.example.com. IN A 172.16.1.20
-ns1.sub.example.com. IN AAAA fd02:faea:f561:8fa0:1::20
-ns2.sub.example.com. IN A 172.16.1.21
-ns2.sub.example.com. IN AAA fd02:faea:f561:8fa0:1::21
-
-sub.example.com. IN NS ns1.sub.example.com.
-sub.example.com. IN NS ns2.sub.example.com.
-
-```
-
-Then each of the subdomain servers have their own zone files. The trick here is for each server to return its own IP address. The zone statement in `named.conf` is the same on both servers:
-```
-zone "sub.example.com" {
- type master;
- file "db.sub.example.com";
-};
-
-```
-
-Then the data files are the same, except that the A/AAAA records use the server's own IP address. The SOA (start of authority) refers to the primary name server:
-```
-; first subdomain name server
-$ORIGIN sub.example.com.
-$TTL 60
-sub.example.com IN SOA ns1.example.com. admin.example.com. (
- 2018123456 ; serial
- 3H ; refresh
- 15 ; retry
- 3600000 ; expire
-)
-
-sub.example.com. IN NS ns1.sub.example.com.
-sub.example.com. IN A 172.16.1.20
-ns1.sub.example.com. IN AAAA fd02:faea:f561:8fa0:1::20
-
-; second subdomain name server
-$ORIGIN sub.example.com.
-$TTL 60
-sub.example.com IN SOA ns1.example.com. admin.example.com. (
- 2018234567 ; serial
- 3H ; refresh
- 15 ; retry
- 3600000 ; expire
-)
-
-sub.example.com. IN NS ns1.sub.example.com.
-sub.example.com. IN A 172.16.1.21
-ns2.sub.example.com. IN AAAA fd02:faea:f561:8fa0:1::21
-
-```
-
-Next, make your round-robin entries on the subdomain name servers, and you're done. Now you have multiple name servers handling requests for your subdomains. Again, BIND is complex and has multiple ways to do the same thing, so your homework is to ensure that your configuration fits with the way you use it.
-
-Subdomain delegations are easier in Dnsmasq. On your primary server, add lines like this in `dnsmasq.conf` to point to the name servers for the subdomains:
-```
-server=/sub.example.com/172.16.1.20
-server=/sub.example.com/172.16.1.21
-server=/sub.example.com/fd02:faea:f561:8fa0:1::20
-server=/sub.example.com/fd02:faea:f561:8fa0:1::21
-
-```
-
-Then configure round-robin on the subdomain name servers in `/etc/hosts`.
-
-For way more details and help, refer to these resources:
-
-Learn more about Linux through the free ["Introduction to Linux" ][1]course from The Linux Foundation and edX.
-
---------------------------------------------------------------------------------
-
-via: https://www.linux.com/learn/intro-to-linux/2018/3/simple-load-balancing-dns-linux
-
-作者：[CARLA SCHRODER][a]
-译者：[译者ID](https://github.com/译者ID)
-校对：[校对者ID](https://github.com/校对者ID)
-
-本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
-
-[a]:https://www.linux.com/users/cschroder
-[1]:https://training.linuxfoundation.org/linux-courses/system-administration-training/introduction-to-linux
diff --git a/translated/tech/20180322 Simple Load Balancing with DNS on Linux.md b/translated/tech/20180322 Simple Load Balancing with DNS on Linux.md
new file mode 100644
index 0000000000..87f8863ec5
--- /dev/null
+++ b/translated/tech/20180322 Simple Load Balancing with DNS on Linux.md	
@@ -0,0 +1,139 @@
+在 Linux 上用 DNS 实现简单的负载均衡
+======
+
+![](https://www.linux.com/sites/lcom/files/styles/rendered_file/public/american-robin-920.jpg?itok=_B_RRbfj)
+如果你的后端服务器是由多台服务器构成的，比如集群化或者镜像的 Web 或者文件服务器，通过一个负载均衡器提供了单一的入口点。业务繁忙的大型电商花费大量的资金在高端负载均衡器上，用它来执行各种各样的任务：代理、缓存、状况检查、SSL 处理、可配置的优先级、流量整形等很多任务。
+
+但是你并不需要做那么多工作的负载均衡器。你需要的是一个跨服务器分发负载的简单方法，它能够提供故障切换，并且不太在意它是否高效和完美。DNS 轮询和使用轮询的子域委派是实现这个目标的两种简单方法。
+
+DNS 轮询是将多台服务器映射到同一个主机名上，当用户访问 `foo.example.com` 时多台服务器都可用于处理它们的请求，使用的就是这种方式。
+
+当你有多个子域或者你的服务器在地理上比较分散时，使用轮询的子域委派就比较有用。你有一个主域名服务器，而子域有它们自己的域名服务器。你的主域名服务器将所有的到子域的请求指向到它们自己的域名服务器上。这将提升响应时间，因为 DNS 协议会自动查找最快的链路。
+
+### DNS 轮询
+
+轮询和旅鸫鸟（robins）没有任何关系，据我喜欢的图书管理员说，它最初是一个法语短语，_`ruban rond`_、或者 `round ribbon`。很久以前，法国政府官员以不分级的圆形、波浪形、或者辐条形状去签署请愿书以掩盖请愿书的发起人。
+
+DNS 轮询也是不分级的，简单配置一个服务器列表，然后将请求转到每个服务器上。它并不做真正的负载均衡，因为它根本就不测量负载，也没有状况检查，因此如果一个服务器宕机，请求仍然会发送到那个宕机的服务器上。它的优点就是简单。如果你有一个小的文件或者 Web 服务器集群，想通过一个简单的方法在它们之间分散负载，那么 DNS 轮询很适合你。
+
+你所做的全部配置就是创建多条 A 或者 AAAA 记录，映射多台服务器到单个的主机名。这个 BIND 示例同时使用了 IPv4 和 IPv6 私有地址类：
+```
+fileserv.example.com. IN A 172.16.10.10
+fileserv.example.com. IN A 172.16.10.11
+fileserv.example.com. IN A 172.16.10.12
+
+fileserv.example.com. IN AAAA fd02:faea:f561:8fa0:1::10
+fileserv.example.com. IN AAAA fd02:faea:f561:8fa0:1::11
+fileserv.example.com. IN AAAA fd02:faea:f561:8fa0:1::12
+
+```
+
+Dnsmasq 在 _/etc/hosts_ 文件中保存 A 和 AAAA 记录：
+```
+172.16.1.10 fileserv fileserv.example.com
+172.16.1.11 fileserv fileserv.example.com
+172.16.1.12 fileserv fileserv.example.com
+fd02:faea:f561:8fa0:1::10 fileserv fileserv.example.com
+fd02:faea:f561:8fa0:1::11 fileserv fileserv.example.com
+fd02:faea:f561:8fa0:1::12 fileserv fileserv.example.com
+
+```
+
+请注意这些示例都是很简化的，解析完全合格域名有多种方法，因此，关于如何配置 DNS 请自行学习。
+
+使用 `dig` 命令去检查你的配置能否按预期工作。将 `ns.example.com` 替换为你的域名服务器：
+```
+$ dig @ns.example.com fileserv A fileserv AAA
+
+```
+
+它将同时显示出 IPv4 和 IPv6 的轮询记录。
+
+### 子域委派和轮询
+
+子域委派结合轮询要做的配置会更多，但是这样有一些好处。当你有多个子域或者地理位置比较分散的服务器时，就应该去使用它。它的响应时间更快，并且宕机的服务器不会去响应，因此客户端不会因为等待回复而被挂住。一个短的 TTL，比如 60 秒，就能帮你做到。
+
+这种方法需要多台域名服务器。在最简化的场景中，你需要一台主域名服务器和两个子域，每个子域都有它们自己的域名服务器。在子域服务器上配置你的轮询记录，然后在你的主域名服务器上配置委派。
+
+在主域名服务器上的 BIND 中，你至少需要两个额外的配置，一个区声明以及在区数据文件中的 A/AAAA 记录。主域名服务器中的委派应该像如下的内容：
+```
+ns1.sub.example.com. IN A 172.16.1.20
+ns1.sub.example.com. IN AAAA fd02:faea:f561:8fa0:1::20
+ns2.sub.example.com. IN A 172.16.1.21
+ns2.sub.example.com. IN AAA fd02:faea:f561:8fa0:1::21
+
+sub.example.com. IN NS ns1.sub.example.com.
+sub.example.com. IN NS ns2.sub.example.com.
+
+```
+
+接下来的每台子域服务器上有它们自己的区文件。在这里它的关键点是每个服务器去返回它**自己的** IP 地址。在 `named.conf` 中的区声明，所有的服务上都是一样的：
+```
+zone "sub.example.com" {
+ type master;
+ file "db.sub.example.com";
+};
+
+```
+
+然后数据文件也是相同的，除了那个 A/AAAA 记录使用的是各个服务器自己的 IP 地址。SOA 记录都指向到主域名服务器：
+```
+; first subdomain name server
+$ORIGIN sub.example.com.
+$TTL 60
+sub.example.com IN SOA ns1.example.com. admin.example.com. (
+ 2018123456 ; serial
+ 3H ; refresh
+ 15 ; retry
+ 3600000 ; expire
+)
+
+sub.example.com. IN NS ns1.sub.example.com.
+sub.example.com. IN A 172.16.1.20
+ns1.sub.example.com. IN AAAA fd02:faea:f561:8fa0:1::20
+
+; second subdomain name server
+$ORIGIN sub.example.com.
+$TTL 60
+sub.example.com IN SOA ns1.example.com. admin.example.com. (
+ 2018234567 ; serial
+ 3H ; refresh
+ 15 ; retry
+ 3600000 ; expire
+)
+
+sub.example.com. IN NS ns1.sub.example.com.
+sub.example.com. IN A 172.16.1.21
+ns2.sub.example.com. IN AAAA fd02:faea:f561:8fa0:1::21
+
+```
+
+接下来生成子域服务器上的轮询记录，方法和前面一样。现在你已经有了多个域名服务器来处理到你的子域的请求。再说一次，BIND 是很复杂的，做同一件事情它有多种方法，因此，给你留的家庭作业是找出适合你使用的最佳配置方法。
+
+在 Dnsmasq 中做子域委派很容易。在你的主域名服务器上的 `dnsmasq.conf` 文件中添加如下的行，去指向到子域的域名服务器：
+```
+server=/sub.example.com/172.16.1.20
+server=/sub.example.com/172.16.1.21
+server=/sub.example.com/fd02:faea:f561:8fa0:1::20
+server=/sub.example.com/fd02:faea:f561:8fa0:1::21
+
+```
+
+然后在子域的域名服务器上的 `/etc/hosts` 中配置轮询。
+
+获取配置方法的详细内容和帮助，请参考这些资源：~~（致校对：这里的资源链接全部丢失了！！）~~
+
+通过来自 Linux 基金会和 edX 的免费课程 ["Linux 入门" ][1] 学习更多 Linux 的知识。
+
+--------------------------------------------------------------------------------
+
+via: https://www.linux.com/learn/intro-to-linux/2018/3/simple-load-balancing-dns-linux
+
+作者：[CARLA SCHRODER][a]
+译者：[qhwdw](https://github.com/qhwdw)
+校对：[校对者ID](https://github.com/校对者ID)
+
+本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
+
+[a]:https://www.linux.com/users/cschroder
+[1]:https://training.linuxfoundation.org/linux-courses/system-administration-training/introduction-to-linux