Lost one of my servers in nslookup

[mandg]

For the longest time, doing an nslookup echoed back two servers running DNS, our IIS server and our PDC server. Now however, I only get the IIS server to echo back and there's no sign of the PDC server. As a result, I believe that one of the problems this is creating is that users are no longer able to sign in to the domain since their pc's can't resolve it. Can anyone help on where I need to look first? Thanks.

 

[pQi]

Is your DHCP and DNS service running?

 

[pQi]

flush your dns and re-register.

 

[mandg]

Yes, I've verified that the DHCP and DNS services are running. As you suggested, I did "ipconfig /flushdns" and then "ipconfig -renew" however the "nslookup" still only shows the IIS server.

 

[GlenJohnson]

Check you're nics for sending bad packets. I've seen this exact same thing when a brand new server started sending out bad packets as the nic went bad. Users were having problems to logging onto the domain, and I realized when I shut down the new server for upgrades, people could log on. I changed the nic out, problem solved. Good luck.

Glen A. Johnson
If you like fun and sun, check out Tek-Tips Florida Forum
"Creditors have better memories than debtors."
Benjamin Franklin (1706-1790); US author, diplomat and inventor.

 

[pQi]

Can you please run NETDiag on the ghost server and review the log, or paste log in thread.

Also have you checked the event log/DNS for any known errors.

 

[mandg]

Results from NetDiag below (replaced real domain name with mydomain.com);

=============================================

Computer Name: PDC_RICH
DNS Host Name: pdc_rich.mydomain.com
System info : Windows 2000 Server (Build 2195)
Processor : x86 Family 6 Model 8 Stepping 6, GenuineIntel
List of installed hotfixes :
KB822343
KB823182
KB823559
KB824105
KB825119
KB826232
KB828035
KB828741
KB828749
KB830352
KB832353
KB832359
KB834707-IE6SP1-20040929.091901
KB835732
KB837001
KB839643
KB839645
KB840315
KB840987
KB841356
KB841533
KB841872
KB841873
KB842526
KB842773
KB867282-IE6SP1-20050127.163319
KB870763
KB871250
KB873333
KB873339
KB883939-IE6SP1-20050428.125228
KB885250
KB885834
KB885835
KB885836
KB888113
KB889293-IE6SP1-20041111.235619
KB890046
KB890047
KB890175
KB890859
KB890923-IE6SP1-20050225.103456
KB891711
KB891781
KB893066
KB893086
KB893756
KB893803
KB893803v2
KB894320
KB896358
KB896422
KB896423
KB896424
KB896688-IE6SP1-20051004.130236
KB896727-IE6SP1-20050719.165959
KB897715-OE6SP1-20050503.210336
KB899587
KB899588
KB899589
KB899591
KB900725
KB901017
KB901214
KB902400
KB904706
KB905414
KB905495-IE6SP1-20050805.184113
KB905749
KB905915-IE6SP1-20051122.175908
KB908519
KB908523
KB911564
KB912919
Q147222
Q828026
Update Rollup 1


Netcard queries test . . . . . . . : Passed



Per interface results:

Adapter : Local Area Connection

Netcard queries test . . . : Passed

Host Name. . . . . . . . . : pdc_rich.mydomain.com
IP Address . . . . . . . . : 10.1.16.2
Subnet Mask. . . . . . . . : 255.255.240.0
Default Gateway. . . . . . : 10.1.16.1
Primary WINS Server. . . . : 10.1.16.2
Secondary WINS Server. . . : 10.1.32.2
Dns Servers. . . . . . . . : 10.1.16.25
4.2.2.1

IpConfig results . . . . . : Failed
Pinging the Secondary WINS server 10.1.32.2 - not reachable

AutoConfiguration results. . . . . . : Passed

Default gateway test . . . : Passed

NetBT name test. . . . . . : Passed

WINS service test. . . . . : Passed


Global results:


Domain membership test . . . . . . : Passed


NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{E47CF2BF-C0FB-443A-AF9A-0EC79290C505}
1 NetBt transport currently configured.


