Re: nsd configuration problem

2015-06-26 Thread Craig Skinner
On 2015-06-25 Thu 14:22 PM |, Andrew Daugherity wrote: The important bits to actually make this work are the 'do-not-query-localhost: no' and 'local-zone: C.B.A.in-addr.arpa. transparent' options, needed to override unbound's default behavior of ignoring localhost and RFC1918 addresses. It

Re: nsd configuration problem

2015-06-25 Thread David Dahlberg
Am Mittwoch, den 24.06.2015, 18:02 +0100 schrieb Graham Stephens: I've tried to set up nsd on 5.7 x64 and it's not working as it should, but I'm lost as to where to look to correct the issue. I was hoping for some pointers. :) Okay. First of all, I hope you are aware of the difference

Re: nsd configuration problem

2015-06-25 Thread David Dahlberg
Am Donnerstag, den 25.06.2015, 11:42 +0100 schrieb Graham Stephens: I'm trying to replace several boxes (firewall, file server, mail server) with one virtualized one. [..] So actually you do not want to serve names of a domain (say thestephensdomain.com) to the Internet, but you want the

Re: nsd configuration problem

2015-06-25 Thread Andrew Daugherity
On Wed, Jun 24, 2015 at 1:06 PM, Graham Stephens gra...@thestephensdomain.com wrote: --- On 24/06/2015 18:43, mxb wrote: Hey, this is a bit different from bind/named. nsd is a authoritative server ONLY. unbound is a caching server ONLY. I use those together on

Re: nsd configuration problem

2015-06-25 Thread mxb
Good that you solved your problem. I'v done same work as you by converting from bind to nsd+unbound. The hard way via digging Google and trying out. You got lucky with shortcut ;) //mxb On 2015-06-25 21:22, Andrew Daugherity wrote: On Wed, Jun 24, 2015 at 1:06 PM, Graham Stephens

Re: nsd configuration problem

2015-06-25 Thread Patrik Lundin
On Thu, Jun 25, 2015 at 02:13:15PM +0100, Graham Stephens wrote: OK, it seems that when I skip-read the NSD/Unbound info I got them wrong. Unbound sounded like a DNS cache, and NSD, unsurprisingly, a name server. They are both name servers, but NSD is only meant to serve information

Re: nsd configuration problem

2015-06-25 Thread Patrik Lundin
On Thu, Jun 25, 2015 at 11:55:06AM +0100, Graham Stephens wrote: I haven't used dig before, I hope these are what you're after. They do show different results to nslookup. These are all taken from the local machine. dig blahms01 and dig @127.0.0.1 blahms01 return: ; DiG 9.4.2-P2 blahms01

Re: nsd configuration problem

2015-06-24 Thread Patrik Lundin
On Jun 24, 2015, at 10:02 AM, Graham Stephens gra...@thestephensdomain.com wrote: I've tried to set up nsd on 5.7 x64 and it's not working as it should, but I'm lost as to where to look to correct the issue. I was hoping for some pointers. :) (possible) Symptoms: Starting nsd causes

Re: nsd configuration problem

2015-06-24 Thread Peter Pauly
NSD (name server daemon) is for authoritative DNS - answering the question for internet users what is the IP address of my servers. You may want to use Unbound. It is a recursive DNS lookup that answers the question: what is the IP address of a server out on the internet that belongs to someone

Re: nsd configuration problem

2015-06-24 Thread trondd
On Wed, June 24, 2015 2:28 pm, Peter Pauly wrote: NSD (name server daemon) is for authoritative DNS - answering the question for internet users what is the IP address of my servers. You may want to use Unbound. It is a recursive DNS lookup that answers the question: what is the IP address of