Welcome to WebmasterWorld Guest from 18.104.22.168
Forum Moderators: mack
this is my first post but i have been a lurker here for years. i have a shared hosting account with Godaddy. it has been running ok, but recently its been a drag so i decided to setup a dedicated server to run my websites. i have pretty everything setup at this point except transferring the domain over to the dedicated box. I am totally new to DNS, domain name setup. Anyone have experience done something like this? What is needed to get this done? In the dedicated server panel, there is a command to "Create DNS zone (master or slave)", what is that for? Any tips would be appreciated.
I am not familiar with godaddy hosting or dns management but the usual course is to just change the DNS to your new servers IP address, changes will take place anywhere between 10 minutes and a day or so. You need to change the A records in your control panel.
Now your server, if you are NOT running the nameservers on your server, some, including me, run DNS from a different server incase a server goes belly up you can quickly change DNS to another server. The DNS zones ON your server are only needed IF you plan on running nameservers on that server, so, if you just update the DNS to the new server everything will work.
Anyone have experience done something like this? What is needed to get this done?
It takes some getting used to, but after the first one it becomes easier. The info below is sketchy as it's been a while, get support on the phone, they will help you through it.
In the dedicated server panel, there is a command to "Create DNS zone (master or slave)", what is that for?
I don't think you have to mess with that one.
You should have THREE IP addresses assigned to this server. By default, they are not bound to the server. You would do this through the server admin control panel, not Plesk - they are different. (You may need to call G.D. support on this one to walk you through.)
Second, mark this well: there is a reason you have three. You will need to assign two of those to a primary and secondary DNS so that your DNS report for your domain(s) come up clean. The mistake often made is to a) bind only one IP to your name server and assign NS1 and NS2 to that IP, or 2) dedicate two IP's away to SSL certs, which means you have to get more IP's. Your NS1 and NS2 need to be different IP's*, and need dedicated IP's for any domains you use as a name server.
Go to the domains you want to use for name servers, dedicate the IP's to those domains. Go into DNS setup for those domains, add A records for the name servers: ns1.domain.com, ns2.domain.com, etc. You may be able to do this as a subdomain of the domain you are using if you only have one domain on the server. (Get support on the phone, this info may be incomplete!)
While you're in there, add an SPF record, this will help avert future problems with email. Click Add Record, select TXT as the record type, add
v=spf1 a mx include:[ROOT SERVER].net ~all
Where "[ROOT SERVER]" is the name of GD's outgoing MAIL SERVER. In my case that's just "secureserver.net." Yours may or may not be the same. Understand this is not your mail server, mail.yourdomain.com, this is G.D.'s mail relay server. All your mail will have to pass through this (it's how they control relay limits.)
Once your DNS servers are set up, go into your domain name registration account (hopefully with G.D.) Go to the domain manager. Get on the page to edit the domain name info for the domain you want to use as the name server. Lower left, look for "Host Summary", it should be blank. Click add.
Now add the two name servers you created. Don't add the full NS name (ns1.domain.com) just assign two NS's, NS1 and NS2.
* The above scenario is not perfect - name servers for a given domain SHOULD be geographically diverse, in which case you might want to pay for an external DNS service, which adds up. But if you assign two unique IP's to your DNS servers, it is passable on the DNS report.
Again, been a while since I did this, so get support on the phone before making any changes - they are actually very helpful and unless you add a lot of domains or SSL certs to the dedi, it should only have to be done once.
After it's all set up, before loading any files go to DNS reports and run a report. Address any red flags one by one by tweaking the DNS/Mail server settings. As you do any of this, keep in mind it takes time to propagate, just like moving a domain, don't be alarmed if the changes don't update immediately.
- Have the client contact their registrar and have them create authoritative records for the nameservers at the registrar (have them make the nameservers on their end) This is important as the nameserver will not work unless this has been done
- Have the registrar point the domain at your nameservers.
That is it in a nutshell. What point are you at currently PalmPilot?