Problems AD / GC /DNS

[mysticslayer]

Hi everyone,

I've got the following problems regarding my domain:

I got a hosted domain at a hosting provider called mysticslayer.nl
This mysticslayer.nl I also used for creating my Domain at home.

My Ip info of my PDC

IP : 192.168.1.2
Sub : 255.255.255.0
Gate : 192.168.1.254

DNS Primary: 192.168.1.254 (Or my internet will fail)
DNS Secondary: 82.98.232.11 (Hosting Provider)

When I run ldp:

ld = ldap_open("athome-pdc.mysticslayer.nl", 389);
Established connection to athome-pdc.mysticslayer.nl.
Retrieving base DSA information...
Result <0>: (null)
Matched DNs:
Getting 1 entries:
>> Dn:
1> currentTime: 09/02/2008 13:05:47 W. Europe Standard Time W. Europe Daylight Time;
1> subschemaSubentry: CN=Aggregate,CN=Schema,CN=Configuration,DC=mysticslayer,DC=nl;
1> dsServiceName: CN=NTDS Settings,CN=ATHOME-PDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=mysticslayer,DC=nl;
5> namingContexts: DC=mysticslayer,DC=nl; CN=Configuration,DC=mysticslayer,DC=nl; CN=Schema,CN=Configuration,DC=mysticslayer,DC=nl; DC=DomainDnsZones,DC=mysticslayer,DC=nl; DC=ForestDnsZones,DC=mysticslayer,DC=nl;
1> defaultNamingContext: DC=mysticslayer,DC=nl;
1> schemaNamingContext: CN=Schema,CN=Configuration,DC=mysticslayer,DC=nl;
1> configurationNamingContext: CN=Configuration,DC=mysticslayer,DC=nl;
1> rootDomainNamingContext: DC=mysticslayer,DC=nl;
23> supportedControl: 1.2.840.113556.1.4.319; 1.2.840.113556.1.4.801; 1.2.840.113556.1.4.473; 1.2.840.113556.1.4.528; 1.2.840.113556.1.4.417; 1.2.840.113556.1.4.619; 1.2.840.113556.1.4.841; 1.2.840.113556.1.4.529; 1.2.840.113556.1.4.805; 1.2.840.113556.1.4.521; 1.2.840.113556.1.4.970; 1.2.840.113556.1.4.1338; 1.2.840.113556.1.4.474; 1.2.840.113556.1.4.1339; 1.2.840.113556.1.4.1340; 1.2.840.113556.1.4.1413; 2.16.840.1.113730.3.4.9; 2.16.840.1.113730.3.4.10; 1.2.840.113556.1.4.1504; 1.2.840.113556.1.4.1852; 1.2.840.113556.1.4.802; 1.2.840.113556.1.4.1907; 1.2.840.113556.1.4.1948;
2> supportedLDAPVersion: 3; 2;
12> supportedLDAPPolicies: MaxPoolThreads; MaxDatagramRecv; MaxReceiveBuffer; InitRecvTimeout; MaxConnections; MaxConnIdleTime; MaxPageSize; MaxQueryDuration; MaxTempTableSize; MaxResultSetSize; MaxNotificationPerConn; MaxValRange;
1> highestCommittedUSN: 20782;
4> supportedSASLMechanisms: GSSAPI; GSS-SPNEGO; EXTERNAL; DIGEST-MD5;
1> dnsHostName: athome-pdc.mysticslayer.nl;
1> ldapServiceName: mysticslayer.nl:athome-pdc$@MYSTICSLAYER.NL;
1> serverName: CN=ATHOME-PDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=mysticslayer,DC=nl;
3> supportedCapabilities: 1.2.840.113556.1.4.800; 1.2.840.113556.1.4.1670; 1.2.840.113556.1.4.1791;
1> isSynchronized: TRUE;
1> isGlobalCatalogReady: TRUE;
1> domainFunctionality: 2 = ( DS_BEHAVIOR_WIN2003 );
1> forestFunctionality: 0 = ( DS_BEHAVIOR_WIN2000 );
1> domainControllerFunctionality: 2 = ( DS_BEHAVIOR_WIN2003 );
-----------

C:\Documents and Settings\Administrator.ATHOME-PDC.001>dcdiag /test:connectivity


Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\ATHOME-PDC
Starting test: Connectivity
*** 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
......................... ATHOME-PDC passed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\ATHOME-PDC

