On 19/08/14 13:12, Bazy V wrote:
$ORIGIN 20.172.IN-ADDR.ARPA.
0.220/24 NS ns2.sub.test.com
On 19.08.14 13:37, Phil Mayers wrote:
You don't need to do this. You just need:
$ORIGIN 20.172.IN-ADDR.ARPA.
220 NS ns2.sub.test.com.
RFC 2317 is only need for /25 and longer.
... and it exactly causes the problem.
if ns2.sub.test.com contains 220.20.172.IN-ADDR.ARPA, resolution should
work the usual way.
Delegating 220/24.20.172.IN-ADDR.ARPA. to ns2.sub.test.com, you'd have to
create CNAMEs for 0.220/24 to 255.220/24, whic would be an overkill.
Note that either 0.220/24 wasn't technically correct, it should be:
220/24 NS ns2.sub.test.com.
0.220 CNAME 0.220/24
but that's an overkill as Phil correctly pointed out.
--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Microsoft dick is soft to do no harm
_______________________________________________
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
