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

Issue The domain resolves to the incorrect IP address...

madpugger

New Pleskian
Server operating system version
Ubuntu 20.04.6 LTS
Plesk version and microupdate number
18.0.57 Update #5,
Hi, and thanks for any assistance!
I've recently setup a couple of new domains and followed Ionos' instructions for using Plesk as the Nameserver. On all my other domains, I've just used Ionos for the DNS records but this is a bit tedious when using let's encrypt for example.
As far as I can tell, the DNS records in Plesk are correct, and the site is working as it should in safari - but sometimes in google, it tells me "This site can't be reached" and "Connection Reset". I am fairly certain this is to do with the company network I am accessing from for testing right now so not "too" concerned about this, but would like to understand why it works sometimes!

More concerning, is Plesk has a warning stating:
"Domain domainname.co.uk resolve problems detected:
The domain resolves to the incorrect IP address (217.160.0.112). To put your website online, correct DNS Settings."

Why would this be? The domain appears to work, the DNS records in Plesk appear to be correct and doing a DNS lookup seems ok too?

For those not familiar with Ionos, their instructions tell me to use NS1 as the VPS IP and NS2 as something like abcdefg.online-server.cloud. The abcdefg is presumably unique to my account.

TIA
Mike
 
Back
Top