To follow up and provide the answer for those who seek it in future, for
reasons I still can't entirely find the source for (you might have to dust
off your RFCs), the advice is don't run an authoritative name server, and a
resolver, on the same port.
You can do something like this:
pdns-recursor
Hi,
I realise this issue has been covered on the list, but (a) a couple of years
ago, and (b) with slightly different symptoms.
On Amazon EC2, I have a PowerDNS server [1] set up for an example.local
domain. I also have recursion enabled and set to the EC2 "virtual
nameserver", 172.16.0.23. For
