No DNS Server

  • Thread starter Thread starter Mike
  • Start date Start date
M

Mike

Hello,
When i run nslookup i get this
********************************************************
C:\Program Files\Support Tools>nslookup
*** Can't find server name for address 10.30.0.9: Non-existent domain
Default Server: s2.masd.org
Address: 10.30.0.8
********************************************************
10.30.0.9 is my PDC. When i started here, the second DC's address was used
in the IP properties of the clients. So i got rid of the root in the PDC
and made it work the way it should. All the clients now point to
thePDC(10.30.0.9) and things work fine, almost. At a certain time of day
the Internet goes down. i have to disable and enable the connections to get
it back up. i included a dcdiag a FRSdiag. Thanks again for your past help
and hopfully future.
*********************************************************
dcdiag PDC
C:\Program Files\Support Tools>dcdiag

Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: MinersvilleHighSchool\S1
Starting test: Connectivity
......................... S1 passed test Connectivity

Doing primary tests

Testing server: MinersvilleHighSchool\S1
Starting test: Replications
......................... S1 passed test Replications
Starting test: NCSecDesc
......................... S1 passed test NCSecDesc
Starting test: NetLogons
......................... S1 passed test NetLogons
Starting test: Advertising
......................... S1 passed test Advertising
Starting test: KnowsOfRoleHolders
......................... S1 passed test KnowsOfRoleHolders
Starting test: RidManager
......................... S1 passed test RidManager
Starting test: MachineAccount
* S1 is not trusted for account delegation
......................... S1 failed test MachineAccount
Starting test: Services
Could not open SMTPSVC Service on [S1]:failed with 1060: The
specifi
ed service does not exist as an installed service.
......................... S1 failed test Services
Starting test: ObjectsReplicated
......................... S1 passed test ObjectsReplicated
Starting test: frssysvol
......................... S1 passed test frssysvol
Starting test: kccevent
......................... S1 passed test kccevent
Starting test: systemlog
An Error Event occured. EventID: 0xC0001B70
Time Generated: 12/23/2003 11:49:38
Event String: The Messenger service terminated with
An Error Event occured. EventID: 0x800009CA
Time Generated: 12/23/2003 12:03:50
Event String: The value named IRPStackSize in the server's
An Error Event occured. EventID: 0x00004E8A
Time Generated: 12/23/2003 12:04:31
Event String: Unable to add the interface Internal with the
......................... S1 failed test systemlog

Running enterprise tests on : masd.org
Starting test: Intersite
......................... masd.org passed test Intersite
Starting test: FsmoCheck
......................... masd.org passed test FsmoCheck
**********************************************************
FRSDiag on PDC
------------------------------------------------------------
FRSDiag v1.7 on 12/23/2003 1:04:29 PM
..\S1 on 2003-12-23 at 1.04.29 PM
------------------------------------------------------------

Checking for errors/warnings in FRS Event Log ....
NtFrs 12/22/2003 1:47:49 PM Warning 13508 The File Replication Service is
having trouble enabling replication from S2 to S1 for
c:\winnt\sysvol\domain using the DNS name S2.masd.org. FRS will keep
retrying. Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name S2.masd.org from this
computer. [2] FRS is not running on S2.masd.org. [3] The topology
information in the Active Directory for this replica has not yet replicated
to all the Domain Controllers. This event log message will appear
once per connection, After the problem is fixed you will see another event
log message indicating that the connection has been established.
NtFrs 12/22/2003 1:22:48 PM Warning 13508 The File Replication Service is
having trouble enabling replication from S2 to S1 for
c:\winnt\sysvol\domain using the DNS name S2.masd.org. FRS will keep
retrying. Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name S2.masd.org from this
computer. [2] FRS is not running on S2.masd.org. [3] The topology
information in the Active Directory for this replica has not yet replicated
to all the Domain Controllers. This event log message will appear
once per connection, After the problem is fixed you will see another event
log message indicating that the connection has been established.
NtFrs 12/22/2003 8:27:01 AM Warning 13508 The File Replication Service is
having trouble enabling replication from S2 to S1 for
c:\winnt\sysvol\domain using the DNS name S2.masd.org. FRS will keep
retrying. Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name S2.masd.org from this
computer. [2] FRS is not running on S2.masd.org. [3] The topology
information in the Active Directory for this replica has not yet replicated
to all the Domain Controllers. This event log message will appear
once per connection, After the problem is fixed you will see another event
log message indicating that the connection has been established.
WARNING: Found Event ID 13508 errors without trailing 13509 ... see above
for (up to) the 3 latest entries!