Autonet address test . . . . . . . : Passed


IP loopback ping test. . . . . . . : Passed


Default gateway test . . . . . . . : Passed


NetBT name test. . . . . . . . . . : Passed


Winsock test . . . . . . . . . . . : Passed


DNS test . . . . . . . . . . . . . : Failed
[WARNING] The DNS host name 'pdc_rich.mydomain.com' valid only on Windows 2000 DNS Servers. [DNS_ERROR_NON_RFC_NAME]
[WARNING] Cannot find a primary authoritative DNS server for the name
'pdc_rich.mydomain.com.'. [RCODE_SERVER_FAILURE]
The name 'pdc_rich.mydomain.com.' may not be registered in DNS.
[WARNING] The DNS entries for this DC are not registered correctly on DNS server '10.1.16.25'. Please wait for 30 minutes for DNS server replication.
[WARNING] The DNS entries for this DC are not registered correctly on DNS server '4.2.2.1'. Please wait for 30 minutes for DNS server replication.
[FATAL] No DNS servers have the DNS records for this DC registered.


Redir and Browser test . . . . . . : Passed
List of NetBt transports currently bound to the Redir
NetBT_Tcpip_{E47CF2BF-C0FB-443A-AF9A-0EC79290C505}
The redir is bound to 1 NetBt transport.

List of NetBt transports currently bound to the browser
NetBT_Tcpip_{E47CF2BF-C0FB-443A-AF9A-0EC79290C505}
The browser is bound to 1 NetBt transport.


DC discovery test. . . . . . . . . : Passed


DC list test . . . . . . . . . . . : Passed


Trust relationship test. . . . . . : Skipped


Kerberos test. . . . . . . . . . . : Passed


LDAP test. . . . . . . . . . . . . : Passed
[WARNING] Failed to query SPN registration on DC 'pdc_rich.mydomain.com'.
[WARNING] Failed to query SPN registration on DC 'file02rich.mydomain.com'.


Bindings test. . . . . . . . . . . : Passed


WAN configuration test . . . . . . : Skipped
No active remote access connections.


Modem diagnostics test . . . . . . : Passed

IP Security test . . . . . . . . . : Passed
IPSec policy service is active, but no policy is assigned.


The command completed successfully

 

[mandg]

...and here's the log from the DCDiag program (replaced real domain name with mydomain.com);

=============================================

DC Diagnosis

Performing initial setup:
*** Warning: could not confirm the identity of this server in
the directory versus the names returned by DNS servers.
If there are problems accessing this directory server then
you may need to check that this server is correctly registered
with DNS
[10.1.16.2] Directory Binding Error 87:
The parameter is incorrect.
This may limit some of the tests that can be performed.
Done gathering initial info.

Doing initial non skippeable tests

Testing server: Default-First-Site-Name\PDC_RICH
Starting test: Connectivity
PDC_RICH's server GUID DNS name could not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name (5baaee45-4f08-4c8f-8e2d-ad13dabe732c._msdcs.mydomain.com) couldn't be resolved, the server name (pdc_rich.mydomain.com) resolved to the IP address (10.1.16.2) and was

pingable. Check that the IP address is registered correctly with the DNS server.
......................... PDC_RICH failed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\PDC_RICH
Skipping all tests, because server PDC_RICH is
not responding to directory service requests

Running enterprise tests on : mydomain.com
Starting test: Intersite
......................... mydomain.com passed test Intersite
Starting test: FsmoCheck
[PDC_RICH] DsBind() failed with error 1722,
The RPC server is unavailable..
......................... mydomain.com passed test FsmoCheck

 

[pQi]

If your domain name is labeled with an underscore, its an invalid DNS format...which in this case please follow the articles below:

Q292541
Q300684

If the above is not valid, do you have an entry in your reverse lookup zone for starters? If you do, is there an entry for your DNS server in other words (PTR) record? If not, add one.

Then do an ipconfig /flushdns
registerdns

Let me know