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
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
Hi,
i can't find the version 9.4-ESV-R4-P1 even here: http://ftp.isc.org/isc/bind9/
Last week this version was on the website(http://www.isc.org/downloads/all).
why they remove it? I know it's EOL but at least i have to find it here
http://ftp.isc.org/isc/bind9/
Thanks
Issam HARRATHI
On 6/7/11 7:51 AM, Barry Finkel bsfin...@anl.gov 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
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 Fri, Jun 03, 2011 at 03:09:13PM -0700,
Sri Harsha Yalamanchili har...@thought-matrix.com wrote
a message of 145 lines which said:
o query-source address X.X.X.X port 53;
That's typically a very bad idea because it makes the source port
predictable and therefore makes you much
McDonald, Dan dan.mcdon...@austinenergy.com 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
BIND 9.6.1-P3 seems to be a somewhat old release of BIND, and yet, I can
find no vulnerabilities listed on the ISC Security Advisories pages. Am
I missing something?
Regards,
Joe
Joseph A. Borgia, Jr.
Network Services Team Lead
Team Rome IT - NCI
The query-source address is nat'ed address inside the firewall. We opted
for that to make our firewall less porous but may be we should re-visit
that strategy.
The forwarder actually works. That was the primary/only DNS server we
were using until we decided to install our own internal dns and
On Jun 7, 2011, at 11:07 AM, Sri Harsha Yalamanchili wrote:
Not much luck using tcpdump either. We know, from both the query_log and
tcpdump logging, that the queries are going out. But we never get a reply
back. That's the confusing part. The Google DNS server replies back but not
our own
Can anyone tell me why my MX record for the coop-uspto.gov domain are IP
addresses instead of hostnames?
[klear@dns1 conf]$ nslookup
set type=mx
coop-uspto.gov
Server: 10.240.11.20
Address:10.240.11.20#53
Non-authoritative answer:
coop-uspto.gov mail exchanger = 5
On 06/07/2011 08:31 PM, Lear, Karen (Evolver) wrote:
Can anyone tell me why my MX record for the coop-uspto.gov domain are IP
addresses instead of hostnames?
[klear@dns1 conf]$ nslookup
As of right now, that's not what I see:
;; ANSWER SECTION:
coop-uspto.gov. 7200IN MX
Karen Lear wrote:
Can anyone tell me why my MX record for the coop-uspto.gov domain are IP
addresses instead of hostnames?
...
Non-authoritative answer:
coop-uspto.gov mail exchanger = 5 151.207.128.23.coop-uspto.gov.
coop-uspto.gov mail exchanger = 5 151.207.128.22.coop-uspto.gov.
I
Thanks.
From: bind-users-bounces+karen.lear=uspto@lists.isc.org
[bind-users-bounces+karen.lear=uspto@lists.isc.org] On Behalf Of Eivind
Olsen [eiv...@aminor.no]
Sent: Tuesday, June 07, 2011 5:38 PM
To: bind-users@lists.isc.org
Subject: Re: MX
I suspect a operator error that has now been fixed. If you put IP
addresses in the MX records, instead of hostnames, the current $ORIGIN
will be appended which is born out by looking at the address records
for the mail exchangers.
Mark
[drugs:~/cvs/bind9] marka% dig mx coop-uspto.gov
; DiG
Hello,
My second nameserver has tow IPs, for example,
61.144.56.1
61.144.57.1
(They are in different CIDRs.)
and my ns2.example.com was pointed to these two IPs.
Will this cause problems, for example, the duplicated notification or
zone-transfer?
Thanks in advance.
Hello,
From the dig info below:
C:\digdig +nocmd www.nsbeta.info +noall +answer @ns1.google.com
www.nsbeta.info.3497IN CNAME nsbeta.info.
nsbeta.info.2434IN A 74.117.232.204
C:\digdig +nocmd www.nsbeta.info +noall +answer @ns1.google.com
17 matches
Mail list logo
