• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Hello need help with the domain and dns

Are you sure that your nameservers works fine?

[root@pvclinux64 ~]# telnet 162.220.242.229 53
Trying 162.220.242.229...
telnet: connect to address 162.220.242.229: No route to host
[root@pvclinux64 ~]# telnet 162.220.242.23 53
Trying 162.220.242.23...
telnet: connect to address 162.220.242.23: No route to host
[root@pvclinux64 ~]# host ns1.sayadns.com
Host ns1.sayadns.com not found: 2(SERVFAIL)
[root@pvclinux64 ~]# host ns2.sayadns.com
Host ns2.sayadns.com not found: 2(SERVFAIL)
[root@pvclinux64 ~]# host sayadns.com
Host sayadns.com not found: 2(SERVFAIL)
 
Make sure at least that named is started on these nameservers and port 53 is opened and not firewalled.
 
I can't reach 53 port:

$ telnet 162.220.242.23 53
Trying 162.220.242.23...
telnet: connect to address 162.220.242.23: No route to host
 
Back
Top