On 7/23/2010 8:50 AM, Phil Mayers wrote:
> On 23/07/10 13:23, Danny Mayer wrote:
>> On 7/22/2010 11:33 AM, Phil Mayers wrote:
>>> On 22/07/10 12:19, Rock July wrote:
Windows Vista and 7 clients will query both type A and query even
>>>
>>> The OS might make the query, but the application
On Thu, 22 Jul 2010, Peter Laws wrote:
BIND 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2
9.3.x has been EOL for a long time now, FYI.
--
Improve the effectiveness of your Internet presence with
a domain name makeover!http://SupersetSolutions.com/
Computers are useless. The
On Fri, 23 Jul 2010, Peter Laws wrote:
Except that the 2 "masters" are simply different interfaces on the same
master
Why do you think that would be helpful? Or are you just testing the
multi-master configuration in the hopes of adding actual diversity down
the road?
Doug
--
Imp
On Fri, 23 Jul 2010, Prabhat Rana wrote:
So as can be seen we are using the top level domain as the PTR zone
file for all the 10.x.x.x (10/8)address. However it appears in the
masters nodes, they don't have a top level zone file and have
basically broken down the top level to numerous sub doma
On 07/22/10 19:57, Barry Margolin wrote:
In article,
Peter Laws wrote:
I have multiple interfaces on my master and multiple interfaces on most of
my slaves.
Is that expected behavior?
Yes. What if the first server stops getting updates, but the second one
does and has a higher seria
Hello,
I have a BIND 9.7.1 running on a Solaris 10 box. This node is slave to certain
zone for PTR records as shown in the named.conf file below
zone "10.in-addr.arpa" in {
type slave;
check-names ignore;
file "zones/internal/10.in-addr.arpa";
masters { 10.2.3.4; 10
On 07/23/10 05:37, Danny Mayer wrote:
On 7/22/2010 11:08 PM, Merton Campbell Crockett wrote:
Thanks for the confirmation that the problem was related to DNSSEC.
I didn't see your message until I got home from work; however, I did
find the root of the problem late this afternoon. At each of our
Address selection configuration
In IPv6, each interface can have multiple addresses assigned to network and
tunneling interfaces intended for different purposes. For this reason,
RFC3484 provides a standardized method to choose source and destination IPv6
addresses with which to attempt connections
Change
## B. Atkins 20100723Started program...
###
## VARIABLES
PATH=$PATH:/usr/sbin/:/usr/local/bin/
###
## FUNCT
Finally I caught one query/server that produces the ". SOA: got insecure
response; parent indicates it should be secure" log each time:
"dig @ns ladeco.com. MX" does this every time, where ns runs bind
9.7.1-P2, with only the root TA configured.
The server serving that domain returns not exactly
On 23/07/10 13:23, Danny Mayer wrote:
On 7/22/2010 11:33 AM, Phil Mayers wrote:
On 22/07/10 12:19, Rock July wrote:
Windows Vista and 7 clients will query both type A and query even
The OS might make the query, but the application will (should) be using
getaddrinfo, and this will return
On 7/22/2010 11:08 PM, Merton Campbell Crockett wrote:
> Thanks for the confirmation that the problem was related to DNSSEC.
>
> I didn't see your message until I got home from work; however, I did
> find the root of the problem late this afternoon. At each of our
> Internet egress and ingress po
On 7/22/2010 11:33 AM, Phil Mayers wrote:
> On 22/07/10 12:19, Rock July wrote:
>> Windows Vista and 7 clients will query both type A and query even
>
> The OS might make the query, but the application will (should) be using
> getaddrinfo, and this will return the IPv4 addresses first, so it
I've test next configuration, which improve recursion performance of
isc-bind frontend.
bind listen on only on external interface and forward all recursive
queries to 127.0.0.1
=== named.conf ===
listen-on { 1.1.1.1; };
forward only;
forwarders {
127.0.0.1;
};
===
14 matches
Mail list logo
