fasahat

  • Thread starter Thread starter dns error
  • Start date Start date
D

dns error

guys
i think i am really screwed.i cannot get my srv
records back on my win2k PDC AND BDC since my dns is
active directory integrated.i deleted and recreated the
forward lookup zones as described in
articlehttp://support.microsoft.com/?kbid=310568
IT is of no help.i ran the repadmin/show reps from the cmd
to test replication it is giving following
error.C:\Documents and Settings\fasahat>repadmin /showreps
gscserver1
Default-First-Site-Name\GSCSERVER1
DSA Options : IS_GC
objectGuid : ce2b919a-f666-48d7-b91d-5632a1673379
invocationID: ce2b919a-f666-48d7-b91d-5632a1673379

==== INBOUND NEIGHBORS
======================================

CN=Schema,CN=Configuration,DC=gct
Default-First-Site-Name\GSCSERVER4
DEL:9e1cb4ed-bf7a-4fa4-9910-ffa718c084e8 (deleted DSA) via
RPC
objectGuid: 9270f080-3606-44c6-8973-53fd4bc040d7
Default-First-Site-Name\GSCSERVER4
DEL:243dbd4d-850e-4b21-8ed8-b39ddcbdab53 (deleted DSA) via
RPC
objectGuid: 9713b428-61ad-4c4e-a24d-d2c2ef3c421b
Default-First-Site-Name\GSCSERVER3 via RPC
objectGuid: 2ad53db2-eb5e-4ef9-969a-7b4b12bc6aa4
Last attempt @ 2004-09-30 11:45.36 failed, result
8524:
The DSA operation is unable to proceed because
of a DNS lookup failu
re.
Last success @ 2004-09-18 01:58.55.
310 consecutive failure(s).
Default-First-Site-Name\GSCSERVER4
DEL:9e1cb4ed-bf7a-4fa4-9910-ffa718c084e8 (deleted DSA) via
RPC
objectGuid: 93db7dff-913d-4ca5-b76f-664374d9e508
Default-First-Site-Name\GSCSERVER4
DEL:9e1cb4ed-bf7a-4fa4-9910-ffa718c084e8 (deleted DSA) via
RPC
objectGuid: 0fd444ef-ab50-462d-b414-039977d2b65f
Default-First-Site-Name\GSCCPDC
DEL:58f6e4fb-c018-4b6c-bd50-a79b67b1641e (deleted DSA) via
RPC
objectGuid: b292d413-21e1-4fc1-840e-5d281c0ad39f

CN=Configuration,DC=gct
Default-First-Site-Name\GSCSERVER4
DEL:9e1cb4ed-bf7a-4fa4-9910-ffa718c084e8 (deleted DSA) via
RPC
objectGuid: 9270f080-3606-44c6-8973-53fd4bc040d7
Default-First-Site-Name\GSCSERVER4
DEL:243dbd4d-850e-4b21-8ed8-b39ddcbdab53 (deleted DSA) via
RPC
objectGuid: 9713b428-61ad-4c4e-a24d-d2c2ef3c421b
Default-First-Site-Name\GSCSERVER3 via RPC
objectGuid: 2ad53db2-eb5e-4ef9-969a-7b4b12bc6aa4
Last attempt @ 2004-09-30 11:45.35 failed, result
8524:
The DSA operation is unable to proceed because
of a DNS lookup failu
re.
Last success @ 2004-09-18 01:58.55.
310 consecutive failure(s).
Default-First-Site-Name\GSCSERVER4
DEL:9e1cb4ed-bf7a-4fa4-9910-ffa718c084e8 (deleted DSA) via
RPC
objectGuid: 93db7dff-913d-4ca5-b76f-664374d9e508
Default-First-Site-Name\GSCSERVER4
DEL:9e1cb4ed-bf7a-4fa4-9910-ffa718c084e8 (deleted DSA) via
RPC
objectGuid: 0fd444ef-ab50-462d-b414-039977d2b65f
Default-First-Site-Name\GSCCPDC
DEL:58f6e4fb-c018-4b6c-bd50-a79b67b1641e (deleted DSA) via
RPC
objectGuid: b292d413-21e1-4fc1-840e-5d281c0ad39f

