Skip to Content.
Sympa Menu

discuss - Re: [opennic-discuss] dns.openic.glue zone WAS New T2 Server Config

discuss AT lists.opennicproject.org

Subject: Discuss mailing list

List archive

Re: [opennic-discuss] dns.openic.glue zone WAS New T2 Server Config


Chronological Thread 
  • From: Günter Grodotzki <guenter AT grodotzki.ph>
  • To: discuss AT lists.opennicproject.org
  • Subject: Re: [opennic-discuss] dns.openic.glue zone WAS New T2 Server Config
  • Date: Tue, 04 Jan 2011 13:35:57 +0100
  • List-archive: <http://lists.darkdna.net/pipermail/discuss>
  • List-id: <discuss.lists.opennicproject.org>

Hmm but why these changes at all? Do T1 get too much traffic? If so, I could think about hosting a T1.

I just read unbound does support static zones/records: http://www.unbound.net/documentation/unbound.conf.html

But I feel uncomfortable putting T2 Servers in there which change frequently.

On 1/4/11 7:46 AM, Julian DeMarchi wrote:
On 01/04/2011 03:46 PM, Jamyn Shanley wrote:
Ah, nevermind. I think you meant to say 'unbound is
non-authoritative.' ... right. So if we really are going to be
required to do this as a T2, we'll probably have to look at other
options (NSD, etc) unfortunately.

Thats right. Sorry!

We can't go limiting the DNS software used. We need to think of another
way to present the dns zone so the T2 address's can be grabbed without
drama.

I propose that the DNS zone be setup with all the T1's as NS servers and
leave all the T2s as A records of the domain dns.opennic.glue.

Hopefully this will keep all happy?

--julian

_______________________________________________
discuss mailing list
discuss AT lists.opennicproject.org
http://lists.darkdna.net/mailman/listinfo/discuss





Archive powered by MHonArc 2.6.19.

Top of Page