......... failed 1
Checking for errors in Directory Service Event Log .... passed
Checking for minimum FRS version requirement ... passed
Checking for errors/warnings in ntfrsutl ds ... passed
Checking for Replica Set configuration triggers... passed
Checking for suspicious file Backlog size... passed
Checking Overall Disk Space and SYSVOL structure (note: integrity is not
checked)... passed
Checking for suspicious inlog entries ... passed
Checking for suspicious outlog entries ... passed
Checking for appropriate staging area size ... passed
Checking for errors in debug logs ...
ERROR on NtFrs_0004.log : "RPC_S_CALL_FAILED_DNE(Indicates RPC Session was
established to target, but there was a failure to send RPC call package.
Check for Networking problems!)" : <FrsDsGetName: 2784:
4516: S0: 14:15:50> :DS: ERROR - DsCrackNames(cn=s2,ou=domain
controllers,dc=masd,dc=org, 00000002); WStatus: RPC_S_CALL_FAILED_DNE
ERROR on NtFrs_0004.log : "RPC_S_CALL_FAILED_DNE(Indicates RPC Session was
established to target, but there was a failure to send RPC call package.
Check for Networking problems!)" : <FrsDsGetName: 2784:
4516: S0: 11:50:57> :DS: ERROR - DsCrackNames(cn=s2,ou=domain
controllers,dc=masd,dc=org, 00000002); WStatus: RPC_S_CALL_FAILED_DNE

Found 2 RPC_S_CALL_FAILED_DNE error(s)! Latest ones (up to 3) listed above

......... failed with 2 error entries
Checking NtFrs Service (and dependent services) state...passed
Checking NtFrs related Registry Keys for possible problems...passed
Checking Repadmin Showreps for errors...passed
*******************************************************
i hope it is not totaly messed up. i know this is a burden to look through
all this, i just din't know what to do. if anybody can point me in the
right direction i would appreciate it. thanks agian.
 
In
Mike said:
Hello,
When i run nslookup i get this
********************************************************
C:\Program Files\Support Tools>nslookup
*** Can't find server name for address 10.30.0.9: Non-existent domain
Default Server: s2.masd.org
Address: 10.30.0.8
********************************************************
10.30.0.9 is my PDC. When i started here, the second DC's address
was used in the IP properties of the clients. So i got rid of the
root in the PDC and made it work the way it should. All the clients
now point to thePDC(10.30.0.9) and things work fine, almost. At a
certain time of day the Internet goes down. i have to disable and
enable the connections to get it back up. i included a dcdiag a
FRSdiag. Thanks again for your past help and hopfully future.
*********************************************************
dcdiag PDC
C:\Program Files\Support Tools>dcdiag

Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: MinersvilleHighSchool\S1
Starting test: Connectivity
......................... S1 passed test Connectivity

Doing primary tests

