"Kelvin Beaton" <kelvin at mccsa dot com> wrote in message
news:%23ZaWc$hoHHA.208[ at ]TK2MSFTNGP05.phx.gbl...
[Quoted Text] > I'm studying up on DNS (Windows 2003 server with Active Directories) so
> thought I would take a look at how my network is setup. (some I setup and
> some I had outside help with)
>
> I found a DNS entry for an old server (DC/DNS server) that hasn't been on
> line for a year or more.
> I deleted the entry in DNS for the old server (192.168.0.1) and as soon as
> I did, the phone started to ring saying they had lost their conntection to
> our SQL server.... so I put the entry back, all seem ok again.
> What I want to do is get rid of any refference to that old server from my
> network.....
Presumably the clients are using SOMETHING at that address by that OLD
name.
So you really have to STOP the clients from using that old name.
Or just don't worry about it -- there is NO technical reason the working
server cannot be reached by alternate names (as long as it works).
What is at that address? (You don't have to tell me but that is where you
want to figure this out from....)
> I also found in the file "DhcpSrvLog-Tue.log" I'm getting a ton of "DNS
> update failed" don't know where to start looking to resolve this.
> Event Viewer doesn't have corresponding errors, so no clue that I can see
> there.
DHCP isn't updating DNS? maybe you used Update Credentials with an
EXPIRING password?
Maybe DHCP server is not authenticating?
> In the DNS Server manager, under my domain folder, I see duplicate IP
> addresses with different computer names. Is this normal? I would assume
> not. Is there a TTL setting for these records, as some of the computers
> haven't been online for most of a year.
>
> Also why would my Root Hints, displays "Unknown" for about 9 or the 13
> entries.
> I believe this is the file (C:\WINDOWS\system32\dns\cache.dns) it is
> looking at.
> The contents is below.
>
> Any help would be apprectiated
>
> Kelvin
>
>
> ++++++++++++++++++++++++
> ;
> ; Root Name Server Hints File:
> ;
> ; These entries enable the DNS server to locate the root name servers
> ; (the DNS servers authoritative for the root zone).
> ; For historical reasons this is known often referred to as the
> ; "Cache File"
> ;
>
> [ at ] NS d.root-servers.net.
> d.root-servers.net A 128.8.10.90
> [ at ] NS e.root-servers.net.
> e.root-servers.net A 192.203.230.10
> [ at ] NS f.root-servers.net.
> f.root-servers.net A 192.5.5.241
> [ at ] NS g.root-servers.net.
> g.root-servers.net A 192.112.36.4
> [ at ] NS h.root-servers.net.
> h.root-servers.net A 128.63.2.53
> [ at ] NS i.root-servers.net.
> i.root-servers.net A 192.36.148.17
> [ at ] NS j.root-servers.net.
> j.root-servers.net A 192.58.128.30
> [ at ] NS k.root-servers.net.
> k.root-servers.net A 193.0.14.129
> [ at ] NS l.root-servers.net.
> l.root-servers.net A 198.32.64.12
> [ at ] NS m.root-servers.net.
> m.root-servers.net A 202.12.27.33
> [ at ] NS a.root-servers.net.
> a.root-servers.net A 198.41.0.4
> [ at ] NS b.root-servers.net.
> b.root-servers.net A 192.228.79.201
> [ at ] NS c.root-servers.net.
> c.root-servers.net A 192.33.4.12
>
|