On 01-Apr-2008, at 09:21 , Eric B. wrote:
> Thanks Mark.
>
> I tried a dig soa command and got the following output. I am hoping
> that
> someone can help me determine what is missing. The one thing I
> noticed is
> that I don't have the "AUTHORITY" section. Could that be triggering
> the
> problem? If so, any ideas how can I ensure that it is present?
> What do I
> need to make sure is in my Master conf file to have that appear?


> # dig soa mydomain.biz @198.20.1.1 +norec
>
> ; <<>> DiG 9.2.4 <<>> soa mydomain.biz @198.20.1.1 +norec
> ; (1 server found)
> ;; global options: printcmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 42824
> ;; flags: qr aa ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
>



The AUTHORITY section is only present when the name server that
responds is not authoritative for the data you queried about. The
presence of the AUTHORITY section suggests "I'm not authoritative for
this data, the name servers listed here are." You wouldn't expect it
to be present in a response from your master.

The key thing to note in your output is that the +aa bit is set, which
means that this is an authoritative response.

Looking back at your original post, I see where your problem is:

> zone "mydomain.biz.dns" IN { type slave; file "slaves/
> mydomain.biz.dns";
> masters { 198.20.1.1; }; };
>



The zones 'mydomain.biz.dns' (in your config file) and 'mydomain.biz'
are not the same. Your master is authoritative for mydomain.biz, but
your slave is configured to do a zone transfer for mydomain.biz.dns,
which your master is not authoritative for.

Fix your slave configuration and you should be golden.