Internet: IP one way to mail one way to web

[Mental Trousers]

The info in the pic is good, but personally I'd change the 2nd line to read

www.notmyname.co.nz - IP v4 (CNAME) - notmyname.co.nz

A CNAME is an alias/pointer.

Not necessary but I always reduce how many actual ip numbers are involved cos it sucks arse having to change the same ip number 10+ times, whereas with CNAME's you do it once.

The MX record you've got there is fine. No need to change it.

As for SSL, I just use a self signed certificate on all of our servers and tell Go Daddy etc to jam it. Nobody outside our office is going to be using https with our machines and if they are then they get to pay for the certificate.

http://www.akadia.com/services/ssh_t...rtificate.html

[Gremlin]

We use SSL certs for lappys/mobiles etc connecting over the internet to exchange. Outlook RPC over HTTP (forget the new name for it...) kicks up a hell of a fuss with self-signed certs.

[pzkpfw]

The info in the pic is good, but personally I'd change the 2nd line to read

...

A CNAME is an alias/pointer.

Not necessary but I always reduce how many actual ip numbers are involved cos it sucks arse having to change the same ip number 10+ times, whereas with CNAME's you do it once.

That's good info, thanks. I'll probably leave it alone as I just don't have that many entries to worry about; but that's information I'll hopefully retain for later use.

The MX record you've got there is fine. No need to change it.

Yep. Made the change today, using option B, and I'm still getting mail - so that's a relief.

The new http://dev.notmyname.co.nz correctly gets to my home web server.

(I used option B, because I looked at my hosts website and there's no email-only option, so I figured since I'm paying for the "website" too, I may as well leave it there just in case. May one day have something I need hosted 24x7.)

As for SSL, I just use a self signed certificate on all of our servers and tell Go Daddy etc to jam it. Nobody outside our office is going to be using https with our machines and if they are then they get to pay for the certificate.

http://www.akadia.com/services/ssh_t...rtificate.html

Yeah, I'm making my own certs (a CA and one for the site itself, plus more (client and server-side) for the web service I'm testing) using the Microsoft dev tool "makecert".

I just find having the cert name match the site name removes one warning, and makes clients feel happier. Otherwise people can worry about why they get the warning.

I still have to get them to accept my "NotmynameCA" certificate authority cert as trusted, but that's easyish to explain, and once the website gives no "errors" it all looks good.

Cheers,

[pzkpfw]

Thanks, everyone.

[thecharmed01]

Late in the game, but have you looked at Google Apps.
They route all mail etc through the cloud with GMail type access, but using your domain instead of an @gmail.com address.

I have it setup for over a dozen domains and it's super easy.
Also makes access from anywhere simple, just go to gmail.com and login with your full domain email and your password.

[pzkpfw]

Late in the game, but have you looked at Google Apps.
They route all mail etc through the cloud with GMail type access, but using your domain instead of an @gmail.com address.

I have it setup for over a dozen domains and it's super easy.
Also makes access from anywhere simple, just go to gmail.com and login with your full domain email and your password.

Yes, probably would be a good thing, but my current email host does the biz and I'm happy enough.
(
I mostly use Outlook on my Laptop, but they do have a web mail interface so I can access (new mail) via any browser any time.
My phone connects to them fine, and can send/receive.
I've got my IIS connected to their server too so I have my own local SMTP server relaying via my domain/account.
All seems OK.
)

[scracha]

If you do end up running a mailserver, then it's a good idea to have a secondary MX in the event your mailserver goes down or gets disconnected. If it's a small organisation then pointing it to a cloudy based mailserver is a good plan. A really good plan is to have the cloudy based mailserver's mail arrive on your own mailserver automatically when it's back up and running.

Personally I'm a bit paranoid and don't trust a 3rd party to store all a customers mail....so I have mail for most customers on 2 different servers (sometimes as simple as forwarding a copy of all email to another domain).

And google apps domains thingie is the shizz and it's free for up to 10 users. Good tools there to migrate from other email systems. Works with pretty much everything.