Referencing by cname from one authoritative zone to another authoritative zone
Matus UHLAR - fantomas
uhlar at fantomas.sk
Thu Oct 3 09:49:40 UTC 2024
On 03.10.24 09:21, 大浦 義 wrote:
>・9.9.4→OK
># dig @ns1.bbb.co.jp time1.aaa.ne.jp
>;; ANSWER SECTION:
>time1.aaa.ne.jp. 3600 IN CNAME ns2.bbb.co.jp.
>ns2.bbb.co.jp. 900 IN A 1.2.3.5
>
>;; AUTHORITY SECTION:
>bbb.co.jp. 900 IN NS ns6-tk02.ccc.ad.jp.
>bbb.co.jp. 900 IN NS ns2.bbb.co.jp.
>bbb.co.jp. 900 IN NS ns1.bbb.co.jp.
>
>;; ADDITIONAL SECTION:
>ns1.bbb.co.jp. 900 IN A 1.2.3.4
>・9.18.28→NG
># dig @ns1-2024.bbb.co.jp time1.aaa.ne.jp
>;; ANSWER SECTION:
>time1.aaa.ne.jp. 3600 IN CNAME ns2.bbb.co.jp.
Now do:
dig @ns1-2024.bbb.co.jp ns2.bbb.co.jp.
what records does ns2.bbb.co.jp. have on ns1-2024.bbb.co.jp ?
>On 03.10.24 08:40, 大浦 義 wrote:
>>Referencing by cname from one authoritative zone to another authoritative zone may not work properly depending on the version.
>>Is this due to a specification change? Is there a way to handle this?
>>I am running nslookup from a client that is not included in acl respectively.
>>I would like to make the NG part become OK.
>>
>>--
>>One Server Has Two Zone.
>>aaa.ne.jp & bbb.co.jp
>>
>>・aaa.ne.jp
>>time1 CNAME ns2.bbb.co.jp.
>>time2 CNAME ns1.bbb.co.jp.
>>
>>・bbb.co.jp
>>ns1 A 1.2.3.4
>>ns2 A 1.2.3.5
>>time CNAME ns2
>>
>>・Bind9.9.4→OK
>>>nslookup time2.aaa.ne.jp
>>名前: ns1.bbb.co.jp
>>Address: 1.2.3.4
>>Aliases: time2.aaa.ne.jp
>>
>>・Bind9.18.28→NG
>>>nslookup time2.aaa.ne.jp
>>名前: ns1.bbb.co.jp
>
>nslookup is NOT a good tool to resolve DNS problems. Use "dig" instead.
>
>
>dig time2.aaa.ne.jp @"IP of Bind9.9.4"
>
>
>dig time2.aaa.ne.jp @"IP of Bind9.18.28"
--
Matus UHLAR - fantomas, uhlar at 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.
How does cat play with mouse? cat /dev/mouse
More information about the bind-users
mailing list