On Wed, Sep 12, 2018 at 5:49 AM BARAJAS BERMEJO, Sergio < sergio.bara...@econocom.com> wrote:
> Hello, > I have an issue configuring delegated subdomain zone from one NS to > another one. > For security reasons I will obviously not put real domain data (I imagine > you will understand). > > Let's suppose that the delegated subdomain is: > midominio.principal.hosting.com > If we make a "dig" query, putting the hosting server's NS as the domain > name server: > > > > > > > > > > > > > > > > > > > > > > > > > > > > *dig @ns1.hosting.com <http://ns1.hosting.com> > midominio.principal.hosting.com <http://midominio.principal.hosting.com> ; > <<>> DiG 9.10.3-P4-Debian <<>> @ns1.hosting.com <http://ns1.hosting.com> > midominio.principal.hosting.com <http://midominio.principal.hosting.com> ; > (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- > opcode: QUERY, status: NOERROR, id: 40831 ;; flags: qr rd; QUERY: 1, > ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 3 ;; WARNING: recursion requested but > not available ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 > ;; QUESTION SECTION: ;midominio.principal.hosting.com > <http://midominio.principal.hosting.com>. IN A ;; AUTHORITY SECTION: > midominio.principal.hosting.com <http://midominio.principal.hosting.com>. > 125 IN NS sb2.principal.hosting.com <http://sb2.principal.hosting.com>. > midominio.principal.hosting.com <http://midominio.principal.hosting.com>. > 125 IN NS sb1.principal.hosting.com <http://sb1.principal.hosting.com>. ;; > ADDITIONAL SECTION: sb1.principal.hosting.com > <http://sb1.principal.hosting.com>. 125 IN A xxx.xxx.xxx.52 > sb2.principal.hosting.com <http://sb2.principal.hosting.com>. 125 IN A > xxx.xxx.xxx.53 ;; Query time: 12 msec ;; SERVER: > 31.193.224.20#53(31.193.224.20) ;; WHEN: Wed Sep 12 08:09:36 CEST 2018 ;; > MSG SIZE rcvd: 133* > > From which we deduce several things: > > > 1. That in the zone principal.hosting.com of the main server of the > hosting there are created two registers of type A: > 1. > *sb1.principal.hosting.com <http://sb1.principal.hosting.com>. 125 IN A > xxx.xxx.xxx.52 sb2.principal.hosting.com > <http://sb2.principal.hosting.com>. 125 IN A xxx.xxx.xxx.53* > 2. That the authorized DNS servers on the subdomain > midominio.principal.hosting.com are: > *sb1.principal.hosting.com <http://sb1.principal.hosting.com>* y el > *sb2.principal.hosting.com > <http://sb2.principal.hosting.com>* > > Having said that, in my vps I have defined the following: > > > > > > > *; BIND reverse data file for empty rfc1918 zone ; ; DO NOT EDIT THIS FILE > - it is used for multiple zones. ; Instead, copy it, edit named.conf, and > use that copy. ; * > *$TTL 86400* > > *@ IN SOA sb1. sb2. mail. (* > The first field after "SOA" is the *ONE* master server for the domain. You cannot list two. Should be: @ IN SOA sb1. mail. ( -- Bob Harold > > > > > > > * 10 ; Serial 604800 ; Refresh 86400 ; Retry 2419200 ; Expire 86400 ) ; > Negative Cache TTL ; REGISTROS NS sb1.* > *principal.hosting.com <http://principal.hosting.com>. NS sb2.* > *principal.hosting.com <http://principal.hosting.com>. IN MX 10 mail.* > *midominio.principal.hosting.com <http://midominio.principal.hosting.com>. > sb1 IN A * > *xxx.xxx.xxx.52 sb2 IN A * > *xxx.xxx.xxx.53 www IN A * > *xxx.xxx.xxx.53 mail IN A * > > *xxx.xxx.xxx.53 webmail IN CNAME mail * IN A **xxx.xxx.xxx.53* > > > However I can not get it to solve for example > www.midominio.principal.hosting.com What am I doing wrong?. > Thank you very much in advance > > _______________________________________________ > Please visit https://lists.isc.org/mailman/listinfo/bind-users to > unsubscribe from this list > > bind-users mailing list > bind-users@lists.isc.org > https://lists.isc.org/mailman/listinfo/bind-users >
_______________________________________________ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
