VPS Plus Email Help Needed

You need a DNS management tool where you can change and edit records for that domain. Are you saying you already have a public DNS server (the dedicated server you're talking about)? If so what software is it running?

That's the thing i have no idea, i do know with the dedicated server in WHM it looks like this:

But where those comes from I have no clue ?


I have the VPS set up completely isolated as in it is from scratch has nothing to do with the above.

It runs Centos6

But I don't know how those dns stuff works like where does ns.dns1.co.za come from ?
 

Attachments

  • 1430220132114.jpg
    1430220132114.jpg
    74.6 KB · Views: 105
That's the thing i have no idea, i do know with the dedicated server in WHM it looks like this:

But where those comes from I have no clue ?


I have the VPS set up completely isolated as in it is from scratch has nothing to do with the above.

It runs Centos6

But I don't know how those dns stuff works like where does ns.dns1.co.za come from ?

Those name servers have to point to servers that handle DNS (i.e. the server that looks up the IPs when somebody opens your webpage or sends you email, etc). Some hosting providers have their own DNS servers and management tools but some don't, in your case it looks like they don't so you need to use your own. That is why I suggested using Route 53.

I don't know anything about WHM so I'm not going to try and help there.

But once you have your name servers set up and are able to edit your records, then you need to just add an A record which points to your VPS's IP address, e.g:

1.2.3.4 A www.mydomain.com

If you're only running one site off that VPS then you should be able to reach your site as long as your web server (e.g. Apache, nginx) is set up, accepting connections and your site is in the default public location (on Centos it's usually /var/www/html/ for Apache).

If you're running multiple sites off the VPS then you'll either need to give each site their own folder in the public path (e.g. /var/www/html/site1, /var/www/html/site2, etc) or you'll use virtual hosts so you can point to separate subdomains.
 
Those name servers have to point to servers that handle DNS (i.e. the server that looks up the IPs when somebody opens your webpage or sends you email, etc). Some hosting providers have their own DNS servers and management tools but some don't, in your case it looks like they don't so you need to use your own. That is why I suggested using Route 53.

I don't know anything about WHM so I'm not going to try and help there.

But once you have your name servers set up and are able to edit your records, then you need to just add an A record which points to your VPS's IP address, e.g:

1.2.3.4 A www.mydomain.com

If you're only running one site off that VPS then you should be able to reach your site as long as your web server (e.g. Apache, nginx) is set up, accepting connections and your site is in the default public location (on Centos it's usually /var/www/html/ for Apache).

If you're running multiple sites off the VPS then you'll either need to give each site their own folder in the public path (e.g. /var/www/html/site1, /var/www/html/site2, etc) or you'll use virtual hosts so you can point to separate subdomains.

Hey thanks for the reply.

Jip I have multiple sites with vhost

Okey is it possible to create your own dns server instead of using route 53?
 
Hi,

If your VPS Server is hosted with us then you can manage your DNS through the control panel we provide for the VPS server. I can resend you your login details for this. Please private message me and I will assist you if required.

If however you are only using us to register domains then it needs to point to the NS records where the VPS server is hosted. (Sorry trying to make this as non technical as possible :) )

I will assist you in anyway I can even if the VPS is not hosted with us. Please send us a support ticket via your Hostking Client area and make it attention for me and I'll gladly help where I can.
 
Last edited:
Hi,

If your VPS Server is hosted with us then you can manage your DNS through the control panel we provide for the VPS server. I can resend you your login details for this. Please private message me and I will assist you if required.

If however you are only using us to register domains then it needs to point to the NS records where the VPS server is hosted. (Sorry trying to make this as non technical as possible :) )

I will assist you in anyway I can even if the VPS is not hosted with us. Please send us a support ticket via your Hostking Client area and make it attention for me and I'll gladly help where I can.

Hey man! I love you guys your support is wonderful, unfortunately only my domain is with you currently and ag I just don't want to make this your guys problem, because it's not :)


Let me play around today , trying to find my ns records of the vps and then if all else fails then I will send you a pm of desperate help :)


( Again thank you for the willingness )
 
May I suggest you use Amazon's Route 53 as your DNS management tool. It costs a little ($0.51 per domain) but it's well worth it especially since you're going to be using SES with Sendy. Some DNS editors don't play along nicely with the format of the TXT records you have to use for DKIM, Route 53 just works.

To do this:

1. Login to your AWS account.
2. Select the Services menu and choose Route 53.
3. Select Hosted Zones.
4. Create Hosted Zone.
5. Enter Domain Name and comment, leave Type on the default.
6. You will now receive a list of 4 names ervers.
7. In your Hostking control panel change the name servers to the ones shown above.

Wait for a few hours for propagation, now you can manage your DNS through AWS.

To check which nameservers are being used you can run:

Code:
dig yourdomain.com NS

This works on Mac and Linux, not sure what the Windows command is.

I ran that and get the following issue:

Code:
[me@vps43108 ~]$ dig afri-mail.co.za ns @cdns1.hkdns.co.za

; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.30.rc1.el6.1 <<>> afri-mail.co.za ns @cdns1.hkdns.co.za
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 60110
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;afri-mail.co.za.               IN      NS

;; Query time: 259 msec
;; SERVER: 197.242.68.195#53(197.242.68.195)
;; WHEN: Thu Apr 30 02:28:13 2015
;; MSG SIZE  rcvd: 33

@Hostking, is cdns1.hkdns.co.za you guys? I am so confused as to where I got that from, it was in my nameservers in hostking, but not sure If it was there or if I put them there, so sorry.
 
I ran that and get the following issue:

Code:
[me@vps43108 ~]$ dig afri-mail.co.za ns @cdns1.hkdns.co.za

; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.30.rc1.el6.1 <<>> afri-mail.co.za ns @cdns1.hkdns.co.za
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 60110
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;afri-mail.co.za.               IN      NS

;; Query time: 259 msec
;; SERVER: 197.242.68.195#53(197.242.68.195)
;; WHEN: Thu Apr 30 02:28:13 2015
;; MSG SIZE  rcvd: 33

@Hostking, is cdns1.hkdns.co.za you guys? I am so confused as to where I got that from, it was in my nameservers in hostking, but not sure If it was there or if I put them there, so sorry.

Yeah, that's Hostking.
 
I have no idea what you're trying to do :D

Sounds like you're making it way more complicated than it needs to be.
 
I have no idea what you're trying to do :D

Sounds like you're making it way more complicated than it needs to be.

I think the same hahaha.


I'll figure out today. I am wiping the VPS and going with a fresh Debian 7 badboy installation.
 
I think the same hahaha.


I'll figure out today. I am wiping the VPS and going with a fresh Debian 7 badboy installation.

It has nothing to do with the VPS's OS though. Unless you are running your own name servers on that box making changes to your OS is not going to make any difference.
 
Hi,

Yes we parked the domain for you upon registration I see.

However I still recommend you point it to the NS records where the domain is hosted.

We can however point the domain to the IP addresses directly but then no management of DNS and you'll possibly have to email us each time you require dns changes.

I think if you VPS is hosted by Amazon then all you need to do is point it to their NS records so you can manage it within their control panel?
 
Hi,

Yes we parked the domain for you upon registration I see.

However I still recommend you point it to the NS records where the domain is hosted.

We can however point the domain to the IP addresses directly but then no management of DNS and you'll possibly have to email us each time you require dns changes.

I think if you VPS is hosted by Amazon then all you need to do is point it to their NS records so you can manage it within their control panel?

Omg this DNS stuff is so overcomplicated.


Okey I'll do that quickly.

:)
 
best bet, to try first, get in touch with hostking, ask them if the offer a park package where you can manage dns from.. if they use cpanel, they definitely have no excuse not to offer it, and for free as well.. rather keep everything in one place, as opposed to having to manage too many components across various hosts..

been waiting 10 minutes now for a reply from one of their live chat agents.. hope their email support is better..
 
Hi,

Yes we parked the domain for you upon registration I see.

However I still recommend you point it to the NS records where the domain is hosted.

We can however point the domain to the IP addresses directly but then no management of DNS and you'll possibly have to email us each time you require dns changes.

I think if you VPS is hosted by Amazon then all you need to do is point it to their NS records so you can manage it within their control panel?

but why not just offer a dns only hosting account..? its super simple, especially with cpanel..
 
best bet, to try first, get in touch with hostking, ask them if the offer a park package where you can manage dns from.. if they use cpanel, they definitely have no excuse not to offer it, and for free as well.. rather keep everything in one place, as opposed to having to manage too many components across various hosts..

been waiting 10 minutes now for a reply from one of their live chat agents.. hope their email support is better..

It's me who's not understanding, see when we bought our dedicated server from Afrihost they set up the thing with centos whm and their dns server.

Then I buy the domains from hostking godady etc and then point it to AF nameservers


I now went and bought a VPS and have to do all that myself.

Hostking offers me the ability to add namesevers which is all I need.


The problem is I fked up not installing a proper DNS server
 
I just want to give everybody feedback as to what the problem was.

Turns out I did everything right, the issue came in with this:
Code:
cdns1.hkdns.co.za
cdns2.hkdns.co.za

I got confused, because I thought those are the nameservers I can use for DNS, after finally realizing that's just some useless place holder I went with the Dr's advice, but I used cloudfare instead, because it's free :)

The reason I thought these are the DNS stuff

Code:
cdns1.hkdns.co.za
cdns2.hkdns.co.za

Is because when we had domains with afrihost I used there pre filled stuff.

So bottom line I was a koki and over complicated a very basic thing, because I did not fully fathom what DNS and parking etc is.
 
@Drzoid,

Have you had this error?

I uploaded the Sendy files, added the sql settings in
Code:
/include/config.php
i then went to
Code:
mydomain.com/sendy
, but I then get a 404 error, if I go to just
Code:
mydomain.com
I get a 500 internal server error.

I have checked and "AllowOverride All" is active.
 
Top
Sign up to the MyBroadband newsletter
X