DC=gct
Default-First-Site-Name\GSCSERVER4
DEL:9e1cb4ed-bf7a-4fa4-9910-ffa718c084e8 (deleted DSA) via
RPC
objectGuid: 9270f080-3606-44c6-8973-53fd4bc040d7
Default-First-Site-Name\GSCSERVER4
DEL:243dbd4d-850e-4b21-8ed8-b39ddcbdab53 (deleted DSA) via
RPC
objectGuid: 9713b428-61ad-4c4e-a24d-d2c2ef3c421b
Default-First-Site-Name\GSCSERVER3 via RPC
objectGuid: 2ad53db2-eb5e-4ef9-969a-7b4b12bc6aa4
Last attempt @ 2004-09-30 11:45.35 failed, result
8524:
The DSA operation is unable to proceed because
of a DNS lookup failu
re.
Last success @ 2004-09-18 01:58.55.
310 consecutive failure(s).
Default-First-Site-Name\GSCSERVER4
DEL:9e1cb4ed-bf7a-4fa4-9910-ffa718c084e8 (deleted DSA) via
RPC
objectGuid: 93db7dff-913d-4ca5-b76f-664374d9e508
Default-First-Site-Name\GSCSERVER4
DEL:9e1cb4ed-bf7a-4fa4-9910-ffa718c084e8 (deleted DSA) via
RPC
objectGuid: 0fd444ef-ab50-462d-b414-039977d2b65f
Default-First-Site-Name\GSCCPDC
DEL:58f6e4fb-c018-4b6c-bd50-a79b67b1641e (deleted DSA) via
RPC
objectGuid: b292d413-21e1-4fc1-840e-5d281c0ad39f

==== OUTBOUND NEIGHBORS FOR CHANGE NOTIFICATIONS
============

CN=Schema,CN=Configuration,DC=gct
Default-First-Site-Name\GSCSERVER3 via RPC
objectGuid: 2ad53db2-eb5e-4ef9-969a-7b4b12bc6aa4

CN=Configuration,DC=gct
Default-First-Site-Name\GSCSERVER3 via RPC
objectGuid: 2ad53db2-eb5e-4ef9-969a-7b4b12bc6aa4

DC=gct
Default-First-Site-Name\GSCSERVER3 via RPC
objectGuid: 2ad53db2-eb5e-4ef9-969a-7b4b12bc6aa4

also ran nltest command:got the following error
C:\Documents and
Settings\fasahat>nltest /dsgetdc:gct /site:gctsite
DsGetDcName failed: Status = 1355 0x54b
ERROR_NO_SUCH_DOMAIN.
i think the replication is also not working between two
dc,s.
i don,t want to rebuild my domain.

regards
fasahat
 
In
dns error said:
guys
i think i am really screwed.i cannot get my srv
records back on my win2k PDC AND BDC since my dns is
active directory integrated.i deleted and recreated the
forward lookup zones as described in
articlehttp://support.microsoft.com/?kbid=310568
IT is of no help.i ran the repadmin/show reps from the cmd
to test replication it is giving following
error.C:\Documents and Settings\fasahat>repadmin /showreps
gscserver1
Default-First-Site-Name\GSCSERVER1
DSA Options : IS_GC
objectGuid : ce2b919a-f666-48d7-b91d-5632a1673379
invocationID: ce2b919a-f666-48d7-b91d-5632a1673379

==== INBOUND NEIGHBORS
======================================

