On 13 August 2013 08:20, Sury Bu <bushu...@gmail.com> wrote: > When I use host -a support.ourfirst.org 192.168.122.92, the result contains > following: > > ;; AUTHORITY SECTION: > support.ourfirst.org. 86400 IN NS ns.ourfirst.org. > > ;; ADDITIONAL SECTION: > ns.ourfirst.org. 86400 IN A 192.168.122.27 > > Received 71 bytes from 192.168.122.92#53 in 0 ms
So you didn't actually get a response that you wanted, you didn't get the A record for your requested support.ourfirst.org > But, if I directory use -t ns type to query the NS record, then It will > fail. > > [root@tester1 named]# host -t ns support.ourfirst.org 192.168.122.92 > Using domain server: > Name: 192.168.122.92 > Address: 192.168.122.92#53 > Aliases: > > support.ourfirst.org has no NS record You are missing the DNS zone in your DNS configuration for support.ourfirst.org. The NS record in ourfirst.org indicates that the server ns.ourfirst.org is the server responsible for the zone, but the zone either isn't created or has been created and BIND hasn't been reloaded to re-read the new configuration. The reason the server wont return the NS record when queried directly is because that is a glue record only, the zone didn't exist so there was no response to return. Steve _______________________________________________ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