Running partition tests on : ForestDnsZones

Running partition tests on : DomainDnsZones

Running partition tests on : Schema

Running partition tests on : Configuration

Running partition tests on : mysticslayer

Running enterprise tests on : mysticslayer.nl

C:\Documents and Settings\Administrator.ATHOME-PDC.001>dcdiag /dnsall

Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\ATHOME-PDC
Starting test: Connectivity
*** 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
......................... ATHOME-PDC passed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\ATHOME-PDC
Starting test: Replications
......................... ATHOME-PDC passed test Replications
Starting test: NCSecDesc
......................... ATHOME-PDC passed test NCSecDesc
Starting test: NetLogons
......................... ATHOME-PDC passed test NetLogons
Starting test: Advertising
......................... ATHOME-PDC passed test Advertising
Starting test: KnowsOfRoleHolders
......................... ATHOME-PDC passed test KnowsOfRoleHolders
Starting test: RidManager
......................... ATHOME-PDC passed test RidManager
Starting test: MachineAccount
......................... ATHOME-PDC passed test MachineAccount
Starting test: Services
......................... ATHOME-PDC passed test Services
Starting test: ObjectsReplicated
......................... ATHOME-PDC passed test ObjectsReplicated
Starting test: frssysvol
......................... ATHOME-PDC passed test frssysvol
Starting test: frsevent
......................... ATHOME-PDC passed test frsevent
Starting test: kccevent
......................... ATHOME-PDC passed test kccevent
Starting test: systemlog
......................... ATHOME-PDC passed test systemlog
Starting test: VerifyReferences
......................... ATHOME-PDC passed test VerifyReferences

Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test CrossRefValidatin

Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom

Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed test CrossRefValidati

Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom

Running partition tests on : Schema
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom

Running partition tests on : Configuration
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidatio
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom

Running enterprise tests on : mysticslayer.nl
Starting test: Intersite
......................... mysticslayer.nl passed test Intersite
Starting test: FsmoCheck
......................... mysticslayer.nl passed test FsmoCheck

When I look at my reverse lookup zones and watch my soa files I adds 3 IP addresses.

192.168.1.2 (PDC)
192.168.0.1 (Unknown and not pingable)
192.168.32.1 (Unknown and not pingable)

Can someone help me, or asks me what I have to do to give you more info...?

 

[mysticslayer]

Also I tried to use dcpromo:

C:\Documents and Settings\Administrator.ATHOME-PDC.001>dcdiag /test:registerindn
s /dnsdomain:mysticslayer.nl /v
Starting test: RegisterInDNS
DcDiag cannot reach a conclusive result because it cannot interpret the
following message that was returned: 9501.

......................... athome-pdc failed test RegisterInDNS

C:\Documents and Settings\Administrator.ATHOME-PDC.001>

 

[mysticslayer]

C:\Documents and Settings\Administrator.ATHOME-PDC.001>dcdiag /test:dcpromo /dns
domain:mysticslayer.nl /NewTree /ForestRoot:athome-pdc.mysticslayer.nl /v
Starting test: DcPromo
This computer cannot be promoted as a first domain controller of the
domain named mysticslayer.nl. This is because either the DNS SRV record
for _ldap._tcp.dc._msdcs.athome-pdc.mysticslayer.nl is not registered in
DNS, or some zone from the following list of DNS zones does not include
delegation to its child zone:
athome-pdc.mysticslayer.nl, mysticslayer.nl, nl

Ask your network/DNS administrator to perform the following actions: To
find out why the SRV record for _ldap._tcp.dc._msdcs.mysticslayer.nl is
not registered in DNS, run the dcdiag command prompt tool with the
command RegisterInDNS on the domain controller that did not perform the
registration.

Messages logged below this line indicate whether this domain controller
will be able to dynamically register DNS records required for the
location of this DC by other devices on the network. If any
misconfiguration is detected, it might prevent dynamic DNS registration
of some records, but does not prevent successful completion of the Active
Directory Installation Wizard. However, we recommend fixing the reported
problems now, unless you plan to manually update the DNS database.

DNS configuration is sufficient to allow this domain controller to
dynamically register the domain controller Locator records in DNS.

The DNS configuration is sufficient to allow this computer to dynamically
register the A record corresponding to its DNS name.

......................... athome-pdc failed test DcPromo

Does anyone how to fix this issue?