Re: Problems in compiling bind

If I'm not mistaken, those came with the bind package as distributed
by RedHat.  I just took the srpm with an older version, adjusted it to
use the newer version, adjusted the build process (removed some
patches), and built the newer version.

These are standard basic configs that should be present in your
nameservers so that your nameservers don't recurse all the way up to
the root nameservers for these local configurations.  Refer to chapter
4 of RFC 1912 if you want more (than you want) detail.

...Todd

2012/2/25 Nitish Bangera <[email protected]>:
> Hello Todd,
>
> I am really thankfull to your advices as it has helped me a lot. But, i k=
ind
> of new to Bind and do not understand what's written in the rfc files. If =
you
> can please explain it in detail then i would be really grateful. Hope i am
> causing too much of a hassle to you.
>
> Thanks,
> Nitish
>
> 2012/2/24 Todd Lyons <[email protected]>
>>
>> My apologies for the formatting, but I wanted to keep the long lines from
>> wrapping.=A0 If you don't like rich text, feel free to delete this email.
>>
>> 2012/2/23 Nitish Bangera <[email protected]>:
>>
>> > Hey Todd,
>> >
>> > Thanks for the advice. Changing the path name from /usr/lib to
>> > /usr/lib64 in
>> > configure worked like a gem. Now i am wondering where exactly the
>> > configs to
>> > connect to the mysql database should be put in.
>>
>> In your named.conf.
>>
>> You can also mix regular zones with DLZ zones if you choose to. =A0For
>> example:
>> /etc/named.conf:
>> logging {
>> =A0 =A0 =A0 =A0channel default_debug {
>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0file "/var/log/named.debug";
>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0severity info;
>> =A0 =A0 =A0 =A0};
>> };
>>
>> zone "." IN {
>> =A0 =A0 =A0 =A0type hint;
>> =A0 =A0 =A0 =A0file "named.ca";
>> };
>>
>> include "/etc/named.rfc1912.zones";
>> include "/etc/named.dlz";
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
>>
>> /etc/named.dlz:
>> dlz "Mysql zone" {
>> =A0 database "mysql
>> =A0 {host=3Ddb-master user=3Ddomains pass=3D******************** dbname=
=3Dlive_sites
>> ssl=3Dfalse}
>> =A0 {SELECT name FROM domain WHERE name =3D '$zone$' AND active=3D1}
>> =A0 {SELECT '7200' AS ttl,domain_record_type.type,
>> =A0 =A0 =A0 =A0case when lower(domain_record_type.type) =3D 'mx' then
>> domain_record.mx_priority end,
>> =A0 =A0 =A0 =A0case when lower(domain_record_type.type) =3D 'txt' then c=
oncat('\"',
>> domain_record.value, '\"') else domain_record.value end AS data
>> =A0 =A0 =A0 =A0FROM domain_record,domain,domain_record_type
>> =A0 =A0 =A0 =A0WHERE domain_record_type.id=3Ddomain_record.type_id AND
>> domain_record.active=3D1
>> =A0 =A0 =A0 =A0 =A0 =A0AND domain.id=3Ddomain_record.domain_id
>> =A0 =A0 =A0 =A0 =A0 =A0AND domain.name=3D'$zone$'
>> =A0 =A0 =A0 =A0 =A0=A0 AND domain_record.name=3D'$record$'}";
>> };
>>
>> # I use the short form of database lookups since I don't do transfers and
>> such.
>> # That's a personal choice, it's up to you how you configure your system.
>>
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
>>
>> /etc/named.rfc1912.zones:
>> zone "localhost.localdomain" IN {
>> =A0 =A0 =A0 =A0type master;
>> =A0 =A0 =A0 =A0file "named.localhost";
>> =A0 =A0 =A0 =A0allow-update { none; };
>> };
>>
>> zone "localhost" IN {
>> =A0 =A0 =A0 =A0type master;
>> =A0 =A0 =A0 =A0file "named.localhost";
>> =A0 =A0 =A0 =A0allow-update { none; };
>> };
>>
>> zone
>> "1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arp=
a"
>> IN {
>> =A0 =A0 =A0 =A0type master;
>> =A0 =A0 =A0 =A0file "named.loopback";
>> =A0 =A0 =A0 =A0allow-update { none; };
>> };
>>
>> zone "1.0.0.127.in-addr.arpa" IN {
>> =A0 =A0 =A0 =A0type master;
>> =A0 =A0 =A0 =A0file "named.loopback";
>> =A0 =A0 =A0 =A0allow-update { none; };
>> };
>>
>> zone "0.in-addr.arpa" IN {
>> =A0 =A0 =A0 =A0type master;
>> =A0 =A0 =A0 =A0file "named.empty";
>> =A0 =A0 =A0 =A0allow-update { none; };
>> };
>>
>> etc...
>>
>> Regards... =A0 =A0Todd
>>
>>
>> --
>> SOPA: Any attempt to [use legal means to] reverse technological advances
>> is doomed. =A0--Leo Leporte
>>
>>
>>
>> ------------------------------------------------------------------------=
------
>> Virtualization & Cloud Management Using Capacity Planning
>> Cloud computing makes use of virtualization - but cloud computing
>> also focuses on allowing computing to be delivered as a service.
>> http://www.accelacomm.com/jaw/sfnl/114/51521223/
>> _______________________________________________
>> Bind-dlz-testers mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/bind-dlz-testers
>>
>
>
>
> --
> Regards,
> Nitish S. Bangera
>
> -------------------------------------------------------------------------=
-----
> Virtualization & Cloud Management Using Capacity Planning
> Cloud computing makes use of virtualization - but cloud computing
> also focuses on allowing computing to be delivered as a service.
> http://www.accelacomm.com/jaw/sfnl/114/51521223/
> _______________________________________________
> Bind-dlz-testers mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/bind-dlz-testers
>



-- =

SOPA: Any attempt to [use legal means to] reverse technological
advances is doomed. =A0--Leo Leporte

---------------------------------------------------------------------------=
---
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing =

also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/