Re: SERVFAIL on stub zone (WAS: dig @server foobar +trace +recurse)

2015-07-15 Thread Tony Finch
Anne Bennett a...@encs.concordia.ca wrote: It all looks just peachy, but when I issued: dig @localhost -t ns concordia.ca. it gave me a SERVFAIL. I couldn't find anything abnormal in the syslogs. I can't for the life of my figure out why it's unhappy. How can I debug this? Try rndc

Re: SERVFAIL on stub zone (WAS: dig @server foobar +trace +recurse)

2015-07-15 Thread Anne Bennett
Tony Finch suggested: (I'm syslogging default syslog_all, minus edns-disabled, lame-servers, rpz, and unmatched.) Excluding lame-servers might be why you aren't seeing any log messages. I tried un-excluding it: nothing. zone concordia.ca { type stub; file

SERVFAIL on stub zone (WAS: dig @server foobar +trace +recurse)

2015-07-14 Thread Anne Bennett
Tony Finch d...@dotat.at enlightens me thus: The difference between stub and static-stub is that stub works like the root zone hints, i.e. the servers in the zone override the ones that you configure for a stub zone, whereas the servers you configure for a static-stub zone override the

Re: SERVFAIL on stub zone (WAS: dig @server foobar +trace +recurse)

2015-07-14 Thread Anne Bennett
zone concordia.ca { type stub; file StubData/concordia.ca.SEC; masters { 132.205.1.1 ; 132.205.7.51 ; }; multi-master yes; }; [results in transferring:]