From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <fe41879c0909161547i4a0846b0qdfe89b8a106799ab@mail.gmail.com>
References: <fe41879c0909161231q5f1cd5a6r4083aca9e18cbda1@mail.gmail.com>
	<35e1ba3ae1b9f7c427c2823732cd64f0@coraid.com>
	<fe41879c0909161547i4a0846b0qdfe89b8a106799ab@mail.gmail.com>
Date: Wed, 16 Sep 2009 19:02:19 -0400
Message-ID: <fe41879c0909161602u6353630blb9fb5feea4d2962f@mail.gmail.com>
From: Akshat Kumar <akumar@mail.nanosouffle.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [9fans] Authoritative Name Server
Topicbox-Message-UUID: 6f38606a-ead5-11e9-9d60-3106f5b1d025

Further testing shows that the problem is with
my srv entries. Is it my ndb configuration, or
just a problem with ndb/dns? Here's the
portion that causes the above problem
(if uncommented) with a zone transfer using dig
on Linux:

#dom=_jabber._tcp.mail.nanosouffle.net
#	srv=xmpp-server.l.google.com pri=5 weight=0 port=5269
#	srv=xmpp-server1.l.google.com pri=20 weight=0 port=5269
#	srv=xmpp-server2.l.google.com pri=20 weight=0 port=5269
#	srv=xmpp-server3.l.google.com pri=20 weight=0 port=5269
#	srv=xmpp-server4.l.google.com pri=20 weight=0 port=5269
#
#dom=_xmpp-server._tcp.mail.nanosouffle.net
#	srv=xmpp-server.l.google.com pri=20 weight=0 port=5269
#	srv=xmpp-server1.l.google.com pri=20 weight=0 port=5269
#	srv=xmpp-server2.l.google.com pri=20 weight=0 port=5269
#	srv=xmpp-server3.l.google.com pri=20 weight=0 port=5269
#	srv=xmpp-server4.l.google.com pri=20 weight=0 port=5269

If I have this commented, zone transfers with dig work just fine.
What's the proper setup here?


Thanks,
ak