If yall would like, I could provide DNS services. My servers use BIND. I could offer two of any of the 6 server I have. One is on a T1 in Washington state. The rest are one various 50/10 connections. Christopher Dobbs Software Developer LybreDyne Technologies (503) 914-0799 x2213 http://www.lybredyne.net/ NOTICE: The information contained in this e-mail is confidential and may be privileged or otherwise protected from disclosure. This e-mail is intended solely for the use of the named addressee. Please be aware that any other use, printing, copying, disclosure or dissemination may be subject to legal restriction. If you are not the intended recipient, please notify us immediately by return e-mail to the sender and delete from your computer. Although we attempt to sweep e-mail attachments for viruses, it does not guarantee that either are virus-free and accepts no liability for any damage sustained as a result of viruses. -----Original Message----- From: haiku-development-bounce@xxxxxxxxxxxxx [mailto:haiku-development-bounce@xxxxxxxxxxxxx] On Behalf Of Urias McCullough Sent: Tuesday, September 01, 2009 14:49 To: haiku-development@xxxxxxxxxxxxx Subject: [haiku-development] Re: List of svn-users On Tue, Sep 1, 2009 at 2:33 PM, Jorge G. Mare<koki@xxxxxxxxxxxxx> wrote: > For svn, why not just go directly with svn.haiku-os.org? Is it currently > being used? It wasn't - so I already updated the DNS in webfaction to point svn.haiku-os.org there (and Oliver tested this while I was chatting with him in IRC). > For the website and Trac, is it not possible to just create a test > subdomain for each of their respective VMs (ie., testweb.haiku-os.org > and testdev.haiku-os.org? Once those two installations are tested and > known to be running OK, then the DNS settings can be modified to point > to them. Or am I missing something? :) I think it would be OK to test everything with an alternate domain if it's convenient... as long as there are no hardcoded references to haiku-os.net anywhere ;) But we can also easily setup test subdomains as you suggest. >> Ah, I have no concerns about controlling the DNS myself - I simply didn't >> know that we as a group control the DNS already. I was assuming our current >> hoster would do so. >> > > It would still be convenient if those working on the new server had > access to the DNS settings; that way, you would not have to rely on > somebody across the ocean on a different time zone for a change that may > be required right away. Redundancy is this case is good IMO. ;) I agree, and I also think we should have someone in Europe with access to our Godaddy account in the event that emergency maintenance is needed. I would probably suggest Axel as he is currently on the Haiku, Inc. team anyhow. If we want to separate the duties further (for security reasons), and have DNS hosted outside of Godaddy for the domains that need to be maintained, I would be OK with that. Should we considering setting up DNS on our new server? or should we seek a good alternative DNS provider? Hopefully the changes to DNS are somewhat rare... - Urias