CN=Schema,CN=Configuration,DC=gct
Default-First-Site-Name\GSCSERVER4
DEL:9e1cb4ed-bf7a-4fa4-9910-ffa718c084e8 (deleted DSA) via
RPC
objectGuid: 9270f080-3606-44c6-8973-53fd4bc040d7
Default-First-Site-Name\GSCSERVER4
DEL:243dbd4d-850e-4b21-8ed8-b39ddcbdab53 (deleted DSA) via
RPC
objectGuid: 9713b428-61ad-4c4e-a24d-d2c2ef3c421b
Default-First-Site-Name\GSCSERVER3 via RPC
objectGuid: 2ad53db2-eb5e-4ef9-969a-7b4b12bc6aa4
Last attempt @ 2004-09-30 11:45.36 failed, result
8524:
The DSA operation is unable to proceed because
of a DNS lookup failu
re.
Last success @ 2004-09-18 01:58.55.
310 consecutive failure(s).
Default-First-Site-Name\GSCSERVER4
DEL:9e1cb4ed-bf7a-4fa4-9910-ffa718c084e8 (deleted DSA) via
RPC
objectGuid: 93db7dff-913d-4ca5-b76f-664374d9e508
Default-First-Site-Name\GSCSERVER4
DEL:9e1cb4ed-bf7a-4fa4-9910-ffa718c084e8 (deleted DSA) via
RPC
objectGuid: 0fd444ef-ab50-462d-b414-039977d2b65f
Default-First-Site-Name\GSCCPDC
DEL:58f6e4fb-c018-4b6c-bd50-a79b67b1641e (deleted DSA) via
RPC
objectGuid: b292d413-21e1-4fc1-840e-5d281c0ad39f

CN=Configuration,DC=gct
Default-First-Site-Name\GSCSERVER4
DEL:9e1cb4ed-bf7a-4fa4-9910-ffa718c084e8 (deleted DSA) via
RPC
objectGuid: 9270f080-3606-44c6-8973-53fd4bc040d7
Default-First-Site-Name\GSCSERVER4
DEL:243dbd4d-850e-4b21-8ed8-b39ddcbdab53 (deleted DSA) via
RPC
objectGuid: 9713b428-61ad-4c4e-a24d-d2c2ef3c421b
Default-First-Site-Name\GSCSERVER3 via RPC
objectGuid: 2ad53db2-eb5e-4ef9-969a-7b4b12bc6aa4
Last attempt @ 2004-09-30 11:45.35 failed, result
8524:
The DSA operation is unable to proceed because
of a DNS lookup failu
re.
Last success @ 2004-09-18 01:58.55.
310 consecutive failure(s).
Default-First-Site-Name\GSCSERVER4
DEL:9e1cb4ed-bf7a-4fa4-9910-ffa718c084e8 (deleted DSA) via
RPC
objectGuid: 93db7dff-913d-4ca5-b76f-664374d9e508
Default-First-Site-Name\GSCSERVER4
DEL:9e1cb4ed-bf7a-4fa4-9910-ffa718c084e8 (deleted DSA) via
RPC
objectGuid: 0fd444ef-ab50-462d-b414-039977d2b65f
Default-First-Site-Name\GSCCPDC
DEL:58f6e4fb-c018-4b6c-bd50-a79b67b1641e (deleted DSA) via
RPC
objectGuid: b292d413-21e1-4fc1-840e-5d281c0ad39f

DC=gct
Default-First-Site-Name\GSCSERVER4
DEL:9e1cb4ed-bf7a-4fa4-9910-ffa718c084e8 (deleted DSA) via
RPC
objectGuid: 9270f080-3606-44c6-8973-53fd4bc040d7
Default-First-Site-Name\GSCSERVER4
DEL:243dbd4d-850e-4b21-8ed8-b39ddcbdab53 (deleted DSA) via
RPC
objectGuid: 9713b428-61ad-4c4e-a24d-d2c2ef3c421b
Default-First-Site-Name\GSCSERVER3 via RPC
objectGuid: 2ad53db2-eb5e-4ef9-969a-7b4b12bc6aa4
Last attempt @ 2004-09-30 11:45.35 failed, result
8524:
The DSA operation is unable to proceed because
of a DNS lookup failu
re.
Last success @ 2004-09-18 01:58.55.
310 consecutive failure(s).
Default-First-Site-Name\GSCSERVER4
DEL:9e1cb4ed-bf7a-4fa4-9910-ffa718c084e8 (deleted DSA) via
RPC
objectGuid: 93db7dff-913d-4ca5-b76f-664374d9e508
Default-First-Site-Name\GSCSERVER4
DEL:9e1cb4ed-bf7a-4fa4-9910-ffa718c084e8 (deleted DSA) via
RPC
objectGuid: 0fd444ef-ab50-462d-b414-039977d2b65f
Default-First-Site-Name\GSCCPDC
DEL:58f6e4fb-c018-4b6c-bd50-a79b67b1641e (deleted DSA) via
RPC
objectGuid: b292d413-21e1-4fc1-840e-5d281c0ad39f