Testing server: MinersvilleHighSchool\S1
Starting test: Replications
......................... S1 passed test Replications
Starting test: NCSecDesc
......................... S1 passed test NCSecDesc
Starting test: NetLogons
......................... S1 passed test NetLogons
Starting test: Advertising
......................... S1 passed test Advertising
Starting test: KnowsOfRoleHolders
......................... S1 passed test KnowsOfRoleHolders
Starting test: RidManager
......................... S1 passed test RidManager
Starting test: MachineAccount
* S1 is not trusted for account delegation
......................... S1 failed test MachineAccount
Starting test: Services
Could not open SMTPSVC Service on [S1]:failed with 1060:
The specifi
ed service does not exist as an installed service.
......................... S1 failed test Services
Starting test: ObjectsReplicated
......................... S1 passed test ObjectsReplicated
Starting test: frssysvol
......................... S1 passed test frssysvol
Starting test: kccevent
......................... S1 passed test kccevent
Starting test: systemlog
An Error Event occured. EventID: 0xC0001B70
Time Generated: 12/23/2003 11:49:38
Event String: The Messenger service terminated with
An Error Event occured. EventID: 0x800009CA
Time Generated: 12/23/2003 12:03:50
Event String: The value named IRPStackSize in the server's
An Error Event occured. EventID: 0x00004E8A
Time Generated: 12/23/2003 12:04:31
Event String: Unable to add the interface Internal with
the ......................... S1 failed test systemlog

Running enterprise tests on : masd.org
Starting test: Intersite
......................... masd.org passed test Intersite
Starting test: FsmoCheck
......................... masd.org passed test FsmoCheck
**********************************************************
FRSDiag on PDC
------------------------------------------------------------
FRSDiag v1.7 on 12/23/2003 1:04:29 PM
.\S1 on 2003-12-23 at 1.04.29 PM
------------------------------------------------------------

Checking for errors/warnings in FRS Event Log ....
NtFrs 12/22/2003 1:47:49 PM Warning 13508 The File Replication
Service is having trouble enabling replication from S2 to S1 for
c:\winnt\sysvol\domain using the DNS name S2.masd.org. FRS will keep
retrying. Following are some of the reasons you would see this
warning. [1] FRS can not correctly resolve the DNS name S2.masd.org
from this computer. [2] FRS is not running on S2.masd.org.
[3] The topology information in the Active Directory for this replica
has not yet replicated to all the Domain Controllers. This
event log message will appear once per connection, After the problem
is fixed you will see another event log message indicating that the
connection has been established.
NtFrs 12/22/2003 1:22:48 PM Warning 13508 The File Replication
Service is having trouble enabling replication from S2 to S1 for
c:\winnt\sysvol\domain using the DNS name S2.masd.org. FRS will keep
retrying. Following are some of the reasons you would see this
warning. [1] FRS can not correctly resolve the DNS name S2.masd.org
from this computer. [2] FRS is not running on S2.masd.org.
[3] The topology information in the Active Directory for this replica
has not yet replicated to all the Domain Controllers. This
event log message will appear once per connection, After the problem
is fixed you will see another event log message indicating that the
connection has been established.
NtFrs 12/22/2003 8:27:01 AM Warning 13508 The File Replication
Service is having trouble enabling replication from S2 to S1 for
c:\winnt\sysvol\domain using the DNS name S2.masd.org. FRS will keep
retrying. Following are some of the reasons you would see this
warning. [1] FRS can not correctly resolve the DNS name S2.masd.org
from this computer. [2] FRS is not running on S2.masd.org.
[3] The topology information in the Active Directory for this replica
has not yet replicated to all the Domain Controllers. This
event log message will appear once per connection, After the problem
is fixed you will see another event log message indicating that the
connection has been established. WARNING: Found Event ID 13508
errors without trailing 13509 ... see above for (up to) the 3 latest
entries!

