Doing first time the RFC 2317 style subnet reverse DNS, and have a
problem with recursion. When doing a query like dig @ns1.qnet.fi -x
62.142.217.200 is succeeds from the local network, but outside I get
recursion requested but not available. Our /24 reverse zones work
fine, the server knows
Is there a patch for bind 9 to add new zones dynamically without
having to run rndc reconfig?
This feature is being added in BIND 9.7.2. It's available now in the beta
version, 9.7.2b1.
--
Evan Hunt -- e...@isc.org
Internet Systems Consortium, Inc.
On 07/29/2010 08:58 AM, Jukka Pakkanen wrote:
Doing first time the RFC 2317 style subnet reverse DNS, and have a
problem with recursion. When doing a query like dig @ns1.qnet.fi -x
62.142.217.200 is succeeds from the local network, but outside I get
recursion requested but not available. Our
29.7.2010 11:29, Phil Mayers kirjoitti:
On 07/29/2010 08:58 AM, Jukka Pakkanen wrote:
Doing first time the RFC 2317 style subnet reverse DNS, and have a
problem with recursion. When doing a query like dig @ns1.qnet.fi -x
62.142.217.200 is succeeds from the local network, but outside I get
On 29/07/10 10:00, Jukka Pakkanen wrote:
29.7.2010 11:29, Phil Mayers kirjoitti:
On 07/29/2010 08:58 AM, Jukka Pakkanen wrote:
Doing first time the RFC 2317 style subnet reverse DNS, and have a
problem with recursion. When doing a query like dig @ns1.qnet.fi -x
62.142.217.200 is succeeds from
I am out of the office until 08/02/2010.
I am currently out of the office. If you need Unix Admin assistance please
contact USW_21st_PLD-UnixAdmins for assistance.
Note: This is an automated response to your message bind-users Digest,
Vol 589, Issue 2 sent on 7/29/2010 3:45:51 AM.
This
29.7.2010 13:45, Phil Mayers kirjoitti:
On 29/07/10 10:00, Jukka Pakkanen wrote:
29.7.2010 11:29, Phil Mayers kirjoitti:
On 07/29/2010 08:58 AM, Jukka Pakkanen wrote:
Doing first time the RFC 2317 style subnet reverse DNS, and have a
problem with recursion. When doing a query like dig
I know BIND does not currently support multi-master. And I understand that
trying to strap together my own pseudo-multi-master implementation using
BIND, bubble gum, and tape isn't a sustainable solution. But, nevertheless,
I don't really need a true multi-master implementation -- I just need
In message 4c5134af.2080...@qnet.fi, Jukka Pakkanen writes:
Doing first time the RFC 2317 style subnet reverse DNS, and have a
problem with recursion. When doing a query like dig @ns1.qnet.fi -x
62.142.217.200 is succeeds from the local network, but outside I get
recursion requested but
On 2010-07-29 09:58, Jukka Pakkanen wrote
Recursion is only allowed for the local networks, but why the server
thinks recursion is needed in the first place?
Because it is: dig -x looks for 200.217.142.62.in-addr.arpa.
Your server is not a master for this zone; instead it's master for
29.7.2010 14:23, Mark Andrews kirjoitti:
In message4c5134af.2080...@qnet.fi, Jukka Pakkanen writes:
Doing first time the RFC 2317 style subnet reverse DNS, and have a
problem with recursion. When doing a query like dig @ns1.qnet.fi -x
62.142.217.200 is succeeds from the local network, but
29.7.2010 14:26, Niobos kirjoitti:
On 2010-07-29 09:58, Jukka Pakkanen wrote
Recursion is only allowed for the local networks, but why the server
thinks recursion is needed in the first place?
Because it is: dig -x looks for 200.217.142.62.in-addr.arpa.
Your server is not a master
On 29/07/10 12:34, Jukka Pakkanen wrote:
29.7.2010 14:23, Mark Andrews kirjoitti:
In message4c5134af.2080...@qnet.fi, Jukka Pakkanen writes:
Doing first time the RFC 2317 style subnet reverse DNS, and have a
problem with recursion. When doing a query like dig @ns1.qnet.fi -x
62.142.217.200
29.7.2010 14:50, Phil Mayers kirjoitti:
On 29/07/10 12:34, Jukka Pakkanen wrote:
29.7.2010 14:23, Mark Andrews kirjoitti:
In message4c5134af.2080...@qnet.fi, Jukka Pakkanen writes:
Doing first time the RFC 2317 style subnet reverse DNS, and have a
problem with recursion. When doing a query
One solution that was floated recently around here was to use dynamically
loaded zones (http://bind-dlz.sourceforge.net/) with an underlying storage
mechanism that does bidirectional replication (a directory service like LDAP
or a database) for the masters, this way, whichever one gets the update,
In message 4c516756.5060...@qnet.fi, Jukka Pakkanen writes:
29.7.2010 14:23, Mark Andrews kirjoitti:
In message4c5134af.2080...@qnet.fi, Jukka Pakkanen writes:
Doing first time the RFC 2317 style subnet reverse DNS, and have a
problem with recursion. When doing a query like dig
On 07/29/2010 01:38 PM, bind-users-requ...@lists.isc.org wrote:
Date: Thu, 29 Jul 2010 14:38:20 +0300
From: Jukka Pakkanenjukka.pakka...@qnet.fi
Subject: Re: Subnet reverse delagation, RFC 2317
To:bind-users@lists.isc.org
Message-ID:4c51682c.3080...@qnet.fi
Content-Type: text/plain;
Hello Dave Sparro,
Am 2010-07-28 10:11:52, hacktest Du folgendes herunter:
That host name does show up in your e-mail headers. That may
be why there are some people curious about that host name.
On 28.07.10 23:24, Michelle Konzack wrote:
But why do they query my server 3 times per
In message 4c516d09.7080...@qnet.fi, Jukka Pakkanen writes:
29.7.2010 14:50, Phil Mayers kirjoitti:
On 29/07/10 12:34, Jukka Pakkanen wrote:
29.7.2010 14:23, Mark Andrews kirjoitti:
In message4c5134af.2080...@qnet.fi, Jukka Pakkanen writes:
Doing first time the RFC 2317 style subnet
29.7.2010 15:10, Mark Andrews kirjoitti:
In message4c516756.5060...@qnet.fi, Jukka Pakkanen writes:
29.7.2010 14:23, Mark Andrews kirjoitti:
In message4c5134af.2080...@qnet.fi, Jukka Pakkanen writes:
Doing first time the RFC 2317 style subnet reverse DNS, and have a
problem
Please everybody just forget the 62.142.220.0/24 network and
62.142.220.5 address, the problem is not about them. It was just to
inform that our servers are doing regular /24 reverse DNS just fine.
The problem is we are trying to set up and administer reverse DNS for
62.142.217.128/25 IP
29.7.2010 15:21, Mark Andrews kirjoitti:
Yeah, this makes sense. But my question still is, what is wrong in our
setup,
!!! NOTHING
Well, then everything is good and I can go to my vacation... hopefully
the clients whose IP addresses
29.7.2010 15:43, Jukka Pakkanen kirjoitti:
Please everybody just forget the 62.142.220.0/24 network and
62.142.220.5 address, the problem is not about them. It was just to
inform that our servers are doing regular /24 reverse DNS just fine.
The problem is we are trying to set up and
Sorry about using 5 instead of something from 128 to 255 in the
examples. That said there is nothing wrong here.
The rest of the world will get the correct answers without recursion
being enabled on that server and it will NEVER be asked the question
you were testing with in normal operation.
29.7.2010 16:00, Mark Andrews kirjoitti:
Sorry about using 5 instead of something from 128 to 255 in the
examples. That said there is nothing wrong here.
Now I can agree :)
However earlier our servers only answered to the local queries about
those IP addresses, started working during
On 2010-07-29 15:00, Jukka Pakkanen wrote:
Anyway we also have 62.142.217.64/27 IP network (you know what I mean)
which should be delegated to our servers, but that still doesn't work.
But it's probably a delegation problem.
From my point of view, 62.142.217.64 is served by ns3.sci.fi (and its
29.7.2010 17:06, Niobos kirjoitti:
On 2010-07-29 15:00, Jukka Pakkanen wrote:
Anyway we also have 62.142.217.64/27 IP network (you know what I mean)
which should be delegated to our servers, but that still doesn't work.
But it's probably a delegation problem.
From my point of view,
Hello Matus UHLAR - fantomas,
Am 2010-07-29 14:12:54, hacktest Du folgendes herunter:
On 28.07.10 23:24, Michelle Konzack wrote:
But why do they query my server 3 times per second?
deep parsing of e-mail headers by spam filtering software, I guess.
Which is the last crap!
Spamassassin does
Am 2010-07-29 14:12:54, hacktest Du folgendes herunter:
On 28.07.10 23:24, Michelle Konzack wrote:
But why do they query my server 3 times per second?
Hello Matus UHLAR - fantomas,
deep parsing of e-mail headers by spam filtering software, I guess.
On 29.07.10 19:16, Michelle Konzack
Hello Matus UHLAR - fantomas,
Am 2010-07-29 19:37:50, hacktest Du folgendes herunter:
apparently internal_networks set up incorrectly?
No it is the problem if a customer connect trough a VPN to the Router of
the employer/enterprise and send out messages using the the companys own
mail relay and
On 7/29/2010 2:11 PM, Michelle Konzack wrote:
Hello Matus UHLAR - fantomas,
Your hostname is private and inaccessible from the outside. The requesters
get SERVFAIL reply which apparently makes them retry. If you provided them
any IP address (e.g. 127.0.0.1) they could be satisfied and stop
Alan/ Evan,
Thanks didn't get to reading the beta release notes yet. Wow, how timely is
this :)
Thanks
-m
On Wed, Jul 28, 2010 at 8:08 PM, Alan Clegg acl...@isc.org wrote:
On 7/28/2010 10:41 PM, Mike Flathers wrote:
Is there a patch for bind 9 to add new zones dynamically without
Alan,
I was playing around with your example. I can get it to add the zone ( that is
no rndc errors or syslog messages).
I see it send notifies for the new zone in my log.
29-Jul-2010 23:06:47.063 notify: info: zone exampledomain.com/IN: sending
notifies (serial 12)
I also added the global
On 7/29/2010 7:19 PM, Dan Durrer wrote:
Alan,
I was playing around with your example. I can get it to add the zone
( that is no rndc errors or syslog messages).
I see it send notifies for the new zone in my log.
29-Jul-2010 23:06:47.063 notify: info: zone exampledomain.com/IN:
sending
Alan,
So is managed.zone.list and zone.list named differently on purpose or is that
a typo?
Dan
On Jul 29, 2010, at 5:23 PM, Alan Clegg acl...@isc.org wrote:
On 7/29/2010 7:19 PM, Dan Durrer wrote:
Alan,
I was playing around with your example. I can get it to add the zone
( that is
On 7/29/2010 5:38 PM, Jack Tavares wrote:
Will this functionality be available through an api?
Or will it just be through rndc ?
Not sure what API we would use beyond rndc. If you have
recommendations, please e-mail me directly or give me a phone call
(+1-919-355-885) and let's talk about
36 matches
Mail list logo
