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

DNS trouble. Plesk 8.0. Need help!

S

StarGazer

Guest
Plesk 8.0. FreeBSD 6.0. Thats my DNS settings:
1.gif

2.gif

3.gif

4.gif

Whats wrong with nameservers? Why it didnt work? :confused:
http://89.108.90.54 - its ok.
http://egate.ru - no :(
:( :confused:
 
Have you registered these 2 IP addresses with your registraar as nameservers? Just setting them up in your zone will not make them proper nameservers.
 
Originally posted by phoenixisp
Have you registered these 2 IP addresses with your registraar as nameservers? Just setting them up in your zone will not make them proper nameservers.

Yes of course. Its first what i did.

Now zone is delegated and everething cool. Delegated is overlong. Thanks.

But that error:
4.gif

still here. :(
 
Are you doing any sort of NAT or anything? Or is that IP the actual IP of the server? That can cause problems if you don't do it right. Your DNS seems right.. It seems your Apache configuration isn't right. If the IP in the apache configuration doesn't match your local machines address, whether that IP is public or private, it won't show the correct webpage using virtual hosting. Hopefully that sparks a few ideas for you.
 
Back
Top