on the recursor trace mode on that nameserver.
However, even with only a few checks every minute addressed to it,
piecing together the trace logs is still not real easy.
Does anyone else have any thoughts on this?
Thanks for any assistance you can give me!
Jeremy Utley
__
On 7/21/2011 1:14 PM, Stefan Schmidt wrote:
On Thu, Jul 21, 2011 at 8:00 PM, Jeremy Utley wrote:
gnint.prv=66.152.94.11, 66.152.94.12, 66.152.94.13
10.in-addr.arpa=66.152.94.11, 66.152.94.12, 66.152.94.13
...
$ host gn-ldap01.gnint.prv
gn-ldap01.gnint.prv has address 10.1.20.1
Host gn-ldap01
Hello to all on the list!
I'm seeing something kind of weird in our DNS setup, and was hoping I
could bounce it off all of you to see if I could get some input. First
off, structure of our system:
6 Recursor servers, sitting behind a Foundry Load balancer, running
pdns-recursor version 3.3-
Good morning to all on the list!
We ran into an oddity with our recursors this morning that I wanted to
consult with you about. There was a domain we knew had it's DNS entries
changed, but our recursors were still getting the old data, and we
wanted to fix that. So, as I always do in this si
Hello everyone!
Today I started adding some DomainKeys entries into our PowerDNS server,
and I encountered some oddities. I did some research on the net
regarding this issue, and didn't find anything that really helped me.
First off, start with our architecture:
Master Server: CentOS 5, P
On 12/2/2010 12:42 PM, Mark Felder wrote:
If I use a database backend on each side without database replication,
can I use an AXFR to have it automatically add a domain to the
database of the slave, or is this still an issue with AXFR as a whole?
Simply put, I don't want to have to touch the s
Good afternoon,
We've been working on upgrading our recursors from
pdns-recursor-3.1.7.1-1 to pdns-recursor-3.3-1, and have seen some
oddities I wanted to ask the list about. First, a basic rundown of our
environment:
Our existing production servers are running pdns-recursor-3.1.7.1-1
inst
