Guys,
We have upgraded our customer caching name servers to pdns recursor 3.2
(which is working very well), this has now been running for 4 days but
in the last 24 hours we have seen the tcp listener stop answering
queries on 2 seperate servers. Our monitoring servers flag this up for
us
Hi,
I have the following zone 79.73.217.in-addr.arpa with the NS set as my 2
name servers.
What i want to do is just forward reverse dns requests for
217.73.79.224/28 to another name server. What would be the best way to
go about this?
Thanks
You mean delegating a subnet to another nameserver? This may help:
http://www.zytrax.com/books/dns/ch3/#reverse
On 03/25/2010 05:53 PM, Athiqur Rahman wrote:
Hi,
I have the following zone 79.73.217.in-addr.arpa with the NS set as my 2
name servers.
What i want to do is just forward reverse
Looking at the link below. It looks like that I will have to create
CNAME entry for every IP in the /28 subnet, That is 16 CNAME entries?
The nameserver that I am sending to will have to create a zone record
called 224/28.79.73.217.in-addr.arpa?
I am thinking do I have to define the rest of
Le Thu, 25 Mar 2010 15:51:29 +
Simon Bedford sbedf...@plus.net écrit:
Guys,
We have upgraded our customer caching name servers to pdns recursor 3.2
(which is working very well), this has now been running for 4 days but
in the last 24 hours we have seen the tcp listener stop answering
On 3/25/10 9:50 AM, Athiqur Rahman wrote:
Looking at the link below. It looks like that I will have to create
CNAME entry for every IP in the /28 subnet, That is 16 CNAME entries?
The nameserver that I am sending to will have to create a zone record
called 224/28.79.73.217.in-addr.arpa?
I
The rest of the IP addresses (outside that /28) you can define with PTR
in the normal way, whenever you like. It's not necessary to define them
all, if they don't have a PTR record, that's alright.
So in your zone file on your 2 namservers you'll have
224/28 IN NS
On 03/25/2010 05:54 PM, Laurent Papier wrote:
Le Thu, 25 Mar 2010 15:51:29 +
Simon Bedfordsbedf...@plus.net écrit:
Guys,
We have upgraded our customer caching name servers to pdns recursor 3.2
(which is working very well), this has now been running for 4 days but
in the last 24 hours
On Thu, Mar 25, 2010 at 05:54:23PM +0100, Laurent Papier wrote:
I have also upgraded to pdns recursor 3.2 yesterday. And today, I have a
strange
problem on some of my systems. It seems be related to tcp DNS as the only
thing
that stopped working is using tcp dns queries. The rest of the
Le Thu, 25 Mar 2010 19:34:11 +0100
bert hubert bert.hub...@netherlabs.nl écrit:
On Thu, Mar 25, 2010 at 05:54:23PM +0100, Laurent Papier wrote:
I have also upgraded to pdns recursor 3.2 yesterday. And today, I have a
strange
problem on some of my systems. It seems be related to tcp DNS
10 matches
Mail list logo