Dear community,
I do have many error in my Bind's log file such as :
client 192.168.201.1#29404: error sending response: host unreachable
It seems that I have an iptables issue as each time I shut iptables I don't
have anymore this message showing up.
I saw that my firewall is dropping packets
On Mar 12, 2012, at 8:09 AM, Romgo wrote:
Dear community,
I do have many error in my Bind's log file such as :
client 192.168.201.1#29404: error sending response: host unreachable
It seems that I have an iptables issue as each time I shut iptables I don't
have anymore this message
On Mar 12, 2012, at 1:24 PM, Romgo wrote:
Here is my Iptables configuration for bind :
# prod.dns.in
$IPTABLES -t filter -A INPUT -j LOGACCEPT -p udp --dport 53 -i eth1-d
192.168.201.2 -s 0/0
$IPTABLES -t filter -A INPUT -j LOGACCEPT -p tcp --dport 53 -i eth1 -d
192.168.201.2 -s 0/0
I'm not familiar with LTM, so there is no need to check the pool with the
script, LTM will know itself and stop advertising through some other mechanism
when the pool is empty?
therefore checking VIPA using the script is just redundant?
From: David Klein
HEllo,
Has anyone else experience with reverse IPV6 configuration with Bind?
Regards,
Hugo,
From: spa...@countryday.net
To: hugo...@hotmail.com
CC: bind-users@lists.isc.org
Subject: RE: reverse dns for IPV6 ranges
Date: Tue, 6 Mar 2012 03:09:42 +
But if only some IP have e
On Mon, 12 Mar 2012, hugo hugoo wrote:
Has anyone else experience with reverse IPV6 configuration with Bind?
We do static PTR records in the ip6.arpa zones like we do in the in-addr.arpa
zones, to create address-name mappings matching the name-address mappings
created by the A records.
On Mon, Mar 12, 2012 at 12:05 PM, Mr X xproject...@gmail.com wrote:
Hey there
I'm having a bizarre issue with 9.7.3-P3-RedHat-9.7.3-8.P3.el6_2.2 -
recursive queries stop functioning after bind has been running for a few
hours. It's a very low volume system (dev), maybe a few queries per hour
Sorry, it has a space, I just made an error by copying.
Yes 192.168.201.2 is dropped because it uses source port 53. I don't have
any iptables rule for this.
I don't understand why there is a packet with source port 53.
On 12 March 2012 21:33, Chuck Swiger cswi...@mac.com wrote:
On Mar 12,
In message caaoqnkg-xfkws_fen9kedub7w19vf4jocsfp52lb8ixv5+g...@mail.gmail.com
, Romgo writes:
Here is my Iptables configuration for bind :
# prod.dns.in
$IPTABLES -t filter -A INPUT -j LOGACCEPT -p udp --dport 53 -i eth1-d
192.168.201.2 -s 0/0
$IPTABLES -t filter -A INPUT -j LOGACCEPT -p
I don't look at debug logs and may be WAY off base. But the time period
for the log seems to be about 10 seconds start to finish in the failed
query. However line 56 indicates that it timed out the query after 30
seconds.
That just doesn't add up to me for some reason. Or is there 20
10 matches
Mail list logo
