• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • 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.

DNS, NAT, and Plesk not playing nice.

A

artisticdigital

Guest
We are having a very hard time getting plesk up and running on our new dedicated server. I have tried everything that I can think of and we still unable to get it to work correctly. Here are the server details:

1 Blade with 4 nics:

Interface External Internal
eth2 69.13.120.81 10.0.0.50
eth3 69.13.120.82 10.0.0.51
eth0 69.13.120.83 10.0.0.52
eth1 69.13.120.84 10.0.0.53

We are running a SonicWall 2040 firewall and the above IP's are One to One Nat'ed to the internal ip's. The firewall is allowing all traffic and not blocking ports what so ever. I have setup are hostname for the server temporarily at jasmine.artisticdigital.com. We are moving all over clients over to this server. Our name servers are going to be ns1.adsincchicago.com - ns4.adsincchicago.com. As you can see from the DNS report, http://www.dnsstuff.com/tools/dnsreport.ch?domain=adsincchicago.com, the DNS seems to be working fine. I can even pull the domain adsincchicago.com if I force my machine to use our IP.

If you launch our IP's in a web browser your will see that only one of the IP's resolves and shows the plesk page. The others ip's seem to only show the default apache page
http://69.13.120.81
http://69.13.120.82
http://69.13.120.83
http://69.13.120.84

It takes for every to load at http://69.13.120.81...and it seems that is because the server is choking on newsfeed.js.php. It cannot load that page.

If you open http://adsincchicago.com that will load with the default Server Page.

I think the problem lies in the fact that when you try to access the domain from anything other then .81 which is really .50 is chokes because 10.0.0.50 is the only IP in the httpd.include.

I am out of idea and have tried everything in the forum, and in the knowledge base. I am positive that or domain is pointed correctly and that our custom name servers are setup.
 
Back
Top