==== OUTBOUND NEIGHBORS FOR CHANGE NOTIFICATIONS
============

CN=Schema,CN=Configuration,DC=gct
Default-First-Site-Name\GSCSERVER3 via RPC
objectGuid: 2ad53db2-eb5e-4ef9-969a-7b4b12bc6aa4

CN=Configuration,DC=gct
Default-First-Site-Name\GSCSERVER3 via RPC
objectGuid: 2ad53db2-eb5e-4ef9-969a-7b4b12bc6aa4

DC=gct
Default-First-Site-Name\GSCSERVER3 via RPC
objectGuid: 2ad53db2-eb5e-4ef9-969a-7b4b12bc6aa4

also ran nltest command:got the following error
C:\Documents and
Settings\fasahat>nltest /dsgetdc:gct /site:gctsite
DsGetDcName failed: Status = 1355 0x54b
ERROR_NO_SUCH_DOMAIN.
i think the replication is also not working between two
dc,s.
i don,t want to rebuild my domain.

regards
fasahat
Click to expand...

As I posted to your other thread...

If your machine and Active Directory configuration and IP properties are
misconfigured, reinstalling DNS will not help. There are a number of reasons
why SRVs will not register, but we will need more information from you to
ascertain why. There are a number of reasons why you are getting all of
these errors, which invariably are indicative of missing SRVs.

To better assist you, please post this information below so we can diagnose
why your SRV records are not showing up:

1. Unedited ipconfig /all
2. Name of your AD DNS Domain name
3. Name of the zone in DNS and if updates are allowed.

Thanks.

--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services

Security Is Like An Onion, It Has Layers
HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.
 
hi ace
please find the required information
ipconfig/all
indows 2000 IP Configuration



Host Name . . . . . . . . . . . . : gscserver1
Primary DNS Suffix . . . . . . . : gct
Node Type . . . . . . . . . . . . : Broadcast

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : gct

Ethernet adapter Local Area Connection:



Connection-specific DNS Suffix . : gct
Description . . . . . . . . . . . : Intel(R)
PRO/1000 MT Network Connection
Physical Address. . . . . . . . . : 00-08-74-0F-9B-
B2

DHCP Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 220.110.0.231

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 220.110.0.254

DNS Servers . . . . . . . . . . . : 220.110.0.231
Active Directory Domain name:GCT
Dns Forward Lookup Zone on PDC GSCSERVERI.
GSCSERVER1.GCT.
Dns Forward Lookup Zone on BDC:GSCSERVER3.
GSCSERVER3.GCT.
I have my forward lookup zones and Revers Lookup zone on
both Domain Controllers.I deleted my forward lookup zones
on both servers and recreated them.ran ipconfig/register
started and restarted my netlogon services.still i cannot
get the srv back.i think there are no updates between the
two dc,s
my pdc dns server is acting as a forwarder.
my domain is still working.i can create new users on my
pdc,but i cannot create users and mail boxes on my BDC and
Exchange.it is giving an erroe no global catalog found.

need your help guys.

fasahat.
i had my
 
In
fasahat said:
hi ace
please find the required information
ipconfig/all
indows 2000 IP Configuration



Host Name . . . . . . . . . . . . : gscserver1
Primary DNS Suffix . . . . . . . : gct
Node Type . . . . . . . . . . . . : Broadcast

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : gct

Ethernet adapter Local Area Connection:



Connection-specific DNS Suffix . : gct
Description . . . . . . . . . . . : Intel(R)
PRO/1000 MT Network Connection
Physical Address. . . . . . . . . : 00-08-74-0F-9B-
B2

DHCP Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 220.110.0.231

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 220.110.0.254

