In Sonny Singh <
[email protected]>
posted their concerns,
Then Kevin D4Dad added his reply at the bottom.
Hey Kevin, I have 1 DC. It has DNS installed. It is
running AD. I have 2 NICs. I went into the TCP/IP
properties of each NIC and in the DNS space, I put in the
IP address associated with each NIC. This is the only
domain controller in my domain. I will put the IP of the
server into the DNS settings for all of my clients as
well. I no longer am getting that error in the event
log. I guess my question is this: How does my domain
controller know where to go to resolve host names. I put
the DC's own IP in the "preferred DNS server" settings.
Everything works, but I am just curious how it knows
where to go to resolve the host names now. Before I made
these changes today, I had another local DNS server's IP
address in there. I'm assuming it was the IP of another
DNS server on campus. I now have my own DC's IP as the
preferred DNS server. How is my server all of a sudden a
DNS server? I always thought that a DNS server had host
files which resolved IPs to their DNS names. If it
couldn't find it on 1 particular DNS server, it would go
to a root server. I guess that's what I am confused
about. After making these changes, how does my server
know where to go to translate addresses?
Hi Sonny,
I'm glad you got things worked out even though you seem to not understand
how.
You do have a DNS server real, live, go get the answer if it doesn't know
it, bring it back and serve it up to you DNS server. Pretty amazing heh?
You're saying to yourself how's it doing that?
Well consider yourself lucky that it worked for you the first time around it
didn't for me and it doesn't for a lot of people because most of the time
the root "." Forward Lookup Zone is still in place, without the delegations
it needs to work correctly. If it has a root zone with no delegations it
won't work you either have to put the delegations in it or delete it, most
everybody deletes it because it is a simple fix. Deleting the root zone
allows it to either use Root Hints or a forwarder if you have defined one.
That was the link I sent you.
Yes, Sonny you have a DNS server it is not anyone else's it is yours. It has
at least one Forward Lookup Zone (FLZ) in it, which matches the DNS name of
your Windows 2000 domain. Depending on what name you gave your domain you
may or may not have trouble. Let me say what I mean because, this will
answer a question, that seems to be asked here daily.
The question is, "I can't reach my website on the internet which has the
same domain name as my Windows 2000 domain?" The fix is simple a FLZ has
hosts in it for each name in a particular domain. You're internal FLZ has
hosts in it, too. These are for the machines on you local network that it
knows about. The one's it does not know about, if you have one are www,
mail, ftp and so on those have to be entered manually by you, into your FLZ.
It is a pretty simple and straight forward process adding these host with
their respective IP addresses.
So, now it is answered for you, if you by chance named your Domain
something like sonny.com and now you can't reach the website
www.sonny.com .
This is the jest of it. I would bet the rest of it you will pick up on your
own.
let's clarify are you using only your DC that has