> >>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 three processes to start - is this normal? > >>
This is normal. > >>If I use "nslookup blahname 127.0.0.1" from the local host, I get a > >>response as expected. > >> The nslookup tool is not a good option for debugging DNS, see for example http://homepage.ntlworld.com/jonathan.deboynepollard/FGA/nslookup-flaws.html If you can repeat the tests with dig(1), as in "dig @127.0.0.1 example.com", that would make it easier for me to follow. > >>Just using "nslookup blahname" gives as error of: > >>";; Got recursion not available from 127.0.0.1, trying next server". > >> Getting "recursion not available" sounds correct if you are querying NSD. since it is an authoritative only server, it should not allow recursive queries. This should still give you a result for a domain owned by NSD though (without the "ra" (recursion available) bit set. Please try this with dig(1) instead of nslookup and report the results. > >> From another machine on the lan, using "nslookup blahname" returns: > >> > >>"Server: blahname2.domain.com > >>Address: 10.0.2.1 > >> > >>*** blahname2.domain.com can't find blahname: Query refused" > >> The main reason I would expect a "REFUSED" response from NSD would be if you queried it for a domain name that it was not authoritative for. Again, please show the results of dig(1) (including the commandline used). -- Patrik Lundin
