• 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!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    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.

Fixing DNS

S

stevethemusicma

Guest
Hi All,

Here’s the scoop,

When I first got my dedicated server from my hosting service I was migrating from another server the name servers were ns1.Joedumb.net and ns2.Joedumb.net (also had ns3, ns4) all pointing to 2 different IP’s with the old provider.

When I got the new server I started with ns1.Joedumb.net and ns2.Joedumb.net and had the server DNS set like below:


<domain>. NS ns1.Joedumb.net.
<domain>. NS ns2.Joedumb.net.
<domain>. A <ip>
<domain>. MX (10) mail.<domain>.
<ip> / 24 PTR <domain>.
ftp.<domain>. CNAME <domain>.
mail.<domain>. A <ip>
ns.<domain>. A <ip>
webmail.<domain> A <ip>

Joedumb.net is setup like the following:
72.22.141.70 / 24 PTR Joedumb.net.
ftp.Joedumb.net. CNAME Joedumb.net.
mail.Joedumb.net. A 192.22.141.70
ns1.Joedumb.net. A 192.22.141.70
ns2.Joedumb.net. A 192.22.142.134
Joedumb.net. NS ns1.Joedumb.net.
Joedumb.net. NS ns2.Joedumb.net.
Joedumb.net. A 192.22.141.70
Joedumb.net. MX (10) mail.Joedumb.net.
webmail.Joedumb.net. A 192.22.141.70
www.Joedumb.net. CNAME Joedumb.net.

Once I migrated all of the domains over that were pointing to the JimOld.net old server I just changed the DNS at my registrar to point ns1, ns2, ns3, ns4.JimOld.net to the same 2 IP’s of Joedumb.net and set up JimOld.net as shown below:

72.22.141.70 / 24 PTR JimOld.net.
JimOld.net. NS ns1.Joedumb.net.
JimOld.net. NS ns2.Joedumb.net.
JimOld.net. A 192.22.141.70
JimOld.net. MX (10) mail.JimOld.net.
ftp.JimOld.net. CNAME JimOld.net.
mail.JimOld.net. A 192.22.141.70
ns1.JimOld.net. A 192.22.141.70
ns2.JimOld.net. A 192.22.142.134
ns3.JimOld.net. A 192.22.141.70
ns4.JimOld.net. A 192.22.142.134
ns5.JimOld.net. A 192.22.141.70
ns6.JimOld.net. A 192.22.142.134
webmail.JimOld.net. A 192.22.141.70
www.JimOld.net. CNAME JimOld.net.

Now that everything is migrated I want to assign an IP to JimOld.net as shown below:

Here’s my quandary. Now the domain JimOld.net is a shared IP with the name servers. I want to put it on it’s own IP so I can issue an SSL (which I already have). I’m getting another ip for this let say 192.22.141.143 for this domain. What do I need to do to make this work properly. Can I change it as follows and will it work properly?

72.22.141.143 / 24 PTR JimOld.net.
JimOld.net. NS ns1.Joedumb.net.
JimOld.net. NS ns2.Joedumb.net.
JimOld.net. A 192.22.141.143
JimOld.net. MX (10) mail.JimOld.net.
ftp.JimOld.net. CNAME JimOld.net.
mail.JimOld.net. A 192.22.141.70
ns1.JimOld.net. A 192.22.141.70
ns2.JimOld.net. A 192.22.142.134
ns3.JimOld.net. A 192.22.141.70
ns4.JimOld.net. A 192.22.142.134
ns5.JimOld.net. A 192.22.141.70
ns6.JimOld.net. A 192.22.142.134
webmail.JimOld.net. A 192.22.141.70


Thanks,

Steve
 
Back
Top