The www server was up first late last week.
The root@username.vps.bitfolk.com email has accepted email since Friday.
The godaddy nameserver was set up over the weekend and now has ns.exoco.net and a.authns.bitfolk.com (etc) active.
I have no problem in theory with breaking stuff as long as I can eventually
recover. That's one way to learn. Granted, I have taken 7 days to learn something I didn't want to learn, but things seem always to be sub-optimal with IT.
Right now I think I have bind and reverse dns setups that work. Now all I need is to have the root@exoco.net respond. I'll attend to that in another email.
From: Andy Bennett <andyjpb@ashurst.eu.org>
To: Max B <txtmax@yahoo.ca>
Cc: users@lists.bitfolk.com
Sent: Mon, October 4, 2010 10:54:08 AM
Subject: Re: [bitfolk] mx without bind?
Hi,
> my domain
registry is with godaddy.com.
>
> They do offer a control panel with lots of different settings. Looks like a perl script to /etc/ bridge. There are all kinds of CNAME aliases, and I'm not too sure whether I can/should/ought to delete them because they refer to machines on secureserver.net, or to replace them with my own virtual addresses, or some other alternative with less hassle.
Well, it depends on whether you're using them. ;-)
Usually, when you register a domain with someone like godaddy.com or 123reg, they do 4 things:
1) Primary DNS
2) Secondary DNS
3) MX
4) Web "forwarding"
the CNAME aliases and other things will be related to how (3) and (4) are set up.
Usually (4) is set up to go to a "holding" page. Sometimes it can be set up to load a frame containing some other URL to make it look like your website is now hosted on that domain. If you've set up a web server then you'll have
pointed (at least) the www record at your webserver with either your own CNAME or A record.
(3) is usually set up to forward mail to another address. If you've paid more money then they might host a mailbox for you. If you want to delegate to your own machine then you'll have to point the MX records at your own mailserver, much like you would do for case (4).
If you don't understand what these records are for then you should proceed with caution: setting up your own nameserver (as you suggest in your other mails) will certainly break *all* of that unless you take steps to replicate the setup in your zone file.
The registry provides (1) and (2) by delegating the zone, to their nameservers, in the (in the case of exoco.net) .net zone. If you want to run your own nameservers then you need to instruct godaddy (usually via their control panel) to redelegate the zone to your nameservers.
> Any thoughts would be
welcome.
What are you currently doing with exoco.net? You need to make sure you replicate as much of the current zone as you need before you start hosting it for yourself otherwise some things might stop working...
Regards,
@ndy
--
andyjpb@ashurst.eu.orghttp://www.ashurst.eu.org/0x7EBA75FF
_______________________________________________
users mailing list
users@lists.bitfolk.comhttps://lists.bitfolk.com/mailman/listinfo/users