patch adding tags into named.conf

Hi everybody 
I propose to you a simple patch.
This patch adds extended tags into named.conf.
I have added two tags : %zone_tld% and %zone_domain%.
%zone_tld% contains the TLD into a request (com, net, for example)
%zone_domain%. contains ... the domain   without tld, of course
Some config separate tld and domain in database.
Using Concat on multiple tables can provoke a slowdown. :-\

Tested under DLZ 0.7.0 and Ctrix 9.3.1-1

It's not a perfect patch :)
I wait for any suggestion  :-P

See'ya
--

-- 

--
Benjamin GIGON
benjamin#gigon.org

RE: Normal zone update support by DLZ?

RE: Normal zone update support by DLZ?

I don't know what an "enum" service is.  I've never
heard of that in regards to DNS servers or Bind.

As for updates and DLZ, the software currently does
not support rfc-2136 Dynamic DNS updates.  However,
you can still use "normal" bind zone files for domains
that need dynamic updates, and use DLZ for all the
other domains.  I.E. if you have a DHCP server and
your zone is example.com, create a zone for
dhcp.example.com and use a normal zone file for that. 
Then let DLZ manage the example.com zone and delegate
to the sub-zone of dhcp.example.com.  In this way you
can still use dynamic update and dlz together.

DLZ also does not support notifications.  I.E. when
you update a zone in a "normal" zone file via dynamic
dns, the DNS server will send out a notify message so
slaves can pickup the changes immediately.  DLZ
doesn't do this if you update it's database, it has no
way of telling that the database has been updated.  If
you need a capability like that, have your database
(using a trigger) send a notify message to your slave
servers.

Slave servers can still perform an AXFR to DLZ
servers, so zone transfer is supported.  Thus, if you
manually notify your slave server or the timeout
expires and the slave queries the master it will get
the updated information as normal.  DLZ also does not
currently support ixfr or incremental zone transfer. 
In order to do this DLZ would need to know what the
previous state of the data in the database was, and
currently it has no way of knowing that either.  Any
ixfr request is upgraded to a full axfr request as
allowed by the DNS RFC's.

Hope this helps.
Rob

--- "Li Bin, SLC COM CD/MN R&D SE (BJ)"
<bin_li <at> siemens.com> wrote:

>  In our solutions, one Primary ENUM (BIND9 with DLZ)
> server will access
> Oracel database via ODBC, but we do not want change
> all exist secondary
> ENUM server at all, means the zone update between
> primary and secondary
> will keep the normal DNS zone update procedure. So,
> following is
> question:
>  
> 1. DLZ for BIND9 also support ENUM service without
> modification?
> 2. could the original zone update between primary
> and secondary server
> could be executed correct without severity impact? I
> mean in normal zone
> update, zone file should be checked by BIND, update
> is start if zone
> file has change, now all zone files are in a
> database file, do DLZ also
> check the database change to start the automatic
> zone update? thanks
> lot.
>  
>                                            Best
> Regards 
> 
>  
> 
> L i   B i n 
> Siemens Ltd., China 
> SLC COM CD/MN R&D SE 
> 
> A202, Building No.1, ZGC Software Park
> 
> No.8, DongBeiWang XiLu, HaiDian District, Beijing
> 100094
> 
> Tel in Munchen: +498963644600
> 
> Tel.: +8610 64768834 
> Fax: +8610 64733786 
> E-mail: bin_li <at> siemens.com
> 
>  
> 

		
__________________________________ 
Start your day with Yahoo! - Make it your home page! 
http://www.yahoo.com/r/hs

-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click

RE: Normal zone update support by DLZ?

Thanks your reply, the DNS ENUM service is defined in RFC3761, used for storage E.164 numbers. It is useful
if a tele call from PSTN network to IP network, DNS ENUM will translate the E.164 number to the domain name of
terminal in IP network, normally BIND9 already support this ENUM function. So if DLZ inherit all the
existing BIND9 feature, then should no change on ENUM service also.

Following is my understanting for DLZ solution for our application according your reply, it is correctly?

