On Sat, Dec 13, 2008 at 11:01 AM, Carl Houseman <[email protected]> wrote:
> I'll let you explain them however you like!
I don't have enough information to explain anything definitively,
I'm afraid. :)
> A local LAN adapter references one Windows AD DNS - TLD= a.com
Just so you know, TLD is "Top Level Domain", which means <com.>,
<net.>, <us.>, and the like. <a.com.> or <example.com.> would be 2LD,
"Second Level Domain".
> Based on what you've said, an NXDOMAIN response was not returned - because
> the domain did exist, only the hostname was not found.
At least one of us is confused in the above. :) If I understand
what you mean correctly, it sounds like things are working exactly as
I described: A query for the 2LD domain returned DNS resource records
("domain did exist"), but the domain name for the server resulted in
NXDOMAIN ("hostname was not found").
Understand that in DNS, there is no such thing as a "hostname". All
names are domain names. <com.> is a domain name. <example.com.> is a
domain name. <server.example.com.> is a domain name.
<www.example.com.> is a domain name. NXDOMAIN is returned by a
nameserver when a query is received for a domain name which said
nameserver knows not to exist, regardless of whether said domain is a
TLD, 2LD, or the domain name assigned to a server. :)
This is in contrast to Active Directory, where a "domain name" is an
entity which groups objects (computers, users, etc.) within an AD
forest, but is not itself a single computer. AD clients use DNS
domain names to locate AD Domain Controllers. Thus, confusingly,
while every AD domain name has a DNS domain name, every AD member
computer name has a DNS domain name, too.
-- Ben
~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
