Re: Core dumps

Thanks.  Does that mean that this is normal and that even a non DLZ  
driven system is doing the same things in the background?  I have a a  
few non DLZ systems in place, with query logging on, and I have never  
seen it do so.

Why would it try so hard to locate a record?  if www.example.com has  
no zone, why not return 0 and move on?

Thanks

P.S. I used this url to translate: http://is.gd/xGHE
I hope it got the most of it correct, seems to actually have done an  
amazing job.

While I can live with this multiple query issue, and learn about it  
later, the main issue is the core dumps and DLZ/SBD going totally deaf  
over time.

On May 7, 2009, at 10:42 PM, Reyner Herrpinark Lugo wrote:

> Así es como trabaja el driver mi amigo. Si su servidor de DNS es  
> autoritario para la zona example.com y posee un registro de tipo A  
> con dato 10.0.0.1:
>
> dig a www.example.com --> se irán cortando porciones del nombre de  
> dominio completo hasta llegar a una zona soportada por la BD de  
> vuestro DNS.
>
> SELECT zone FROM resource_records WHERE zone = 'www.example.com' -->  
> Usted no posee una zona con este nombre, por tanto se retira "www" y  
> se repite la consulta;
> SELECT zone FROM resource_records WHERE zone = 'example.com' -->  
> Usted sí posee una zona con este nombre, por tanto esta zona pasa a  
> ser reemplazada en las restantes consultas por el token %zone% y www  
> será reemplazado en las mismas restantes consultas por el token  
> %record%.

-- 
Scott * If you contact me off list replace talklists@ with scott@ *


------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com