雑　談　専　用　ス　ッ　ド　レ　★　38

847 ：がんじゃ兄貴 ◆U18g7nxod6：2014/05/17(土) 11:49:02.16 ID:xmfwtR9v6

>>838
NSレコードに入ってるns[01/02].maido3.comをNTTec側のネームサーバでCNAMEかけたんだよ。
だからおかしくなった。
使えないのはログすら漁らずに脊椎反射で文句垂れる奴のことだろ。

ソース。

Let's talk with Jim-san in operate. ★31
http://qb5.2ch.net/test/read.cgi/operate/1398174370/265
265 ：動け動けウゴウゴ２ちゃんねる ：2014/04/23(水) 20:54:19.94 ID:1+xQMc+00
>>262
だから、

ns1.maido3.com. 300 IN CNAME ns1.nttec.com.
ns1.nttec.com. 300 IN A 206.223.144.254

これが原因だってばさ。CNAMEにせず、ns1.maido3.comにAで直接206.223.144.254を設定すれば
解決する筈。
後は、LAME delegationをなんとかした方がいいだろう。

http://qb5.2ch.net/test/read.cgi/operate/1398174370/305
305 ：Grape Ape ★ ：2014/04/23(水) 23:20:33.84 ID:???0
>>302
Trusting IIS to manage the dns for maido3.com was the big mistake. I pointed it at
ns1 ns2.nttec.com in a rush when I realized that ns1 ns2.maido3.com were not working
correctly anymore. Thank you for pointing out that CNAME is not appropriate for DNS
servers. However the updated versions of BIND seem to be ok with it. Previous versions
have problems with it. I recommend upgrading your BIND versions as soon as possible.
Many of the BIND security holes are fixed with the newest version.