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

Problem with DNS outside of network -- HELP!!

R

rqsweat

Guest
I have a single domain. My problem is that I can hit the webpage for the domain just fine when I enter the URL on ANY of my servers on the same network. However, if I try to hit the domainaname from outside my network, I get the default Plesk page.

My server is behind a firewall and is NAT'ed. I've asked my ISP to enablt tcp on ports 21,22,53,80,443, and 8443. Do you think that port 53 UDP would cause the issue above? IS tthere any other reason why this would happen? Am I missing anything?

Please help me.I've been going at this for 2 days straight with no sleep. I even go myself a new server and migrated from Plesk on Windows to Plesk on Linux.
 
You must log in or register to reply here.

Similar threads

Azurel
Question Could someone share their "ss -tulpn" output from AlmaLinux 9?
Replies
6
Views
2K
Azurel
Azurel
Fahad009
Resolved Plesk DNS not responding externally – Registrar says nameserver did not respond (Windows Server)
Replies
8
Views
9K
Fahad009
Fahad009
M
Resolved Forward-confirmed reverse DNS failed tnmpmscs
Replies
8
Views
685
Kaspar
K
first4it
Issue Docker containers unable to resolve DNS or access external network on Plesk Obsidian 18.0.76 Update #4 (Collabora / Nextcloud issue)
Replies
2
Views
5K
first4it
first4it
bigbear67
Question Network routing issue after update (loss of default route source IP / DNS failure on Ubuntu 24.04)
Replies
0
Views
1K
bigbear67
bigbear67
Back
Top