1. zone transfer supported, means slave server(normal BIND9) send request to master server (DLZ), then
DLZ push AXFR zone files.
2. DLZ do not support notify, this would solve by shorten interval time of slave server send zone transfer
request, but would impact the master performance.
3. DLZ do not support dynamic DNS update procedure, but we can soluve it by sub-domain with plain text zone
file with normal DNS update procedure.

B.R.
LiBin

-----Original Message-----
From: bind-dlz-testers-admin <at> lists.sourceforge.net
[mailto:bind-dlz-testers-admin <at> lists.sourceforge.net] On Behalf Of Rob Butler
Sent: 2005年12月5日 14:48
To: bind-dlz-testers <at> lists.sourceforge.net
Subject: RE: [Bind-dlz-testers] Normal zone update support by DLZ?

I don't know what an "enum" service is.  I've never
heard of that in regards to DNS servers or Bind.

As for updates and DLZ, the software currently does
not support rfc-2136 Dynamic DNS updates.  However,
you can still use "normal" bind zone files for domains
that need dynamic updates, and use DLZ for all the
other domains.  I.E. if you have a DHCP server and
your zone is example.com, create a zone for
dhcp.example.com and use a normal zone file for that. 
Then let DLZ manage the example.com zone and delegate
to the sub-zone of dhcp.example.com.  In this way you
can still use dynamic update and dlz together.

DLZ also does not support notifications.  I.E. when
you update a zone in a "normal" zone file via dynamic
dns, the DNS server will send out a notify message so
slaves can pickup the changes immediately.  DLZ
doesn't do this if you update it's database, it has no
way of telling that the database has been updated.  If
you need a capability like that, have your database
(using a trigger) send a notify message to your slave
servers.

Slave servers can still perform an AXFR to DLZ
servers, so zone transfer is supported.  Thus, if you
manually notify your slave server or the timeout
expires and the slave queries the master it will get
the updated information as normal.  DLZ also does not
currently support ixfr or incremental zone transfer. 
In order to do this DLZ would need to know what the
previous state of the data in the database was, and
currently it has no way of knowing that either.  Any
ixfr request is upgraded to a full axfr request as
allowed by the DNS RFC's.

Hope this helps.
Rob

--- "Li Bin, SLC COM CD/MN R&D SE (BJ)"
<bin_li <at> siemens.com> wrote:

>  In our solutions, one Primary ENUM (BIND9 with DLZ)
> server will access
> Oracel database via ODBC, but we do not want change
> all exist secondary
> ENUM server at all, means the zone update between
> primary and secondary
> will keep the normal DNS zone update procedure. So,
> following is
> question:
>  
> 1. DLZ for BIND9 also support ENUM service without
> modification?
> 2. could the original zone update between primary
> and secondary server
> could be executed correct without severity impact? I
> mean in normal zone
> update, zone file should be checked by BIND, update
> is start if zone
> file has change, now all zone files are in a
> database file, do DLZ also
> check the database change to start the automatic
> zone update? thanks
> lot.
>  
>                                            Best
> Regards 
> 
>  
> 
> L i   B i n 
> Siemens Ltd., China 
> SLC COM CD/MN R&D SE 
> 
> A202, Building No.1, ZGC Software Park
> 
> No.8, DongBeiWang XiLu, HaiDian District, Beijing
> 100094
> 
> Tel in Munchen: +498963644600
> 
> Tel.: +8610 64768834 
> Fax: +8610 64733786 
> E-mail: bin_li <at> siemens.com
> 
>  
> 

		
__________________________________ 
Start your day with Yahoo! - Make it your home page! 
http://www.yahoo.com/r/hs

-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bind-dlz-testers mailing list
Bind-dlz-testers <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bind-dlz-testers

-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click

RE: Normal zone update support by DLZ?

Yes, all 3 items correct.  And as for DNS ENUM, I
never heard of it referred to by that name before, but
I have had others contact me about E.164 support.  DLZ
does work with E.164 records.

Later
Rob

--- "Li Bin, SLC COM CD/MN R&D SE (BJ)"
<bin_li <at> siemens.com> wrote:

> Thanks your reply, the DNS ENUM service is defined
> in RFC3761, used for storage E.164 numbers. It is
> useful if a tele call from PSTN network to IP
> network, DNS ENUM will translate the E.164 number to
> the domain name of terminal in IP network, normally
> BIND9 already support this ENUM function. So if DLZ
> inherit all the existing BIND9 feature, then should
> no change on ENUM service also.
> 
> Following is my understanting for DLZ solution for
> our application according your reply, it is
> correctly?
> 
> 1. zone transfer supported, means slave
> server(normal BIND9) send request to master server
> (DLZ), then DLZ push AXFR zone files.
> 2. DLZ do not support notify, this would solve by
> shorten interval time of slave server send zone
> transfer request, but would impact the master
> performance.
> 3. DLZ do not support dynamic DNS update procedure,
> but we can soluve it by sub-domain with plain text
> zone file with normal DNS update procedure.
> 
> 
> B.R.
> LiBin
> 
> -----Original Message-----
> From: bind-dlz-testers-admin <at> lists.sourceforge.net
>
[mailto:bind-dlz-testers-admin <at> lists.sourceforge.net]
> On Behalf Of Rob Butler
> Sent: 2005ǯ12·î5Æü 14:48
> To: bind-dlz-testers <at> lists.sourceforge.net
> Subject: RE: [Bind-dlz-testers] Normal zone update
> support by DLZ?
> 
> I don't know what an "enum" service is.  I've never
> heard of that in regards to DNS servers or Bind.
> 
> As for updates and DLZ, the software currently does
> not support rfc-2136 Dynamic DNS updates.  However,
> you can still use "normal" bind zone files for
> domains
> that need dynamic updates, and use DLZ for all the
> other domains.  I.E. if you have a DHCP server and
> your zone is example.com, create a zone for
> dhcp.example.com and use a normal zone file for
> that. 
> Then let DLZ manage the example.com zone and
> delegate
> to the sub-zone of dhcp.example.com.  In this way
> you
> can still use dynamic update and dlz together.
> 
> DLZ also does not support notifications.  I.E. when
> you update a zone in a "normal" zone file via
> dynamic
> dns, the DNS server will send out a notify message
> so
> slaves can pickup the changes immediately.  DLZ
> doesn't do this if you update it's database, it has
> no
> way of telling that the database has been updated. 
> If
> you need a capability like that, have your database
> (using a trigger) send a notify message to your
> slave
> servers.
> 
> Slave servers can still perform an AXFR to DLZ
> servers, so zone transfer is supported.  Thus, if
> you
> manually notify your slave server or the timeout
> expires and the slave queries the master it will get
> the updated information as normal.  DLZ also does
> not
> currently support ixfr or incremental zone transfer.
> 
> In order to do this DLZ would need to know what the
> previous state of the data in the database was, and
> currently it has no way of knowing that either.  Any
> ixfr request is upgraded to a full axfr request as
> allowed by the DNS RFC's.
> 
> Hope this helps.
> Rob
> 
> --- "Li Bin, SLC COM CD/MN R&D SE (BJ)"
> <bin_li <at> siemens.com> wrote:
> 
> >  In our solutions, one Primary ENUM (BIND9 with
> DLZ)
> > server will access
> > Oracel database via ODBC, but we do not want
> change
> > all exist secondary
> > ENUM server at all, means the zone update between
> > primary and secondary
> > will keep the normal DNS zone update procedure.
> So,
> > following is
> > question:
> >  
> > 1. DLZ for BIND9 also support ENUM service without
> > modification?
> > 2. could the original zone update between primary
> > and secondary server
> > could be executed correct without severity impact?
> I
> > mean in normal zone
> > update, zone file should be checked by BIND,
> update
> > is start if zone
> > file has change, now all zone files are in a
> > database file, do DLZ also
> > check the database change to start the automatic
> > zone update? thanks
> > lot.
> >  
> >                                            Best
> > Regards 
> > 
> >  
> > 
> > L i   B i n 
> > Siemens Ltd., China 
> > SLC COM CD/MN R&D SE 
> > 
> > A202, Building No.1, ZGC Software Park
> > 
> > No.8, DongBeiWang XiLu, HaiDian District, Beijing
> > 100094
> > 
> > Tel in Munchen: +498963644600
> > 
> > Tel.: +8610 64768834 
> > Fax: +8610 64733786 
> > E-mail: bin_li <at> siemens.com
> > 
> >  
> > 
> 
> 
> 
> 		
> __________________________________ 
> Start your day with Yahoo! - Make it your home page!
> 
> http://www.yahoo.com/r/hs
> 
> 
>
-------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do
> you grep through log files
> for problems?  Stop!  Download the new AJAX search
> engine that makes
> searching your log files as easy as surfing the 
> web.  DOWNLOAD SPLUNK!
>
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
> _______________________________________________
> Bind-dlz-testers mailing list
> Bind-dlz-testers <at> lists.sourceforge.net
>
https://lists.sourceforge.net/lists/listinfo/bind-dlz-testers
> 
> 
>
-------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do
> you grep through log files
> for problems?  Stop!  Download the new AJAX search
> engine that makes
> searching your log files as easy as surfing the 
> web.  DOWNLOAD SPLUNK!
>
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
> _______________________________________________
> Bind-dlz-testers mailing list
> Bind-dlz-testers <at> lists.sourceforge.net
>
https://lists.sourceforge.net/lists/listinfo/bind-dlz-testers
> 

		
__________________________________________ 
Yahoo! DSL – Something to write home about. 
Just $16.99/mo. or less. 
dsl.yahoo.com 