DNS Servers . . . . . . . . . . . : 220.110.0.231
Active Directory Domain name:GCT
Dns Forward Lookup Zone on PDC GSCSERVERI.
GSCSERVER1.GCT.
Dns Forward Lookup Zone on BDC:GSCSERVER3.
GSCSERVER3.GCT.
Click to expand...

Both of these forward lookup zones are incorrect, create a new forward
lookup zone preferably AD integrated, name it GCT make sure allow dynamic
updates are allowed.
You have two DCs? Point both DCs to one of the DCs for DNS and create the
zone on that DC. After you create the zone restart the netlogon service on
both DCs run ipconfig /registerdns. It should take about 15 minutes for this
zone to replicate to both DCs, then point each DC to the other for preferred
DNS then to itself for alternate after the zone is replicated.

Create this zone ONLY on ONE DC!
Let replication create the zone on the other.
 
In
Kevin D. Goodknecht Sr. said:
Both of these forward lookup zones are incorrect, create a new forward
lookup zone preferably AD integrated, name it GCT make sure allow
dynamic updates are allowed.
You have two DCs? Point both DCs to one of the DCs for DNS and create
the zone on that DC. After you create the zone restart the netlogon
service on both DCs run ipconfig /registerdns. It should take about
15 minutes for this zone to replicate to both DCs, then point each DC
to the other for preferred DNS then to itself for alternate after the
zone is replicated.

Create this zone ONLY on ONE DC!
Let replication create the zone on the other.
Click to expand...

Kevin, not sure if you caught that, but its a single label name domain. You
may have and just forgot to add it in your post. He'll need to look at this
article to overcome this problem, unless he chooses to rename the domain.

300684 - Information About Configuring Windows 2000 for Domains with
Single-Label DNS Names:
http://support.microsoft.com/?id=300684

826743 - Clients cannot dynamically register DNS records in a single-label
forward lookup zone:
http://support.microsoft.com/default.aspx?scid=kb;en-us;826743


Ace
 
In Ace Fekay [MVP] <PleaseSubstituteMyActualFirstName&[email protected]>
commented
Then Kevin replied below:
In

Kevin, not sure if you caught that, but its a single
label name domain.
Click to expand...

I caught that and advised him of the single-label domain and registry
entries in his other thread (Srv Records) in this group. I'm not sure why he
decided to start a new thread. He said in that thread he is SP3, maybe that
is why he is still at the SP3 level. IMO that's a bad reason, SP4 has a lot
more fixes that just this, he needs to make the Registry entries then
install SP4. To me it makes good sense to make the registry entries while
still SP3, then go ahead and install SP4.
 
In
Kevin D. Goodknecht Sr. said:
I caught that and advised him of the single-label domain and registry
entries in his other thread (Srv Records) in this group. I'm not sure
why he decided to start a new thread. He said in that thread he is
SP3, maybe that is why he is still at the SP3 level. IMO that's a bad
reason, SP4 has a lot more fixes that just this, he needs to make the
Registry entries then install SP4. To me it makes good sense to make
the registry entries while still SP3, then go ahead and install SP4.
Click to expand...


Its difficult to follow multi-threads or multi-posted threads. If the thread
was cross-posted, we can collaborate on the issue as a whole. I guess this
is a good example of when we're doubling up and repeating responses, for I
wouldn't have made that addition if I knew.

Please, this is for everyone out there, try to keep everything in one post
and cross-post, do not multi-post. It helps you out better in the long run.

:-)
 
In Ace Fekay [MVP] <PleaseSubstituteMyActualFirstName&[email protected]>
commented
Then Kevin replied below:
In


Its difficult to follow multi-threads or multi-posted
threads. If the thread was cross-posted, we can
collaborate on the issue as a whole. I guess this is a
good example of when we're doubling up and repeating
responses, for I wouldn't have made that addition if I
knew.

Please, this is for everyone out there, try to keep
everything in one post and cross-post, do not multi-post.
It helps you out better in the long run.

:-)
Click to expand...

No problem, I was talking to him about migrating this to a different domain
name. I didn't realize in that thread that his zones were mis-named.
 
Back
Top