The scenario:
- DNS zone
myzone.com
defined in BIND. - Authoritative name server at
123.16.123.1
. - Subzone
sub.myzone.com
with an authoritative name server at123.16.123.10
. - Wishing to forward sub-zone to authoritative name server.
$ORIGIN myzone.com.
$TTL 1D
@ IN SOA ns1.myzone.com. hostmaster.myzone.com. (
2015010100 ; serial
21600 ; refresh
3600 ; retry
604800 ; expire
86400 ) ; minimum TTL
;
@ IN NS ns1
ns1 IN A 123.16.123.1 ; glue record
ns1sub IN A 123.16.123.10 ; glue record
;
;
$ORIGIN sub.myzone.com.
$TTL 1D
@ IN NS ns1sub.myzone.com.
- Resolver asks for answer to
foo.sub.myzone.com
from name server. - Via
sub.myzone.com
zone, is given answer ofns1sub.myzone.com
as the authoritative name server. - Resolver able to resolve IP address of
123.16.123.10
forns1sub.myzone.com
via parent zone A "glue" record. - Now resend original query of
foo.sub.myzone.com
to nameserver server at123.16.123.10
. - All done.
~]# named-checkzone -D myzone.com /tmp/test
zone myzone.com/IN: loaded serial 2015010100
myzone.com. 86400 IN SOA ns1.myzone.com. hostmaster.myzone.com. 2015010100 21600 3600 604800 86400
myzone.com. 86400 IN NS ns1.myzone.com.
ns1.myzone.com. 86400 IN A 123.16.123.1
ns1sub.myzone.com. 86400 IN A 123.16.123.10
sub.myzone.com. 86400 IN NS ns1sub.myzone.com.
OK
[root@provider ~]#