Re: Authority Issue with Primary DNS - URGENT

Todd Lyons wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Tue, Apr 22, 2008 at 02:11:37PM -0700, Michael J. Ayers wrote:
>
>   
>>   dlz "Mysql zone" {
>>   database "mysql
>>   {host=localhost dbname=dns_external user=dns pass=password}
>>   {select zone from records where zone = '%zone%'}
>>   {select ttl, type, mx_priority, case when lower(type)='txt' then
>>   concat('\"', data, '\"') when lower(type) = 'soa'
>>      then concat_ws(' ', data, resp_person, serial, refresh, retry, expire,
>>   minimum) else data end from records
>>      where zone = '%zone%' and host = '%record%'}
>>     
>
> The above query is referred to as the "lookup query".  I think you left
> off this from the above query: 
>     and not (type = 'SOA' or type = 'NS')
>
> Basically since you're using two seperate queries, you want to return
> everything but SOA and NS records in the "lookup query" above, and SOA
> and NS records only from the following "authority query".
>
>   
>>   {select ttl, type, mx_priority, data, resp_person, serial, refresh, retry,
>>   expire, minimum from records
>>       where zone = '%zone%' and (type = 'SOA' or type='NS')}
>>   {select ttl, type, host, mx_priority, case when lower(type)='txt' then
>>      concat('\"', data, '\"') else data end, resp_person, serial, refresh,
>>   retry, expire,
>>      minimum from records where zone = '%zone%'}
>>   {select zone from xfr where zone = '%zone%' and client = '%client%'}";
>>   };
>>   };
>>   Now I am seeing a different problem.  Whenever I query our domain
>>   ([1]boingo.com) I get my [2]ns1.boingo.com nameserver listed twice.  I am
>>     
>
> If you're returning the NS info in two different places, it makes sense,
> but I'm not authoritative if this is FAQ type behavior or not.
>
> The docs online specifically say this about the "authority query" when
> using the separate query format:
>     This query should be used to return NS and SOA records if the lookup
>     query does not. If the lookup query will return NS and SOA records,
>     DO NOT USE an authority query, as it will cause errors!
>
> Take a look at the webpage again and compare your config to the sample,
> you are very nearly identical to it.
>     http://bind-dlz.sourceforge.net/mysql_driver.html
> Also read very closely the paragraphs that talk about the lookup and
> authority queries (aka the Red and Green sql queries in that webpage)
> from where I pasted the quote above.
> - -- 
> Regards...		Todd
> I've visited conferences where the wireless LAN was deemed "secure" by
> the organisation because they had outlawed sniffers.    --Neils Bakker
> Linux kernel 2.6.22-14-generic  11 users,  load average: 0.00, 0.03, 0.00
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFIDl7EY2VBGxIDMLwRAp3jAJ9nRiBR5HMyaZLKlH4LfT1Fcv0l4QCZAU3t
> Kpz1BqxxyjENHCvgqpXEtDE=
> =6IXz
> -----END PGP SIGNATURE-----
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
> Don't miss this year's exciting event. There's still time to save $100. 
> Use priority code J8TL2D2. 
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> _______________________________________________
> Bind-dlz-testers mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/bind-dlz-testers
>
>   
That was the issue.  It was returning SOA and NS in too many places.  
Fixed in SQL.  Thank you for the help.

Michael

-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone