• 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 Howto Help Needed

D

dbbotha

Guest
Some advice would be really appreciated

Current setup is
Plesk on Suse 10.2 server behind a pfSense firewall
Server on DMZ address 192.168.3.50
defassa.net 196.212.23.26 registered with Godaddy NATed on firewall to 192.168.3.50
ns1.defassa.net 196.212.23.29 registered with Godaddy NATed on firewall to 192.168.3.50 (port 53)
ns2.defassa.net 196.212.23.28 registered with Godaddy NATed on firewall to 192.168.3.50 (port 53)

Problem Statement
Can load domain default page if 196.212.23.26 is used but takes forever to load!
Cannot load domain default page if www.defassa.net is used (server not found error)
Im sure it is DNS related but would appreciate some Howto help in setting this all up.
A sample defassa.net DNS setup would be most welcome!

Thanks in advance
David
 
First you shouldnt have both name servers on the same physical machine, thats no good. You should have them in seperate machines in different data centers if at all possible to have better redundancy.

If the page loads its most likely not a dns issue, although the second one not loading is a dns issue since there is most likely no domain setup to use the second IP - which is fine, there really isnt a need to unless you want to use a ssl cert on the IP or something like that.
 
Back
Top