[ale] godaddy for DNS

[Crawford Rainwater]

John and company:

You have two options actually.
(1) Use GoDaddy for all of your DNS records.  However, reference another posting about the GoDaddy exodus due to their changing SOPA position.
(2) Use your virtual machine as one DNS server and a second for a DNS slave server.  My personal choice since some ISPs and hosting groups can cause issues with rDNS (reverse DNS) matching of email (part of spam detection/prevention in some cases) and such.  You would have your domain name registrar associate/register the domain's DNS with both of these (e.g., ns1.example.com and ns2.example.com for example.com) which comes up on a "whois example.com" typically at the bottom of the record.

HTH.

--- Crawford 

The Linux ETC Company
10121 Yates Court
Westminster, CO 80031 USA
voice:  +1.303.604.2550
web:    http://www.linux-etc.com

Please do not print this email unless it is absolutely necessary.  Be friendly to the environment by saving paper.


----- "John Heim" <john at johnheim.net> wrote: -----
> 
> Hi, I have a donated virtual machine to use for a non-profit. Its for
> the
> International Association of Visually Impaired Technologists (IAVIT).
> I've
> registered iavit.org at godaddy. But I'm a little confused as to what
> DNS
> records I need in order to get mail (postfix, dovecot) and lists
> (mailman)
> to work. I need email addresses like john at iavit.org to work and
> addresses
> like announce at lists.iavit.org to work.
> What I have at the moment is an A record with a blank host name
> pointing to
> the IP of our VM, another A record for lists that points to the same
> IP
> address. I wasn't sure you could have 2 A records pointing to the same
> IP
> address but it seems to work. Then I have CNAME records for www and
> wiki
> pointing to lists.
> 
> Can I point godday to a DNS server on the virtual machine itself? I
> tried to
> do that but it balked. For one thing, it said I needed 2 DNS servers.
> I'm
> not sure what the point of that is because iif DNS is down on the VM,
> nothing else on the VM is going to work anyway.
>