......... failed 1
Checking for errors in Directory Service Event Log .... passed
Checking for minimum FRS version requirement ... passed
Checking for errors/warnings in ntfrsutl ds ... passed
Checking for Replica Set configuration triggers... passed
Checking for suspicious file Backlog size... passed
Checking Overall Disk Space and SYSVOL structure (note: integrity is
not checked)... passed
Checking for suspicious inlog entries ... passed
Checking for suspicious outlog entries ... passed
Checking for appropriate staging area size ... passed
Checking for errors in debug logs ...
ERROR on NtFrs_0004.log : "RPC_S_CALL_FAILED_DNE(Indicates RPC
Session was established to target, but there was a failure to send
RPC call package. Check for Networking problems!)" : <FrsDsGetName:
2784: 4516: S0: 14:15:50> :DS: ERROR - DsCrackNames(cn=s2,ou=domain
controllers,dc=masd,dc=org, 00000002); WStatus: RPC_S_CALL_FAILED_DNE
ERROR on NtFrs_0004.log : "RPC_S_CALL_FAILED_DNE(Indicates RPC
Session was established to target, but there was a failure to send
RPC call package. Check for Networking problems!)" : <FrsDsGetName:
2784: 4516: S0: 11:50:57> :DS: ERROR - DsCrackNames(cn=s2,ou=domain
controllers,dc=masd,dc=org, 00000002); WStatus: RPC_S_CALL_FAILED_DNE

Found 2 RPC_S_CALL_FAILED_DNE error(s)! Latest ones (up to 3) listed
above

......... failed with 2 error entries
Checking NtFrs Service (and dependent services) state...passed
Checking NtFrs related Registry Keys for possible problems...passed
Checking Repadmin Showreps for errors...passed
*******************************************************
i hope it is not totaly messed up. i know this is a burden to look
through all this, i just din't know what to do. if anybody can point
me in the right direction i would appreciate it. thanks agian.
Click to expand...

Sounds like a couple things. I would first check the clients with an
ipconfig /all to insure that only the internal DNS shows up. If an external
DNS is in there, I would change it if a static entry and/or if uysing DHCP,
check your DHCP Option 006 to insure ONLY the internal DNS shows up. This is
evident by the mere fact you have to disable/enable the connections. Hope
you're not using your router as a DHCP server.

Same with the DC. FRS errors, and other numerous errors will show up if
still referencing your ISP's or router as a DNS server on the DCs.

Setup a forwarder on your internal DNS to your ISP's DNS. If not sure how,
see this article:
http://support.microsoft.com/?id=300202

FYI: There is no such thing as a PDC in AD. Legacy terminology that pertains
to NT4 only. There are replica DCs, so you have DC1, DC2, etc. There is a
PDC Emulator FSMO Role that one of the DCs performs to "act" as a PDC for
backware level clients, time synch, password changes, etc, but it is NOT a
PDC, but rather a DC that just happens to hold that role.

The nslookup message (note: this is NOT an error) just says that you do not
have a reverse zone. If you do, there is not PTR entry for the DNS server's
IP address pointing to it;s name. Nslookup upon intialization is just doing
you a "favor" by looking up in your reverse zone for the name of the server.
That;'s it. So just create a reverse zone and make sure the DNS server has a
PTR entry in it to eliminate that "message", otherwise nslookup will still
function.

Also enable the SMTP service on this machine. AD uses it in certain
circumstances (depending on your Sites links configuration). That is the one
error that I see too.

More info on the 13508 and 13509 errors:
http://www.eventid.net/display.asp?eventid=13508&source=
http://www.eventid.net/display.asp?eventid=13509&source=

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
M> When i run nslookup i get this
M> ********************************************************
M> C:\Program Files\Support Tools>nslookup
M> *** Can't find server name for address 10.30.0.9: Non-existent domain

<URL:http://homepages.tesco.net./~J.deBoynePollard/FGA/nslookup-daft-error-message.html>

M> At a certain time of day the Internet goes down.

Please define "goes down". What is the "certain time of day" ?

<URL:http://homepages.tesco.net./~J.deBoynePollard/FGA/problem-report-standard-litany.html>

Have you tested your ICMP/IP connectivity to the rest of
Internet during this period ?
 
Back
Top