Re: Zonefiles & CIDR
On Sun, Mar 08, 2009 at 10:20:26AM +, Stephen Ward wrote a message of 11 lines which said: > Running BIND9 (someone kindly raped to get it to work on windows) > but it does not seem to support CIDR ranges. Nothing to do with BIND, it is a limitation of the DNS. > Rather than have to enter loads of lines to match up wide spans of > ranges It is three or four lines of Perl, Python or Ruby... ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: RHEL and named with DLZ
On Thu, Mar 05, 2009 at 09:47:07PM -0800, Scott Haneda wrote:
> Hello, I am trying to get named with DLZ on RHEL.
>
> My build line is below, I can start named, and I have base configured it
> so that it will return a lookup for `dig example.com @localhost +norec`
> which returns a custom IP I put in to make sure it is really working.
>
> So far, I know named is working.
>
> I added in dlz "Mysql zone" { ... }
>
> rndc and restarting named all work fine, no errors that I can see. But
> in a successful build on OS X, I was getting a line in the log for named
> that said"
> 'Mysql zone' using driver mysql
>
> I do not get that on RHEL, and I am not getting answers back for my test
> zones I have in the database. MySql is running, I know that much.
>
> Any suggestions?
BIND in RHEL5 is based on 9.3 series and DLZ stuff has been merged in
9.4 development cycle. It is impossible to get DLZ working with bind
package that is shipped in RHEL5.
Could I ask you why you can't use SDB, please?
Regards, Adam
--
Adam Tkac, Red Hat, Inc.
___
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
How do i use å ä ö in domain names?
Hi. This is our scandinavian chars, how do i implement them on our internal server (bind 9.5P1)? Tried to find info on this and failed.. thx. p ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: How do i use å ä ö in domain names?
Piero Giobbi wrote: This is our scandinavian chars, how do i implement them on our internal server (bind 9.5P1)? Tried to find info on this and failed.. http://www.iis.se/domains/IDN/FAQidn -- Christian Laursen ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: RHEL and named with DLZ
On Mar 9, 2009, at 2:40 AM, Adam Tkac wrote:
On Thu, Mar 05, 2009 at 09:47:07PM -0800, Scott Haneda wrote:
Hello, I am trying to get named with DLZ on RHEL.
My build line is below, I can start named, and I have base
configured it
so that it will return a lookup for `dig example.com @localhost
+norec`
which returns a custom IP I put in to make sure it is really working.
So far, I know named is working.
I added in dlz "Mysql zone" { ... }
rndc and restarting named all work fine, no errors that I can see.
But
in a successful build on OS X, I was getting a line in the log for
named
that said"
'Mysql zone' using driver mysql
I do not get that on RHEL, and I am not getting answers back for my
test
zones I have in the database. MySql is running, I know that much.
Any suggestions?
BIND in RHEL5 is based on 9.3 series and DLZ stuff has been merged in
9.4 development cycle. It is impossible to get DLZ working with bind
package that is shipped in RHEL5.
Could I ask you why you can't use SDB, please?
Regards, Adam
--
Adam Tkac, Red Hat, Inc.
Adam, I believe I used you srpm for bind. people.redhat.com/atkac or
soemthing like it. If that's you, thank you.
I didn't confirm this by trying it, but I read in numerous places that
the current RHEL5 bind didn't work with mysql.
Can anyone that the current RHEL bind-sdb does work with mysql?
If I go to isc.org the most prominant download links I find are for
BIND 9.6.0-P1.
I didn't find at isc.org where they state which version is recommended.
Does anyone know where to find this information?
Thank you,
Brad
___
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
Re: Zonefiles & CIDR
On Sun, 08 Mar 2009 21:28:55 -0500, Frank Bulk wrote: > There are other DNS servers that do a better job for RBLs. > > Frank I'm listening. Replica Watches - TRY LIDL - Cheap meds? Visit your GP -- . . . ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: Zonefiles & CIDR
Stephen Ward wrote: > On Sun, 08 Mar 2009 21:28:55 -0500, Frank Bulk wrote: > >> There are other DNS servers that do a better job for RBLs. >> >> Frank > > I'm listening. Take a look at rbldnsd: http://www.corpit.ru/mjt/rbldnsd.html Bill ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
RE: Zonefiles & CIDR
The other package would be djbdns, which has rbldns in it. Frank -Original Message- From: bind-users-boun...@lists.isc.org [mailto:bind-users-boun...@lists.isc.org] On Behalf Of Stephen Ward Sent: Monday, March 09, 2009 2:50 PM To: comp-protocols-dns-b...@isc.org Subject: Re: Zonefiles & CIDR On Sun, 08 Mar 2009 21:28:55 -0500, Frank Bulk wrote: > There are other DNS servers that do a better job for RBLs. > > Frank I'm listening. Replica Watches - TRY LIDL - Cheap meds? Visit your GP -- . . . ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
bind-9.5.1-1.P1 -- identicle zone listing and data file in different views, but doesn't work
Been looking at this for hours and can't figure it out. Views without recursion
don't return a response. I don't know what I'm doing wrong. Setting
"recursion yes" allows the zone to respond.
Sorry if this format is ugly.
Ideas?
Thanks!
>>named.conf
view "internal"
{
match-clients { !192.168.184.44; !192.168.184.46;
franklin_way_nets; localnets; localhost; };
match-destinations { !192.168.184.43; !192.168.184.45; any;};
recursion yes;
include "/etc/named.root.hints";
zone "128/27.168.193.66.in-addr.arpa" {
type master;
file "66.193.168.0.rev.db";
allow-query { any; };
allow-transfer { slaves; };
};
view"comcast"
{
match-clients { any; };
match-destinations { 192.168.184.43; };
recursion yes;
include "/etc/named.root.hints";
zone "128/27.168.193.66.in-addr.arpa" {
type master;
file "66.193.168.0.rev.comcast.db";
allow-query { any; };
allow-transfer { slaves; };
};
>/var/log/messages
Mar 9 17:03:57 w1 named[14663]: zone
128/27.168.193.66.in-addr.arpa/IN/internal: loaded serial 2008120901
Mar 9 17:03:58 w1 named[14663]: zone
128/27.168.193.66.in-addr.arpa/IN/timewarner: loaded serial 2008120901
Mar 9 17:03:58 w1 named[14663]: zone
128/27.168.193.66.in-addr.arpa/IN/comcast: loaded serial 2008120901
>named.run
zone 128/27.168.193.66.in-addr.arpa/IN/comcast: starting load
zone 128/27.168.193.66.in-addr.arpa/IN/comcast: number of nodes in database: 31
no journal file, but that's OK
zone 128/27.168.193.66.in-addr.arpa/IN/comcast: journal rollforward completed
successfully: no journal
zone 128/27.168.193.66.in-addr.arpa/IN/comcast: loaded
zone 128/27.168.193.66.in-addr.arpa/IN/comcast: loaded serial 2008120901
>named.run
client 67.35.22.236#47252: UDP request
client 67.35.22.236#47252: view comcast: using view 'comcast'
client 67.35.22.236#47252: view comcast: request is not signed
client 67.35.22.236#47252: view comcast: recursion not available
client 67.35.22.236#47252: view comcast: query
client 67.35.22.236#47252: view comcast: query (cache)
'130.168.193.66.in-addr.arpa/PTR/IN' approved
client 67.35.22.236#47252: view comcast: send
client 67.35.22.236#47252: view comcast: sendto
client 67.35.22.236#47252: view comcast: senddone
client 67.35.22.236#47252: view comcast: next
client 67.35.22.236#47252: view comcast: endrequest
client @0xb589d008: udprecv
client @0xb5c87008: udprecv
client 192.168.186.6#4399: UDP request
client 192.168.186.6#4399: view comcast: using view 'comcast'
client 192.168.186.6#4399: view comcast: request is not signed
client 192.168.186.6#4399: view comcast: recursion available
client 192.168.186.6#4399: view comcast: query
client 192.168.186.6#4399: view comcast: query (cache)
'130.168.193.66.in-addr.arpa/PTR/IN' approved
client 192.168.186.6#4399: view comcast: query
'130.128/27.168.193.66.in-addr.arpa/PTR/IN' approved
client 192.168.186.6#4399: view comcast: send
client 192.168.186.6#4399: view comcast: sendto
client 192.168.186.6#4399: view comcast: senddone
client 192.168.186.6#4399: view comcast: next
client 192.168.186.6#4399: view comcast: endrequest
___
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
