Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

By mechnotech
Please, help.
It is work. When I test it with dig, answer correct: [olegh@bsd ~]$ dig dns.emercoin.com NS ;; ANSWER SECTION: dns.emercoin.com. 1229 IN NS SEED2.emercoin.com. dns.emercoin.com. 1229 IN NS SEED1.emercoin.com.
If I ask for DNS-record directly from that server, it works, too:
[olegh@bsd ~]$ dig @SEED2.emercoin.com aaa.dns.emercoin.com ;; ANSWER SECTION: aaa.dns.emercoin.com. 4001 IN A 192.168.0.120 aaa.dns.emercoin.com. 4001 IN A 127.0.0.1
(answer IPs aren’t correct, this is for test only)
Thus, my custom DNS server works.
[olegh@bsd ~]$ dig aaa.dns.emercoin.com
; <<>> DiG 9.8.3-P4 <<>> aaa.dns.emercoin.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 50374 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION: ;aaa.dns.emercoin.com. IN A
;; AUTHORITY SECTION: dns.emercoin.com. 430 IN SOA SEED1.emercoin.com. hostmaster.dns.emercoin.com. 1411503131 3600 900 1209600 1800
;; Query time: 5 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Tue Sep 23 18:55:56 2014 ;; MSG SIZE rcvd: 91
Can you help me to understand, why DNS requests are not reached my name servers?