Does anyone know what happens if a domain with an older TXT spf record
is included in a newer SPF spf record? For example:
foo.com IN TXT"v=spf1 mx a:mail1.foo.com a:mail2.foo.com ?all"
bar.com IN SPF"v=spf1 mx a:mail1.bar.com a:mail2.bar.com
include:foo.com ?all"
Ideal
. I was only using the root trusted key in my /etc/trusted-key.key
file for dig while the server itself is using DLV to validate down the
chain until it gets to the missing DNSKEY record.
On 09/15/2010 10:05 AM, Casey Deccio wrote:
> On Wed, Sep 15, 2010 at 7:34 AM, Timothy Holtzen
>
I am having trouble resolving the host name cod.ed.gov which I believe
may be dnssec related. If I run dig with the +cdflag option I get what
appears to be a proper response:
; <<>> DiG 9.7.1-P2-RedHat-9.7.1-2.P2 <<>> +cdflag cod.ed.gov
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opco
Has anyone been able to get 9.7.1-P2 to build with pkcs11 and run on
RHEL/CentOS 5? I appear to be able to configure and make without any
problems but when I go to run it I get the following error in the log.
named[14899]: starting BIND 9.7.1-P2 -c /etc/named.conf -t /var/named/chroot
named[14899
I have seen references out there about cache hit rates of 50-70% being
normal. However I'm confused as to how to measure/calculate hit ratio?
I can't seem to find any good references on how to find it. The only
thing I've been able to find is to do
("responses sent") - ("queries caused recursi
Our secondary server died last night with the following messages:
named[18768]: resolver.c:3827: fatal error:
named[18768]:
RUNTIME_CHECK(((pthread_mutex_unlock(((&res->buckets[bucketnum].lock))) == 0) ?
0 : 34) == 0) failed
named[18768]: exiting (due to fatal error in library)
Has anyone seen
k = (isc_task_t *) 0x0
#17 0x00412434 in main (argc=0, argv=0x7fffcfcc2fe8) at ./main.c:914
result =
JINMEI Tatuya / 神明達哉 wrote:
> At Thu, 26 Feb 2009 07:58:29 -0600,
> Timothy Holtzen wrote:
>
>
>> No it is a single processor on both production and test
with the same errors.
JINMEI Tatuya / 神明達哉 wrote:
> At Wed, 25 Feb 2009 14:17:27 -0600,
> Timothy Holtzen wrote:
>
>
>> I applied the patch on my test system and ran my little test using wget
>> and this is the output I got in the log
>>
>> Feb 25 13:51:1
ser()
wouldn't make a difference. I decided to try anyway and got the same
result.
JINMEI Tatuya / 神明達哉 wrote:
> At Tue, 24 Feb 2009 14:26:45 -0600,
> Timothy Holtzen wrote:
>
>
>> Hi guys I'm getting this assertion failure again under Bind 9.5.1-P1 on
>> RHEL
Hi guys I'm getting this assertion failure again under Bind 9.5.1-P1 on
RHEL 5.2.
Feb 23 22:00:01 foo named[18476]: statschannel.c:696: INSIST(xmlrc >= 0)
failed
Feb 23 22:00:01 foo named[18476]: exiting (due to assertion failure)
I posted about it once before. I understand that this is caused b
Last night one of our name servers stopped unexpectedly. Looking in the
logs I found the following messages.
Jan 13 20:15:01 foo named[29625]: statschannel.c:696: INSIST(xmlrc >= 0)
failed
Jan 13 20:15:01 foo named[29625]: exiting (due to assertion failure)
Anyone have any idea why this would ha
11 matches
Mail list logo