Based on the answer size for the query you presented, I'd focus on
looking for an upstream filter/device that is blocking answers that
are 512 bytes.
On Wed, Sep 9, 2009 at 5:34 AM, Matthias Brehmmatthias.br...@dpd.com wrote:
Dear all,
we use bind9.5.0-P2 for the internet dns server.
On Wed, Sep 9, 2009 at 10:51 AM, Rich Goodson rgood...@gronkulator.com wrote:
zone . {
type slave;
file slave/root.slave;
masters {
192.33.4.12; // C.ROOT-SERVERS.NET.
192.112.36.4; // G.ROOT-SERVERS.NET.
193.0.14.129;
I'm using 3 dns servers with Bind bind-9.2.2.P3-9
Master A (domain1 + domain2)
Slave B (domain1)
Slave C (domain2)
Now I'm migrating master A to Bind 9.5.1.dfsg.P3-1 together OS (Debian
Lenny) so I'm interesting to know if there is some incompatible settings
from/to slave servers.
For
Hi,
I'm testing Bind 9.6.1-P1 on Solaris 10 SPARC (64bit/Sun Studio 12.1)
I noticed this in the logs:
Sep 9 13:15:31 ns3a/ns3a named[23042]: [ID 873579 daemon.info]
listening on IPv4 interface lo0, 127.0.0.1#53
Sep 9 13:15:31 ns3a/ns3a named[23042]: [ID 873579 daemon.info]
listening on
Of course, right after hitting enter on this message, I came across a
message from last year about localhost mapping to all interfaces, not
just 127.0.0.1. I created a loopback acl used it instead that
worked. Sorry for the noise.
-John
On 09/09/2009 03:04 PM, John Center wrote:
Syntax. The parser is matching on localhost before it sees the negated
elements.
- Kevin
John Center wrote:
Hi,
I'm testing Bind 9.6.1-P1 on Solaris 10 SPARC (64bit/Sun Studio 12.1)
I noticed this in the logs:
Sep 9 13:15:31 ns3a/ns3a named[23042]: [ID 873579 daemon.info]
listening on
Hello,
I'm trying to better understand NSEC3. I have a signed zone for which
I periodically resign expiring RRs with expiring RRSIGs using
dnssec-signzone. When I do so, I use a different salt each time,
which results in multiple salts being used in the zone. According to
RFC 5155:
This is
On 09.09.09 11:00, Rick Dicaire wrote:
On Wed, Sep 9, 2009 at 10:51 AM, Rich Goodson rgood...@gronkulator.com
wrote:
zone . {
type slave;
file slave/root.slave;
masters {
192.33.4.12; // C.ROOT-SERVERS.NET.
192.112.36.4; //
On Wed, Sep 09, 2009 at 05:47:34PM +0100, Sam Wilson wrote:
In article mailman.450.1252511223.14796.bind-us...@lists.isc.org,
Balanagaraju Munukutla 9ba...@sg.ibm.com wrote:
Hi
Anybody can help to explain the side effect of configuring the DNS name to
multiple IP addresses(Round Robin
9 matches
Mail list logo