Bathory, here is what you ask...
dig midominio.com @ns1.midominio.com
; <<>> DiG 9.9.5-9+deb8u9-Debian <<>> midominio.com @ns1.midominio.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 43297
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;midominio.com. IN A
;; AUTHORITY SECTION:
midominio.com. 3600 IN SOA ns1.midominio.com. root.ns1.midominio.com. 2017024005 3600 300 1209600 3600
;; Query time: 0 msec
;; SERVER: xxx.yyy.zzz.2#53(xxx.yyy.zzz.2)
;; WHEN: Wed Mar 01 16:24:17 ART 2017
;; MSG SIZE rcvd: 92
With nslookyp I get this...
root@ns1:/etc/bind# nslookup midominio.com
Server: xxx.yyy.zzz.2
Address: xxx.yyy.zzz.2#53
*** Can't find midominio.com: No answer
root@ns1:/etc/bind# nslookup
www.midominio.com
Server: xxx.yyy.zzz.2
Address: xxx.yyy.zzz.2#53
www.midominio.com canonical name = midominio.com.
I still have something wrong.
I change my named.conf.option file commenting forwarders and uncomment recursion like this...
options {
directory "/var/cache/bind";
// If there is a firewall between you and nameservers you want
// to talk to, you may need to fix the firewall to allow multiple
// ports to talk. See
http://www.kb.cert.org/vuls/id/800113
// If your ISP provided one or more IP addresses for stable
// nameservers, you probably want to use them as forwarders.
// Uncomment the following block, and insert the addresses replacing
// the all-0's placeholder.
// forwarders {
// 8.8.8.8;
// };
//========================================================================
// If BIND logs error messages about the root key being expired,
// you will need to update your keys. See
https://www.isc.org/bind-keys
//========================================================================
//dnssec-validation no;
recursion no;
auth-nxdomain no; # conform to RFC1035
allow-query { any; };
//listen-on-v6 { any; };
rate-limit {
responses-per-second 10;
// log-only yes; //comentar
};
};
But I get this error.... REFUSED
01-Mar-2017 16:35:39.662 query-errors: info: client aaa.bbb.ccc.123#17529 (clients4.google.com): rate limit drop REFUSED error response to aaa.bbb.ccc.0/24
01-Mar-2017 16:35:39.704 query-errors: info: client aaa.bbb.ccc.90#61512 (emupdate.avcdn.net): rate limit slip REFUSED error response to aaa.bbb.ccc.0/24
01-Mar-2017 16:35:39.837 query-errors: info: client aaa.bbb.ccc.130#14852 (
www.facebook.com): rate limit drop REFUSED error response to aaa.bbb.ccc.0/24
01-Mar-2017 16:35:39.906 query-errors: info: client aaa.bbb.ccc.16#24348 (graph2.facebook.com): rate limit slip REFUSED error response to aaa.bbb.ccc.0/24
01-Mar-2017 16:35:39.982 rate-limit: info: limit REFUSED error responses to 192.168.20.0/24
01-Mar-2017 16:35:39.982 query-errors: info: client 192.168.20.151#23499 (apis.google.com): rate limit slip REFUSED error response to 192.168.20.0/24
01-Mar-2017 16:35:40.160 query-errors: info: client aaa.bbb.ccc.130#14852 (
www.google.com.ar): rate limit drop REFUSED error response to aaa.bbb.ccc.0/24
01-Mar-2017 16:35:40.233 query-errors: info: client aaa.bbb.ccc.179#26182 (connectivitycheck.android.com): rate limit slip REFUSED error response to aaa.bbb.ccc.0/24
01-Mar-2017 16:35:40.238 query-errors: info: client aaa.bbb.ccc.179#26184 (connectivitycheck.android.com): rate limit drop REFUSED error response to aaa.bbb.ccc.0/24
01-Mar-2017 16:35:40.307 query-errors: info: client aaa.bbb.ccc.211#15764 (a.root-servers.net): rate limit slip REFUSED error response to aaa.bbb.ccc.0/24