I was setting up a web application on Windows 2000 IIS
to use locally in my office. the web application was
installed on the, let say, 192.168.0.100 server under
the name of somename.computername.local
But when I opened the IE, type in [somename.computername.local...]
it can not resolve this name. I found out later that
instead of looking to 192.168.0.100 the DNS resolve
[somename.computername.local...] as a 192.168.0.200
(.200 in stead of .100).
Yes this web application I tried to install was set up
on another server, 192.168.0.200, before. And the DNS
server not seem to know that that .200 is no longer
on the system. I have no authority on that DNS server,
so I can not do any thing (even I have authorize I might
not know how to fix it)
Now the only solution I have is to add a line
to the file "host" on every single computer that have to
use this web application and it works.
I figure, why not i just have my own dns server. I have
never set up an dns server before. My theory is that if
I have a dns server of my own, I can tell the dns that
somename.computername.local is on 192.168.0.100.
And I will set every single computer in my office to use
my new DNS server.
There are 3 things to do to done this, I think.
1. Add dns server component to windows 2000 which I think
I have already done it
2. Add a domain name somename.computername.local to the new dns!
how to do this I can not figure out the way my self
3. For the rest of the domain that this dns server will be asked
to query, this new dns server must consult the old DNS server.
This I do not know either of how to set it
It seem to me as an easy job to do but I must have just
please help me.