-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click

zone is appended to the end of SOA objects

Why is the zone appended to the end of the origin and mail_addr objects?
Looking at the output of the query it's not there.

example.com
  origin = ns1.example.com.example.com
  mail addr = test\ <at> example.com.example.com
  serial = 2005122101
  refresh = 500
  retry = 600
  expire = 700
  minimum = 800

Running on BIND-9.3.1, DLZ-0.7.0

Here is the query used:

dlz "Mysql zone" {
   database "mysql
   {host=munged user=munged password=munged dbname=munged ssl=true}
   {select zone from tbl_dns_records where zone = '%zone%'}
   {select ttl, type, mx_priority, case when lower(type)='txt' then
concat('\"', data, '\"')
        when lower(type) = 'soa' then concat_ws(' ', primary_ns,
resp_person, serial, refresh, retry, expire, minimum)
        else data end from tbl_dns_records where zone = '%zone%' and host =
'%record%'}";
};

Thanks,
Nicklas B

-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click

Re: zone is appended to the end of SOA objects

On Wed 21 Dec 2005 11:52:23 GMT , Nicklas Bondesson 
<nicklas.bondesson <at> mindping.com> wrote:
> Why is the zone appended to the end of the origin and mail_addr objects?
> Looking at the output of the query it's not there.
<snip>

Because you're not terminating the data in the appropriate fields with 
a period. Your client then appends the local $ORIGIN value to the 
returned data.

Ensure that your primary nameserver and responsible person data are 
terminated with a period.

Graeme

-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click

RE: zone is appended to the end of SOA objects

> On Wed 21 Dec 2005 11:52:23 GMT , Nicklas Bondesson 
> <nicklas.bondesson <at> mindping.com> wrote:
> > Why is the zone appended to the end of the origin and 
> mail_addr objects?
> > Looking at the output of the query it's not there.
> <snip>
> 
> Because you're not terminating the data in the appropriate 
> fields with a period. Your client then appends the local 
> $ORIGIN value to the returned data.
> 
> Ensure that your primary nameserver and responsible person 
> data are terminated with a period.
> 
> Graeme
> 

Thanks! Just like in regular BIND you have to end it with a period.

Nicklas B

-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click

RE: zone is appended to the end of SOA objects

On Wed 21 Dec 2005 12:04:22 GMT , Nicklas Bondesson 
<nicklas.bondesson <at> mindping.com> wrote:
> Thanks! Just like in regular BIND you have to end it with a period.

Yes.

In fact, everything about the data BIND-DLZ serves has to "be like 
regular BIND" (or djbdns, or MS DNS) because it is in fact delivering 
data which must conform to an Internet Standard - see RFC1035 et al.

Graeme

-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click

Seperated data in two tables

Does anyone use DLZ with the data seperated in two tables?

I'd like to have all the SOA records in one table, and all the others (NS,
A, PTR, etc) in a seperate table.

Examples are welcomed.

Thanks,
Nicklas B

-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click