Good afternoon I finish migrating my server of Windows NT to Windows 2003
server and my problem is that when attempt to add an equipment with Windows
2000 send me the next error
Network Identification

In a PC, a memeber of 2k3 AD, I typed at the command line "ipconfig
/displaydns"  and got a list of my PC cached resolved names.  Then, I typed
"ipconfig /flushdns" and got a confirmation message that the command executed
successfully.  Again, I typed "ipconfig /displaydns" and ...

I can do a name lookup for anyone on the internet and it works just fine UNLESS there is an Alias involved with the name.
Example 1 :
C:\>nslookup nws.noaa.gov
Server:  dns1.ksdot.org

I have two companies that we support that each have Windows 2003 with
Exchange 2003.  They each are current on all updates and service packs.
But, on occasion, their dns service stops resolving and the queue's stack
up.  Email does not go out.

we are hosting a new website inhouse and I'd like to know how setup my DNS to
point to the internal IP of the new site.
Thanks
Al

This is kind of newbie question... I googled about this scenario,
but with no results :(
Lets say I have fictivedomain.com registered with ns1.fictivedomain.com
(10.20.30.1) and ns2.fictivedomain.com (10.20.30.2) that serve as

How do I tell my server.....
When I type ftp.mydomain.com in internet explorer
Go to ftp://www.mydomain.com
Thanks!

The web site is hosted on the webserver in DMZ in our office ad the whole
world is able to open it ... but from nside the company we cannot open it by
name, our ISP says ... they changed the DNS address .... now my AD DC
forwarded is configured to point to the new IPs but still ...

we have one Server 2003 where nslookup only works sometimes. We have a lot
of trouble with this server because it is our Terminal Server and sometimes
it is very slow.
I think it is because of the problems with the name resolution.

I have recently changed my 2003 server st.editon, to have directly acess to
internet
I have a new networkadapter which I connect directly to a xDSL connection
and an other networkadapter for the simple internal network. Active

Our internal DNS is the same as our external DNS.  We only have one A record
"www" that we point to an external IP address.  This has worked no problem
for the last serveral years.  
Today for some reason, I am unable to resolve the www.xxx.com site

I just want to make sure that I've either got this concept right, or
completely wrong.
If I configure a DNS forwarder on a Server2003 DC using an external DNS
server for "all other domains," am I correct that if I don't disable

Has anyone had a problem similar to this:
Server 2003 running DNS/DHCP... All XP enviroment.
For no reason at all, a machine can't find the name of a machine it just
knew.  the machine will be unable to contact the server through name

I current'y have 1 DMS server. I would like to make an additional server a
DNS server for fault tolerance and so that Exchange and name resolution will
still work in the even that I have to reboot the orginal DNS server. Some
background info:

We have Active Directory on Windows Server 2003. I'll call our domain
ourdomain.com. All machines have the DNS suffix set to
local.ourdomain.com in the DNS properties.
We have a problem with the UK Health and Safety site at www.hse.gov.uk.