• 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.

Resolved DNS Settings

papahausa

Basic Pleskian
Server operating system version
AlmaLinux 8.6
Plesk version and microupdate number
18.0.45
dns not wirking after a fresh install?

example my domain cloudhive.pro did not work and when i try ping this domain, show old ip.
also i have subdomain bill.cloudhive.pro, this domain have correct ip and have ping with new ip.
other did not work.

all domain recods is updated with a new ip.

ping cloudhive.pro
Pinging cloudhive.pro [65.21.73.156] (show old ip) with 32 bytes of data:
Request timed out.

subdomain works.

ping bill.cloudhive.pro
Pinging bill.cloudhive.pro [194.163.186.107] (new ip in panel )with 32 bytes of data:
Reply from 194.163.186.107: bytes=32 time=32ms TTL=53
Reply from 194.163.186.107: bytes=32 time=31ms TTL=53
Reply from 194.163.186.107: bytes=32 time=31ms TTL=53
 
Your domain cloudhive.pro uses the name servers:

Name Server: hive1.serverit.cloud
Name Server: hive2.serverit.cloud
Name Server: hive3.serverit.cloud
Name Server: hive4.serverit.cloud

These nameserves are reporting 65.21.73.156 as the A record for cloudhive.pro.

hive1.serverit.cloud which I assume is your server at 65.21.73.156 is not responding for DNS lookups or pings.
 
Hi! Will you provide any info what was the root cause of the issue and how it was solved? it could help other people who might face with similar issue in the future.
 
Back
Top