Barry Finkel wrote:
I ran a test this morning on one of the Solaris 10 slave servers.
A query to the server showed serial numbers:
_tcp 1238
_udp842
Both of these match the zone on the MS Windows DNS Server.
I checked the zone files on the slave server:
_tcp 1239
_u
Barry Finkel wrote:
I ran a test this morning on one of the Solaris 10 slave servers.
A query to the server showed serial numbers:
_tcp 1238
_udp842
Both of these match the zone on the MS Windows DNS Server.
I checked the zone files on the slave server:
_tcp 1239
_u
On 07/06/11 13:51, I wrote:
I now have this situation on one Solaris 10 slave; the problem
probably also exists on the other Sol 10 slave and the two
Ubuntu hardy slaves:
The _tcp zone on the master MS DNS Server:
1238 600 86400 3600
The _tcp zone on the BIND 9.7.3-P1 Solaris 10 server di
"McDonald, Dan" " replied to my
posting:
I think your root problem is trying to deal with active directory
integrated zones. We stopped using them entirely when we found that
each domain controller maintains an individual SOA record with its own
serial number. The serial numbers rapidly (and p
On 07/06/11 13:51, Barry Finkel wrote:
In my last posting I was confused as to the .jnl file. I have
about 44 AD slave files on my BIND servers, and 40 .jnl files.
The two zones in question do not have .jnl files. As I do not
look at .jnl files much, I had forgotten about the tool to
list them.
On 6/7/11 7:51 AM, "Barry Finkel" wrote:
> There was a zone serial number mismatch, each zone expired three days
> ago, and new zones were transferred from the master. But the zone
> files on disk still have the higher serial numbers. There are no .jnl
> files on the disk. A "dig" on the serve
In my last posting I was confused as to the .jnl file. I have
about 44 AD slave files on my BIND servers, and 40 .jnl files.
The two zones in question do not have .jnl files. As I do not
look at .jnl files much, I had forgotten about the tool to
list them.
I now have this situation on one Solar
On 06/06/2011 08:01 PM, Barry Finkel wrote:
Phil Mayers suggested a corrupt .jnl file; I am not sure.
How do I debug this?
Given what Mark has said, I think it's unlikely; I didn't realise bind
wrote a new journal and did a rename() which is atomic on every POSIX
system that you're likely to
sts.isc.org
> Subject: Re: BIND 9.7 Serial Number Decrease Problem
I think your root problem is trying to deal with active directory
integrated zones. We stopped using them entirely when we found that
each domain controller maintains an individual SOA record with its own
serial number. The ser
Barry Finkel wrote:
>
> I am not sure how to decode the .jnl file; I have not looked at the code
> in detail.
Try the named-journalprint program. You can also try named-compilezone -j
which applies the journal to the master file.
Tony.
--
f.anthony.n.finchhttp://dotat.at/
Rockall, Malin, He
In message<4de9045c.2050...@anl.gov>, Barry Finkel writes:
I have a problem with BIND 9.7.x on Ubuntu.
I have two servers that are running 9.7.3.
They slave 332 zones, and they also master 213,750
malware/spyware zones that we have defined to reroute these
domains to a local machine.
When I was
In message <4de9045c.2050...@anl.gov>, Barry Finkel writes:
> I have a problem with BIND 9.7.x on Ubuntu.
> I have two servers that are running 9.7.3.
> They slave 332 zones, and they also master 213,750
> malware/spyware zones that we have defined to reroute these
> domains to a local machine.
>
On 06/03/2011 04:57 PM, Barry Finkel wrote:
I have a problem with BIND 9.7.x on Ubuntu.
I have two servers that are running 9.7.3.
They slave 332 zones, and they also master 213,750
malware/spyware zones that we have defined to reroute these
domains to a local machine.
That's a hell of a lot of
13 matches
Mail list logo
