Wow... completely skipped your dig output. I'm sorry--that's what I get
for trying to reply at 11:58 pm.
Looks like your zone transfer came across, so that's good. My previous
comment about checking your BIND config still holds up (test.com has to be
defined in your named.conf), but also, do you
Hello,
Is the name change you're referring to the "db-n5Bia3fZ" file? If so,
that's not a zone name, but a journal file that BIND uses for dynamic
updates and incremental zone transfers.
At this point, don't worry about BIND itself at all. Just log into your
slave nameserver and run
dig @maste
Hello,
Is there any equivalent to the BIND Response Policy Zones (RPZ) feature for
PowerDNS Recursor? We've had some recent phishing attacks, and it'd be
nice to see if we can stop them before they start. Obviously mail
filtering plays a big role, but some sort of recursive DNS "firewall" would
Hi,
I have a newly created zone in PowerDNS using PowerAdmin GUI named test.com.
When I slave this zone to bind server. The file name gets changed. This
happens only with zones that are newly created on PowerDNS.
server1 /var/named/slave # touch test.com
server1 /var/named/slave # chown named:na
Hello Uprit,
On Jun 17, 2013, at 6:42 , Uprit Srivasatava wrote:
> I wrote a backend following the backend User's guide.
> I wanted my backend to support multi domain for eg: myproxy.domain1.com ,
> myproxy.domain2.com and so on, something like that.
>
> How I can achieve this in my backend.