• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

DNS problems on a home Plesk server

J

jbeevers

Guest
Hello:

I just set up a Windows Plesk 7.6 server at my home. It's not being used as a production server, just to run a few personal sites.

The problem I'm having is that the domains I've tried to set up are not resolving. Here's the setup:

1 static WAN IP from my ISP
1 home router running Nat and DHCP
- Port forwards: 21, 25, 80, 110, 443, 8443
Server has internal IP (192.168.x.x) which Plesk is using
Windows Firewall is turned off

I registered ns1.domain.com with one of my domains using my WAN IP and pointed domains to that without success. I get the same result if I change the domain's DNS template in Plesk to use the WAN IP instead of the internal IP.

If I use ZoneEdit, I can get them to resolve. But there's got to be a way to get around having to use ZoneEdit (and having to pay for it). If anyone has done this before and knows how to get it working I'd really appreciate some direction. Thanks!
 
Back
Top