help please

[Baka092]

Help please!

I set up the 2 name severs and ip's on my godaddy domain, exactly like the video. Now what's next? Any help would be excellent.

[EuroNut]

Help please!

I set up the 2 name severs and ip's on my godaddy domain, exactly like the video. Now what's next? Any help would be excellent.

Baka092 - Welcome to the Jag Club You're gonna have to be a bit more specific ... Like what cPanel are you using, what do you want to do next, etc ...

(I was gonna type "Break for coffee" but I'm not feeling that nasty today LOL)

[JPC-Veena]

Baka092,

Please open a support ticket from
https://secure.jaguarpc.com/clients/
with details of what you are trying to do and we can help you.

[Baka092]

What I would like to do it:

1. Set up accounts (which i have done)
2. Be able to get to these pages (Using the ip # based URL works but none of my domains seem to 'take' after making DNS/Name server changes)
3. Have my Godaddy domains actually pull up the pages when I type them in. (I can forward the domains to the ip # based URL, but hoped to be able to figure out how to do it the right way)

I am new to VPS's but have many hosted accounts and don't consider my self a newb in the web wrold. Just a newb in the server area, which is why I go the thing to begin with.

I know I am doing something wrong because I keep getting this email:

[ipcheck] Problems with dns setup on vps.konscience.com


PS. I submitted a ticket and they pointed me to the video which I have already used to set up my name servers! It was a fast reply but didn't really help much.

Forgive the newb-ness and thanks for any help you can offer. If I can figure this little problem out I promise to help the next newb that comes into the forums. ;-)

[EuroNut]

What I would like to do it:

1. Set up accounts (which i have done)
2. Be able to get to these pages (Using the ip # based URL works but none of my domains seem to 'take' after making DNS/Name server changes)

Baka092, please tell us which control panel you're using.

If it's WHM/cPanel or DirectAdmin, I'll be happy to talk you through some early setup stages, as will many others in these forums.

If it's Plesk or one of the other CPs available, I have no real working knowledge of them and will stand back and let someone else dive in.

Just give us a starting point, OK?

[Baka092]

Opps, that would help wouldn't it. cPanel/WHM

[EuroNut]

Opps, that would help wouldn't it. cPanel/WHM

LOL! Yup! That helps!

OK, I just had a quick look at dnsstuff.com to get an idea of how the outside world is looking at your domain and nameservers. You might want to take a look too here

Basically what that's saying is that you've registered your name-servers OK at GoPoppy (you know who I mean) but you haven't installed them onto your VPS.

That needs to be the first job before you start adding other domains. Get yourself into WHM and select the very first menu option "Basic cPanel/WHM Setup". Scroll down a bit and you'll get to an item "Main Shared Virtual Host IP".

I'm assuming you've been issued 3 IP addresses here, ending 166, 167 and 168, so the 166 address needs to be in there (it probably already is).

Then scroll down a bit more till you get to Primary Nameserver and type in there the NS1 name you're using (ns1.kon########.com) - You know what to replace the #s with.

To the left of that click on "Assign IP address" and assign it your 167 IP address. Then click on the "Add an A entry" button.

Scroll down 1 more item to Secondary Name Server and repeat the above for your NS2 nameserver assigning your IP address ending in 168 to it, and then add the A entry for it too.

Now scroll right down to the bottom of that screen and click "Save".

What you've now done is actually install the nameservers onto your VPS, and they'll start answering queries from outside.

Now, if you scroll way down the left-hand menu in WHM to the section that starts DNS Functions you can click on Edit DNS Zone and take a look.

If you've already installed your main domain (kon#######.com) you should see it listed and be able to select that zone to edit.

Let us know how you get on up to this point and we'll take it from there.

[Baka092]

Okay I am successful up to this point. Ready for the next instructions boss!


Note: On the last part I see my main domain and also my NS1/NS2 ones. Is this correct?

[EuroNut]

Okay I am successful up to this point. Ready for the next instructions boss!

LOL! Cool!

Note: On the last part I see my main domain and also my NS1/NS2 ones. Is this correct?

Yussir! Now you're gonna edit the DNS zone for your main domain, and get the nameservers and domain all working, OK?

Sooooo, now you need to select "Edit DNS Zone" in WHM, then select your main domain, and click on "Edit".

(Note of caution: For some reason WHM put "Delete DNS Zone" into the menu right above the edit option, so if you slip with your mouse and hit the button, you'll hit "delete" instead of "edit" - Been there, done that, you never do it twice LOL)

Once you've hit the Edit button you'll get a screen giving the DNS zone file's details about your domain. I don't know how much will be there, or missing, right now, so I'm just gonna type below here what the "standard" file should look like, and you can check it against what you've actually got...... (In all cases, you'll know what to replace the #s with) ....

From the top .... the top central box should contain ns1.kon#######.com. Note the period after .com - Most errors occur at first by forgetting that you MUST use that period to signify the end of the record. If you don't, it will append the domain name and you'll end up with ns1.kon#######.com.kon#######.com <== not good!

Next you need to put an admin email address to the right of that, replacing the "@" with a "."

So something like "hostmaster.kon#######.com." would do fine - Note there's another period at the end after .com (you'll get used to it!).

The next column of 5 boxes contain some time settings for refresh, retry, etc, which you can leave as default for now, and the top box of those 5 is the serial number for this entry. That increments by 1 and changes the date automatically each time you edit in this section, and you should just let it do its thing and not touch it.

Now for the meaty bit - I'm just going to type below what it should look like and you can compare (The order these appear in don't matter) ......


Domain TTL Record Type

kon#######.com. 86400 NS ns1.kon#######.com.
kon#######.com. 86400 NS ns2.kon#######.com.
ns1.kon#######.com. 14400 A ###.###.###.167
ns1.kon#######.com. 14400 A ###.###.###.168
kon#######.com. 14400 A ###.###.###.166
localhost.kon#######.com. 14400 A 127.0.0.1
mail 14400 CNAME kon#######.com.
www 14400 CNAME kon#######.com.
ftp 14400 A ###.###.###.166
kon#######.com. 14400 MX 0 vps.kon######.com.
kon#######.com. 14400 TXT "v=spf1 a mx a:vps.kon####.com ~all"


Note (again) - Fully qualified entries like "kon#######.com." must have the dot at the end.

Where I've just used a hostname (like mail, www and ftp) NO dot is used - It will fill in the blanks itself in the record.

IP addresses do NOT have a dot at the end.

The SPF entry at the end is enclosed in quotes.

I think that should about cover it - Holler when you've got this far and we'll take a look to see how it's working

Have fun!!

[EuroNut]

ns1.kon#######.com. 14400 A ###.###.###.167
ns1.kon#######.com. 14400 A ###.###.###.168

I made a mistake with the above (darn cut and paste!!)

It should read ...

ns1.kon#######.com. 14400 A ###.###.###.167
ns2.kon#######.com. 14400 A ###.###.###.168

Sorry about that, and I'll catch your next update tomorrow ... Goodnight

[thisisit3]

I suggest you use "-all" instead of "~all" in your SPF records, otherwise they don't have any effect on forged emails ("~all" means SOFTFAIL and forged emails aren't deleted).

[Baka092]

Okay I am that far. Most of it was there as you said but had to add the follwing:

vps.konXXXXXX.com. (the bold part to the MX record type)
I also had to add all of the spf thing.

Hope I didn't jack anything up. :-)

Again thanks for all the help!! Next, step please.

[EuroNut]

I suggest you use "-all" instead of "~all" in your SPF records, otherwise they don't have any effect on forged emails ("~all" means SOFTFAIL and forged emails aren't deleted).

Agreed, if this were a brand new just-registered domain. But it's coming from somewhere else and I don't know what Baka092's current mail setup is, so until this VPS is handling all the mail I left the door ajar

[EuroNut]

Okay I am that far. Most of it was there as you said but had to add the follwing:

vps.konXXXXXX.com. (the bold part to the MX record type)
I also had to add all of the spf thing.

Hope I didn't jack anything up. :-)

Cool! Well, we should be almost there now.

I added the vps. to the front of kon####.com in the MX record, because this zone file can become something you can refer to when you add other domains. They can all have the same MX record and the same SPF record, so you won't need to worry about working out if something else should be in there.

Before we go on, you need to open a support ticket with JPC and ask them to set your Reverse DNS records for your IPs. Basically, all you need for now is for ###.###.###.166 to be set to vps.kon#####.com, but also ask them to clear the current reverse DNS they have set for your 167 address, as it looks like an entry has been left behind from a previous user of that IP address, and it could confuse stuff later.

Once you've done that, it's back to WHM to check a couple of final bits ....

On the left menu, the 3rd section relates to Network Setup

Click on hostname and just check that the "Current Hostname" field at the top reads "vps.kon####.com", then click on "Nameserver IPs". If all goes well, WHM will check at the registry for the names and IPs of your nameservers and fill in the blanks, to give you 2 entries looking like:

IP                            Nameserver

###.###.###.167  ns1.kon#######.com
###.###.###.168  ns2.kon#######.com

If for some reason it doesn't then you can use the entry field below to type in the 2 name server names (no dot at the end this time) and assign them to your 167 and 168 addresses.

All being well, this should now have your basic setup running - If it doesn't it means I've missed something, or you've mis-typed something, or ........