ask - Nameservers are lame pada dns cluster

Discussion in 'Masalah Teknik dan Keamanan' started by procaster, 22 May 2014.

Thread Status:
Not open for further replies.
  1. procaster

    procaster Poster 1.0

    Messages:
    67
    Likes Received:
    10
    Trophy Points:
    8
    master2, mau sedikit tanya.. Kalo name server lame itu kira2 kenapa ya?

    saya coba buat dns cluster baru dengan typologi seperti gambar dibawah, tapi kenapa ns1 da ns2 selalu error (Nameservers are lame) tapi ns3 nya normal.
    padahal ns1-ns3 instalasi nya sama.. kira2 setingan apa yg salah ya?

    Ada yang pernah ngalami?
    thx

    [​IMG]
    ERROR: looks like you have lame nameservers. The following nameservers are lame:
    188.xxx.xxx.xxx
    167.xxx.xxx.xxx
     
  2. junior riau

    junior riau Hosting Guru Web Hosting

    Messages:
    3,230
    Likes Received:
    515
    Trophy Points:
    113
  3. procaster

    procaster Poster 1.0

    Messages:
    67
    Likes Received:
    10
    Trophy Points:
    8
    Dulunya saya setting begitu bos, tapi di sengaja di buat tangga justru untuk memper cepat resolve karena ada interface tambahan (bukan WHM) untuk add, edit dan set geodns di server ns.alamat**.com nya, jadi semua server whm cp hanya syncron write only ke ns private (ns.alamat**.com) baru di syncron ke ns public (ns1-3).
    yang jadi masalah kenapa muncul error lame padahal kalo di lihat di bind recordnya benar
     
  4. junior riau

    junior riau Hosting Guru Web Hosting

    Messages:
    3,230
    Likes Received:
    515
    Trophy Points:
    113
    saya ga pake model tangga sih, tetep seperti model saya itu, cepat kok resolvingnya
     
  5. procaster

    procaster Poster 1.0

    Messages:
    67
    Likes Received:
    10
    Trophy Points:
    8
    Thx pak sarannya, tapi saya rubah seperti model default ns1-2 nya tetap lame, sampai servernya di install ulang dan di reconfigure tetap sama :(
     
  6. gonggo

    gonggo Poster 1.0

    Messages:
    53
    Likes Received:
    6
    Trophy Points:
    8
    di basic whm setup, semua ns udah masuk?
     
  7. procaster

    procaster Poster 1.0

    Messages:
    67
    Likes Received:
    10
    Trophy Points:
    8
    sudah, setingan sudah benar,. sekarang curiga setingan firewall router server nya yang bermasalah,. ns2 di pindah lokaasi server sudah normal..
     
  8. junior riau

    junior riau Hosting Guru Web Hosting

    Messages:
    3,230
    Likes Received:
    515
    Trophy Points:
    113
    coba di cek lagi, allow2nya
    saya aman2 man aja,
     
  9. procaster

    procaster Poster 1.0

    Messages:
    67
    Likes Received:
    10
    Trophy Points:
    8
    iya Tuan @junior riau . UDAH SOLVE.. dan di set tangga lagi hehe
    Tadi konsultasi dengan data center bilang begini

    "Lame server basically means that it doesn't have information about your zone. However this is not the case with your ns1 and ns2 servers. As part of DDoS protection some of the packages are forwarded to TCP, but the checkers expect them to be over the UDP protocol and returns this error. There is nothing to worry about a replay is always returned and the job is done."

    Jadi masalahnya pada IP yang saya gunakan,
    Karena ke NS1 dan NS2 mengunakan IP DDOS Filtered,
    Jadi pada DDoS protection sebagian paket di forward ke TCP, sedangkan tools yg buat ngecek menganggap lwt UDP makanya terjadi mis komunikasi.
    Tapi NS tetap bekerja..

    Thx
     
  10. junior riau

    junior riau Hosting Guru Web Hosting

    Messages:
    3,230
    Likes Received:
    515
    Trophy Points:
    113
    ok sip, masalah pemakaian protocol berarti, yang forward protocol tcp, yang dipake buat ngecek make protocol udp
    sisip
     
Loading...
Thread Status:
Not open for further replies.

Share This Page

Loading...