Which one is screwed up?
I am building a new domain (abc.com) with W2K as the operating system, and I eventually wish to have the new domain run AD.
Last night I was creating both the forward and reverse DNS zones for abc.com
Standard Primary both forward and backward
Allow dynamic updates- yes (forward only)
SOA record pointing to the proper name of the server (nifty)
Server nifty.abc.com is defined as a name server both forward and backward with the proper IP defined (1.2.3.4)
So I start up nslookup to check the zones. Nslookup tells me that I am accessing nifty.abc.com at address 1.2.3.4 so everthing looks just fine.
I type in ls-d nifty.abc.com
Receive: Cannot find ls-d server failed.
Using nslookup, if I type in the names included within the zone files proper resolution takes place. Example: If I type in nifty I receive the proper 1.2.3.4 is returned. I can see proper resolution is happening if I ping a name that is included in the zone files.
I feel like my zones are set up properly and ready for the next step of AD installation, but the error in nslookup concerns me. Am I just a worry wart? What have I done wrong?
I am building a new domain (abc.com) with W2K as the operating system, and I eventually wish to have the new domain run AD.
Last night I was creating both the forward and reverse DNS zones for abc.com
Standard Primary both forward and backward
Allow dynamic updates- yes (forward only)
SOA record pointing to the proper name of the server (nifty)
Server nifty.abc.com is defined as a name server both forward and backward with the proper IP defined (1.2.3.4)
So I start up nslookup to check the zones. Nslookup tells me that I am accessing nifty.abc.com at address 1.2.3.4 so everthing looks just fine.
I type in ls-d nifty.abc.com
Receive: Cannot find ls-d server failed.
Using nslookup, if I type in the names included within the zone files proper resolution takes place. Example: If I type in nifty I receive the proper 1.2.3.4 is returned. I can see proper resolution is happening if I ping a name that is included in the zone files.
I feel like my zones are set up properly and ready for the next step of AD installation, but the error in nslookup concerns me. Am I just a worry wart? What have I done wrong?