DNS configuration Runabove, Linode, OVH

7 posts / 0 new
Last post
#1 Sat, 01/10/2015 - 07:09
nilbud

DNS configuration Runabove, Linode, OVH

Hey there,

I have a problem which is mainly related to my lack of knowledge regarding DNS. Recently I've been looking at moving from my various shared hosting packages to a VPS. Obviously Virtualmin is the way to go. Obviously, after busting my brain comparing and testing all the various competitors available.

Now I have three vps systems set up. OVH is cheap and hoary. Linode is pricey but consistent. Runabove is fast and shiny and new with lots of RAM and cores and whizzy SSDs.

Apparently using Linode you can just point your nameserver entries on your domain to Linode's nameservers everything works magically.

Using Runabove there seems to be no DNS handling of any kind and if there is they are saying nothing.

OVH on the other hand just seems to be a giant septic tank of incomprehensible gibberish even if it wasn't in French. No one ever knows if their configuration is messed up or if the system admins have randomly changed their DDOS tech.

Like Goldilocks I want to use Runabove, it's fast, cheap and loads of memory but DNS has to be set up either elsewhere or within my Runabove instance or some combo of the two.

My domain is held in a registry which only allows two nameserver cnames and nothing else.

Can anyone help with a few sane suggestions for getting me going with Runabove or failing that Linode. I doubt if anyone has a happy OVH story but if you do please pass it along.

TIA Seán (not a n00b but new to this)

I run virtualmin in a Ubuntu 14.04 server instance as I'm familiar with ubuntu but if Centos is more convivial to Virtualmin I'll run that instead.

Sat, 01/10/2015 - 14:04
tpnsolutions
tpnsolutions's picture

Hi,

I'd be happy to assist you in getting a proper DNS setup regardless of the provider you work with.

Please feel free to read about REAL user experience when working with me at:

https://virtualmin.com/node/25081

Best Regards,
Peter Knowles
TPN Solutions

Email: pknowles@tpnsolutions.com
Phone: 604-782-9342
Skype: tpnsupport
Website: http://www.tpnsolutions.com
Best Regards,
Peter Knowles | TPN Solutions
Email: pknowles@tpnsolutions.com | Skype: tpnassist
Sat, 01/10/2015 - 14:35 (Reply to #2)
nilbud

Cheers first of all I'd like to make clear I'm not in a position to reimburse you for your time but I'll say nice things about you if it works.

I like Runabove, they have great bang for buck but you can't even set a reverse dns. I had the website hosted on a standard shared hosting setup, so I just went into the shared hosting and rewrote the DNS to point to my Runabove instance. What I couldn't do was set up the reverse dns. Regardless I wasn't going to get away with just squatting on their DNS for very long.

Is there such a thing as a nameserver/DNS service? Am I just being particularly obtuse with regard to runabove's DNS/Nameserver-ness?

I've been jamming away on this for a while now and have made good progress but where postfix meets DNS DNSSEC and DKIM my brain hurts. I got to the point where I could send and receive email from everywhere except google and then I tweaked something and now no mail works in or out.

Sun, 01/11/2015 - 00:11
tpnsolutions
tpnsolutions's picture

please see below...

Best Regards,
Peter Knowles | TPN Solutions
Email: pknowles@tpnsolutions.com | Skype: tpnassist
Sun, 01/11/2015 - 00:09
tpnsolutions
tpnsolutions's picture

Hi,

Cheers first of all I'd like to make clear I'm not in a position to reimburse you for your time but I'll say nice things about you if it works.

That's cool, I work on a "gratitude pricing" model, which includes but is not limited to: feedback/testimonials, spreading the word about my assistance and skills, financial compensation.

So adding a comment to the page noted above outlining what you needed help with, and whether/how I helped you is gratitude in itself :-)

The good news is, you'll still get the same level of assistance regardless of how you show your gratitude since I love helping people.

I like Runabove, they have great bang for buck but you can't even set a reverse dns.

I've only briefly skimmed over their offering but it does look pretty cool. Reverse DNS can only be managed by the IP address owner, so you'll need to get the provider to make the adjustment for you. Some providers also offer a control panel option to make the process simple, but bottom line, they control this record NOT you.

Drop me a line on Skype if you want to proceed with acquiring my assistance so we can discuss your needs in greater detail and get you setup with a solution!

Best Regards,
Peter Knowles
TPN Solutions

Email: pknowles@tpnsolutions.com
Phone: 604-782-9342
Skype: tpnsupport
Website: http://www.tpnsolutions.com
Best Regards,
Peter Knowles | TPN Solutions
Email: pknowles@tpnsolutions.com | Skype: tpnassist
Wed, 04/15/2015 - 10:38 (Reply to #5)
nilbud

As an update to this saga...

It was probably a good idea anyway. I hunted high and low for a place which could handle my somewhat limited DNS requirements. Ended up on CloudFlare, so now I have a CDN and https and caching AND DNS. It points to my Runabove instance but could point to any machine anywhere so there's that, on the other hand CloudFlare is a potential horror story if it goes wrong. If it comes to that I could replicate the DNS part if I had to.

I've a demo wordpress site set up on it at https://hpk.ie and it seems to be functional.

Except for the email.

Do you know anything about MailJet?

Fri, 04/17/2015 - 10:34 (Reply to #6)
nilbud

To configure Postfix for relaying emails through mailjet

postconf -e 'relayhost = in-v3.mailjet.com'
postconf -e 'smtp_sasl_auth_enable = yes'
postconf -e 'smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd'
postconf -e 'smtp_sasl_security_options ='

Create the file sasl_passwd and insert the following line

in-v3.mailjet.com [Big lump of password from mailjet]

I used sudo nano sasl_passwd and pasted it in but you could do this instead

echo "in-v3.mailjet.com [Big lump of guff from mailjet]" > /etc/postfix/sasl_passwd
chown root:root sasl_passwd
chmod 600 sasl_passwd

Now convert /etc/postfix/sasl_passwd into a format that Postfix can read:

postmap /etc/postfix/sasl_passwd

This will create the file /etc/postfix/sasl_passwd.db.

All that is left to do is restart Postfix:

/etc/init.d/postfix restart

The following links are good info.

https://app.mailjet.com/account/setup

and

https://www.howtoforge.com/postfix_relaying_through_another_mailserver

Topic locked