[Pdns-users] "Additional Section" with A records in NS lookups missing?

[John Morris]

OK, I didn't try hard enough, turned this on:

	disable-axfr=no

And now get this (ordinary hosts edited out), not sure why two SOAs:

        $ dig @127.0.0.1 zultron.com axfr
        
        ; <<>> DiG 9.2.4 <<>> @127.0.0.1 zultron.com axfr
        ;; global options:  printcmd
        zultron.com.            10800   IN      SOA     ns1.zultron.com. root.zultron.com. 2006031900 28800 600 1209600 10800
        zultron.com.            3600    IN      A       69.26.161.66
        zultron.com.            3600    IN      NS      ns1.zultron.com.
        zultron.com.            3600    IN      NS      ns2.zultron.com.
        ns1.zultron.com.        3600    IN      A       69.26.161.66
        ns2.zultron.com.        3600    IN      A       207.210.96.241
        zultron.com.            10800   IN      SOA     ns1.zultron.com. root.zultron.com. 2006031900 28800 600 1209600 10800
        ;; Query time: 71 msec
        ;; SERVER: 127.0.0.1#53(127.0.0.1)
        ;; WHEN: Tue Mar 21 16:55:53 2006
        ;; XFR size: 16 records
        
Thanks again-

	John



> > > I've just noticed a problem with my domain.  The nifty tool at
> > > http://www.dnsreport.com/ tests for A records returned on NS queries.
> > > See the following (edited) output from dig; powerdns.com does,
> > > zultron.com doesn't:
> > 
> > This might be a bug in the LDAP backend. Can you dump the content of your
> > 'zultron' zone?
> 
> Hmm, seems I can't.  Never tried before since I use LDAP replication to
> propagate changes.  I turned on 
> 
> 	allow-axfr-ips=127.0.0.1
> 
> and saw this:
> 
>         $ dig @127.0.0.1 zultron.com axfr
>         
>         ; <<>> DiG 9.2.4 <<>> @127.0.0.1 zultron.com axfr
>         ;; global options:  printcmd
>         ; Transfer failed.
>