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

A second look please

G

G4 Hosting

Guest
DNS Setup: A second look please

Need a second look at my DNS setup, just to make sure I've got it right. Using Plesk 8.2 for Windows and first time with a Windows server. The server was setup last Wednesday, the 21 and configured Plesk on the sameday. Made some changes today after reading some more docs and the forums.

I'm thinking it just may be a propagation period but not sure since it's been 72 hours (there about's). In any case, doesn't hurt to have some else to take a look at this setup; a second pair of eyes if you will and to boost my confidence :).

Here's my setup:

mydomainhosted.com.<domain>. NS mydomainhosted.com.
mail.mydomainhosted.com.<domain>. A 75.125.242.91
mssql.mydomainhosted.com.<domain>. A 75.125.242.91
mydomainhosted.com.<domain>. A 75.125.242.91
ns1.mydomainhosted.com.<domain>. A 75.125.242.91
ns2.mydomainhosted.com.<domain>. A 75.125.242.92
webmail.mydomainhosted.com.<domain>. A 75.125.242.91
ftp.mydomainhosted.com.<domain>. CNAME mydomainhosted.com.
mydomainhosted.com.<domain>. MX (10) mydomainhosted.com.
75.125.242.91 / 24 PTR mydomainhosted.com.<domain>.

In my registrar, I have my settings as follows:

ns1.mydomainhosted.com - 75.125.242.91
ns2.mydomainhosted.com - 75.125.242.92

And I've setup the domain to point to those IP address. And what's even more disburbing is I can FTP via the IP address into the domain however the browser is unable to find the site (http or IP).

Is there something I’m missing? Apprecaite any feedback.

Thanks,
Rolly
 
Your dns setting is totally wrong,

It should be exactly like the format below:

<domain>. NS ns1.mydomainhosted.com.
<domain>. NS ns2.mydomainhosted.com.
<domain>. NS ns.<domain>.
<domain>. A <ip>
<domain>. MX (10) mail.<domain>.
<ip> / 24 PTR <domain>.
ftp.<domain>. CNAME <domain>.
mail.<domain>. A <ip>
mssql.<domain>. A <ip>
ns.<domain>. A <ip>
sitebuilder.<domain>. A <ip>
webmail.<domain>. A <ip>
 
Thanks! Made the changes and will wait(?) for it to propagate.
 
Still having problems with this windows server. According to dnsstuff.com I have a lameserver and no SOA records. I am sure that I've missed a step somewhere. I have the records down exactly as kami has it. Does the order on which it appears be any concern?

Any help is appreciated.

Thanks,
Rolly
 
Does DNSStuff point to nameservers which have your Plesk server IP?
John S.G.
 
Funny thing - I switch the server within Plesk from a master to a slave and everything came to life. Then I switched it back to master and haven't had a problem since. Last time I checked DNSstuff.com, there were some minor errors that I need to take care of.

Thanks for helping out.

Rolly
 
Back
Top