DNS does not display client records

My network is forest and domain function 2003. All DNS servers build in with
DC, active-directory-integrated and all DNS servers in the active directory
domain. Three DNS on the one site do not display host records. But servers,
switches, printers and PCs with static IP are displayed. Clients can resolve
their DNS names fine by PING or NSLOOKUP. DHCP is running on the same server
and dynamic updates are enabled. All PCs run XP with sp3. Internet FQDN
resolution is working. I can not find any error message of DNS from DC
servers and PCs.
Any suggestions on how to fix the issue?
Thanks a lot!

George Wang

>
>
> Any suggestions on how to fix the issue?
>
The "issue" appears to be from what you write that everything is
working, your servers are providing the right answers when asked, and
the only thing is that you haven't managed to work out how to see the
DNS data in the management console for the servers. There doesn't seem
to be much to fix in such a case.

"George" <> wrote in message
news:6A12405C-F89C-4586-8219-...
> My network is forest and domain function 2003. All DNS servers build in
> with
> DC, active-directory-integrated and all DNS servers in the active
> directory
> domain. Three DNS on the one site do not display host records. But
> servers,
> switches, printers and PCs with static IP are displayed. Clients can
> resolve
> their DNS names fine by PING or NSLOOKUP. DHCP is running on the same
> server
> and dynamic updates are enabled. All PCs run XP with sp3. Internet FQDN
> resolution is working. I can not find any error message of DNS from DC
> servers and PCs.
> Any suggestions on how to fix the issue?
> Thanks a lot!
>
> George Wang
>


If only one DNS server at one site, assuming it is a DC, is not showing
records of the same zone that other DC/DNS are, then it is telling theer is
possibly an AD replication problem. This is all assuming that the zone is AD
integrated.

To better help, please post the following:

1. Unedited ipconfig /all of the bad DC and a working DC.
2. EventID#s of errors in the event logs of any of the DCs.
3. Are any DCs multihomed (meaning with more than one NIC installed, more
than one IP, or that has RRAS installed)?


--
Ace

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

Please reply back to the newsgroup or forum for collaboration benefit among
responding engineers, and to help others benefit from your resolution.

Ace Fekay, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE &
MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services

If you feel this is an urgent issue and require immediate assistance, please
contact Microsoft PSS directly. Please check http://support.microsoft.com
for regional support phone numbers.

"Ace Fekay [MVP-DS, MCT]" wrote:

> "George" <> wrote in message
> news:6A12405C-F89C-4586-8219-...
> > My network is forest and domain function 2003. All DNS servers build in
> > with
> > DC, active-directory-integrated and all DNS servers in the active
> > directory
> > domain. Three DNS on the one site do not display host records. But
> > servers,
> > switches, printers and PCs with static IP are displayed. Clients can
> > resolve
> > their DNS names fine by PING or NSLOOKUP. DHCP is running on the same
> > server
> > and dynamic updates are enabled. All PCs run XP with sp3. Internet FQDN
> > resolution is working. I can not find any error message of DNS from DC
> > servers and PCs.
> > Any suggestions on how to fix the issue?
> > Thanks a lot!
> >
> > George Wang
> >
>
>
> If only one DNS server at one site, assuming it is a DC, is not showing
> records of the same zone that other DC/DNS are, then it is telling theer is
> possibly an AD replication problem. This is all assuming that the zone is AD
> integrated.
>
> To better help, please post the following:
>
> 1. Unedited ipconfig /all of the bad DC and a working DC.
> 2. EventID#s of errors in the event logs of any of the DCs.
> 3. Are any DCs multihomed (meaning with more than one NIC installed, more
> than one IP, or that has RRAS installed)?
>
>
> --
> Ace
>
> This posting is provided "AS-IS" with no warranties or guarantees and
> confers no rights.
>
> Please reply back to the newsgroup or forum for collaboration benefit among
> responding engineers, and to help others benefit from your resolution.
>
> Ace Fekay, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE &
> MCSA 2003/2000, MCSA Messaging 2003
> Microsoft Certified Trainer
> Microsoft MVP - Directory Services
>
> If you feel this is an urgent issue and require immediate assistance, please
> contact Microsoft PSS directly. Please check http://support.microsoft.com
> for regional support phone numbers.
>
>
>Hi, Ace,
We have four offices sites. Head office has three DCs, One DC is with DNS,
WINS and DHCP, other two DCs are with DNS, WINS. Three branch offices have
one DC, each of them with DNS, WINS and DHCP. All DCs, DNS, DHCP WINS are
working fine. Recently I found most host records at head office are
disappeared in all DNS. There is not any error message in DNS log. One static
IP is for each of DCs.
Also I found pen icon on client PC under "address leases" in DHCP of head
office.
The picture can not be paste.

I open DHCP log from DHCP fold, copy some of them.

30,02/17/10,00:00:24,DNS Update
Request,97.20.168.192,Supervisor-ADT.acld.int,,
30,02/17/10,00:00:24,DNS Update
Request,98.20.168.192,Codrington-Orette.acld.int,,
30,02/17/10,00:00:24,DNS Update Request,99.20.168.192,Dawson-Jeff.acld.int,,
30,02/17/10,00:00:24,DNS Update
Request,101.20.168.192,Treopaldo-Jack.acld.int,,
30,02/17/10,00:00:24,DNS Update
Request,102.20.168.192,Alexander-Alan.acld.int,,
30,02/17/10,00:00:24,DNS Update Request,103.20.168.192,FredJonson.acld.int,,
30,02/17/10,00:00:24,DNS Update Request,104.20.168.192,Mckenna-Ver.acld.int,,
30,02/17/10,00:00:24,DNS Update Request,3.123.168.192,Lev-Sup.,,
30,02/17/10,00:00:24,DNS Update Request,4.123.168.192,Lynne-PC.acld.int,,
30,02/17/10,00:00:24,DNS Update Request,5.123.168.192,tastro.acld.int,,
30,02/17/10,00:00:24,DNS Update Request,6.123.168.192,Levittown_5.,,
30,02/17/10,00:00:24,DNS Update
Request,7.123.168.192,Shelton-Jeanie.acld.int,,
30,02/17/10,00:00:24,DNS Update Request,8.123.168.192,Levitton_1.,,
30,02/17/10,00:00:24,DNS Update Request,9.123.168.192,lightell-lupe.acld.int,,
30,02/17/10,00:00:24,DNS Update Request,10.123.168.192,Leavy-Joann.acld.int,,
30,02/17/10,00:00:24,DNS Update Request,11.123.168.192,barbara-PC.acld.int,,
30,02/17/10,00:00:24,DNS Update Request,15.123.168.192,kim-moorehead.,,
25,02/17/10,00:00:24,0 leases expired and 0 leases deleted,,,,
25,02/17/10,00:00:24,0 leases expired and 0 leases deleted,,,,
31,02/17/10,00:00:24,DNS Update Failed,192.168.2.37,Sime-Anne.acld.int,-1,
31,02/17/10,00:00:24,DNS Update Failed,192.168.2.39,Landers.acld.int,-1,
31,02/17/10,00:00:24,DNS Update Failed,192.168.2.44,s-karp.acld.int,-1,
31,02/17/10,00:00:24,DNS Update Failed,192.168.2.46,Valentino.acld.int,-1,
31,02/17/10,00:00:24,DNS Update Failed,192.168.2.47,hrnogidni.acld.int,-1,
31,02/17/10,00:00:24,DNS Update Failed,192.168.2.48,storich.acld.int,-1,
31,02/17/10,00:00:24,DNS Update Failed,192.168.2.49,Thibeault.acld.int,-1,
31,02/17/10,00:00:24,DNS Update Failed,192.168.2.50,Emer_Prep_1.acld.int,-1,
31,02/17/10,00:00:24,DNS Update Failed,192.168.2.51,tigerev.acld.int,-1,
31,02/17/10,00:00:24,DNS Update Failed,192.168.2.54,HSC-Lap1.acld.int,-1,
31,02/17/10,00:00:24,DNS Update Failed,192.168.2.55,prested.acld.int,-1,
31,02/17/10,00:00:24,DNS Update Failed,192.168.2.56,Riordan.acld.int,-1,
31,02/17/10,00:00:24,DNS Update Failed,192.168.2.59,Gentile-Linda.acld.int,-1,
31,02/17/10,00:00:24,DNS Update Failed,192.168.2.62,Halstead-Pat.acld.int,-1,
31,02/17/10,00:00:24,DNS Update Failed,192.168.2.64,DMVMT.acld.int,-1,
31,02/17/10,00:00:24,DNS Update Failed,192.168.2.65,Varghese-Liz.acld.int,-

I checked DHCP and DNS configuration follow the technet article id:816592.
It looks fine.

This is one DC with DHCP at head office.

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator.ACLD>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : phoenix
Primary Dns Suffix . . . . . . . : acld.int
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : acld.int

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection
Physical Address. . . . . . . . . : 00-14-22-45-86-03
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.2.4
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.16
DNS Servers . . . . . . . . . . . : 192.168.2.4
192.168.2.23
Primary WINS Server . . . . . . . : 192.168.2.4
Secondary WINS Server . . . . . . : 192.168.2.23
192.168.2.6



This is the DC at branch office.

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator.ACLD>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : hauppauge1
Primary Dns Suffix . . . . . . . : acld.int
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : acld.int

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection
Physical Address. . . . . . . . . : 00-13-72-3E-98-38
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.3.6
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.3.30
DNS Servers . . . . . . . . . . . : 192.168.3.6
192.168.2.23
Primary WINS Server . . . . . . . : 192.168.3.6
Secondary WINS Server . . . . . . : 192.168.2.23


Thanks

George Wang

>

"George" <> wrote in message
news:99D9B824-1A97-40DE-AC74-...
>
>
> "Ace Fekay [MVP-DS, MCT]" wrote:
>
>> "George" <> wrote in message
>> news:6A12405C-F89C-4586-8219-...
>> > My network is forest and domain function 2003. All DNS servers build in
>> > with
>> > DC, active-directory-integrated and all DNS servers in the active
>> > directory
>> > domain. Three DNS on the one site do not display host records. But
>> > servers,
>> > switches, printers and PCs with static IP are displayed. Clients can
>> > resolve
>> > their DNS names fine by PING or NSLOOKUP. DHCP is running on the same
>> > server
>> > and dynamic updates are enabled. All PCs run XP with sp3. Internet FQDN
>> > resolution is working. I can not find any error message of DNS from DC
>> > servers and PCs.
>> > Any suggestions on how to fix the issue?
>> > Thanks a lot!
>> >
>> > George Wang
>> >
>>
>>
>> If only one DNS server at one site, assuming it is a DC, is not showing
>> records of the same zone that other DC/DNS are, then it is telling theer
>> is
>> possibly an AD replication problem. This is all assuming that the zone is
>> AD
>> integrated.
>>
>> To better help, please post the following:
>>
>> 1. Unedited ipconfig /all of the bad DC and a working DC.
>> 2. EventID#s of errors in the event logs of any of the DCs.
>> 3. Are any DCs multihomed (meaning with more than one NIC installed, more
>> than one IP, or that has RRAS installed)?
>>
>>
>> --
>> Ace
>>
>> This posting is provided "AS-IS" with no warranties or guarantees and
>> confers no rights.
>>
>> Please reply back to the newsgroup or forum for collaboration benefit
>> among
>> responding engineers, and to help others benefit from your resolution.
>>
>> Ace Fekay, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE &
>> MCSA 2003/2000, MCSA Messaging 2003
>> Microsoft Certified Trainer
>> Microsoft MVP - Directory Services
>>
>> If you feel this is an urgent issue and require immediate assistance,
>> please
>> contact Microsoft PSS directly. Please check http://support.microsoft.com
>> for regional support phone numbers.
>>
>>
>>Hi, Ace,
> We have four offices sites. Head office has three DCs, One DC is with DNS,
> WINS and DHCP, other two DCs are with DNS, WINS. Three branch offices have
> one DC, each of them with DNS, WINS and DHCP. All DCs, DNS, DHCP WINS are
> working fine. Recently I found most host records at head office are
> disappeared in all DNS. There is not any error message in DNS log. One
> static
> IP is for each of DCs.
> Also I found pen icon on client PC under "address leases" in DHCP of head
> office.
> The picture can not be paste.
>
> I open DHCP log from DHCP fold, copy some of them.
>
> 30,02/17/10,00:00:24,DNS Update
> Request,97.20.168.192,Supervisor-ADT.acld.int,,
> 30,02/17/10,00:00:24,DNS Update
> Request,98.20.168.192,Codrington-Orette.acld.int,,
> 30,02/17/10,00:00:24,DNS Update
> Request,99.20.168.192,Dawson-Jeff.acld.int,,
> 30,02/17/10,00:00:24,DNS Update
> Request,101.20.168.192,Treopaldo-Jack.acld.int,,
> 30,02/17/10,00:00:24,DNS Update
> Request,102.20.168.192,Alexander-Alan.acld.int,,
> 30,02/17/10,00:00:24,DNS Update
> Request,103.20.168.192,FredJonson.acld.int,,
> 30,02/17/10,00:00:24,DNS Update
> Request,104.20.168.192,Mckenna-Ver.acld.int,,
> 30,02/17/10,00:00:24,DNS Update Request,3.123.168.192,Lev-Sup.,,
> 30,02/17/10,00:00:24,DNS Update Request,4.123.168.192,Lynne-PC.acld.int,,
> 30,02/17/10,00:00:24,DNS Update Request,5.123.168.192,tastro.acld.int,,
> 30,02/17/10,00:00:24,DNS Update Request,6.123.168.192,Levittown_5.,,
> 30,02/17/10,00:00:24,DNS Update
> Request,7.123.168.192,Shelton-Jeanie.acld.int,,
> 30,02/17/10,00:00:24,DNS Update Request,8.123.168.192,Levitton_1.,,
> 30,02/17/10,00:00:24,DNS Update
> Request,9.123.168.192,lightell-lupe.acld.int,,
> 30,02/17/10,00:00:24,DNS Update
> Request,10.123.168.192,Leavy-Joann.acld.int,,
> 30,02/17/10,00:00:24,DNS Update
> Request,11.123.168.192,barbara-PC.acld.int,,
> 30,02/17/10,00:00:24,DNS Update Request,15.123.168.192,kim-moorehead.,,
> 25,02/17/10,00:00:24,0 leases expired and 0 leases deleted,,,,
> 25,02/17/10,00:00:24,0 leases expired and 0 leases deleted,,,,
> 31,02/17/10,00:00:24,DNS Update Failed,192.168.2.37,Sime-Anne.acld.int,-1,
> 31,02/17/10,00:00:24,DNS Update Failed,192.168.2.39,Landers.acld.int,-1,
> 31,02/17/10,00:00:24,DNS Update Failed,192.168.2.44,s-karp.acld.int,-1,
> 31,02/17/10,00:00:24,DNS Update Failed,192.168.2.46,Valentino.acld.int,-1,
> 31,02/17/10,00:00:24,DNS Update Failed,192.168.2.47,hrnogidni.acld.int,-1,
> 31,02/17/10,00:00:24,DNS Update Failed,192.168.2.48,storich.acld.int,-1,
> 31,02/17/10,00:00:24,DNS Update Failed,192.168.2.49,Thibeault.acld.int,-1,
> 31,02/17/10,00:00:24,DNS Update
> Failed,192.168.2.50,Emer_Prep_1.acld.int,-1,
> 31,02/17/10,00:00:24,DNS Update Failed,192.168.2.51,tigerev.acld.int,-1,
> 31,02/17/10,00:00:24,DNS Update Failed,192.168.2.54,HSC-Lap1.acld.int,-1,
> 31,02/17/10,00:00:24,DNS Update Failed,192.168.2.55,prested.acld.int,-1,
> 31,02/17/10,00:00:24,DNS Update Failed,192.168.2.56,Riordan.acld.int,-1,
> 31,02/17/10,00:00:24,DNS Update
> Failed,192.168.2.59,Gentile-Linda.acld.int,-1,
> 31,02/17/10,00:00:24,DNS Update
> Failed,192.168.2.62,Halstead-Pat.acld.int,-1,
> 31,02/17/10,00:00:24,DNS Update Failed,192.168.2.64,DMVMT.acld.int,-1,
> 31,02/17/10,00:00:24,DNS Update
> Failed,192.168.2.65,Varghese-Liz.acld.int,-
>
> I checked DHCP and DNS configuration follow the technet article id:816592.
> It looks fine.
>
> This is one DC with DHCP at head office.
>
> Microsoft Windows [Version 5.2.3790]
> (C) Copyright 1985-2003 Microsoft Corp.
>
> C:\Documents and Settings\Administrator.ACLD>ipconfig /all
>
> Windows IP Configuration
>
> Host Name . . . . . . . . . . . . : phoenix
> Primary Dns Suffix . . . . . . . : acld.int
> Node Type . . . . . . . . . . . . : Hybrid
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
> DNS Suffix Search List. . . . . . : acld.int
>
> Ethernet adapter Local Area Connection:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network
> Connection
> Physical Address. . . . . . . . . : 00-14-22-45-86-03
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.2.4
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.2.16
> DNS Servers . . . . . . . . . . . : 192.168.2.4
> 192.168.2.23
> Primary WINS Server . . . . . . . : 192.168.2.4
> Secondary WINS Server . . . . . . : 192.168.2.23
> 192.168.2.6
>
>
>
> This is the DC at branch office.
>
> Microsoft Windows [Version 5.2.3790]
> (C) Copyright 1985-2003 Microsoft Corp.
>
> C:\Documents and Settings\Administrator.ACLD>ipconfig /all
>
> Windows IP Configuration
>
> Host Name . . . . . . . . . . . . : hauppauge1
> Primary Dns Suffix . . . . . . . : acld.int
> Node Type . . . . . . . . . . . . : Hybrid
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
> DNS Suffix Search List. . . . . . : acld.int
>
> Ethernet adapter Local Area Connection:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network
> Connection
> Physical Address. . . . . . . . . : 00-13-72-3E-98-38
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.3.6
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.3.30
> DNS Servers . . . . . . . . . . . : 192.168.3.6
> 192.168.2.23
> Primary WINS Server . . . . . . . : 192.168.3.6
> Secondary WINS Server . . . . . . : 192.168.2.23
>
>
> Thanks
>
> George Wang
>
>>



Hello George,

Thank you for posting this info.

First of, and this has nothing to do with DNS issues, but will affect WINS
if you don't fix it, is that a WINS server can ONLY point to itself. This is
due to WINS registration ownership data. A WINS server must be aware of it's
own registered data. It doesn't work like DNS entries. On any of the WINS
server, only point to itself. Any non-WINS server, you can specify two
entries. For multiple WINS server in an environment, configure them as
replication partners.

As for the rest of the ipconfigs, they look ok.

On the head office DC with DNS, is the zone allowed updates (check zone
properties)?

Did anyone at any time ever manually create the zone acld.int on the head
office DNS taht his having the trouble?

Do you remember what occured prior to this happening, such as any issues on
the DC, an app installed, an update, service pack, or any config changes?

Check each DC/DNS server and look at the zone replication scope in each
server's zone. Please post if any of them are not the same.

Just to make sure, please use ADSI Edit to insure there are no conflicting
zones in Active Directory. Please read my blog to help guide you (link
posted below).

Using ADSI Edit to Resolve Conflicting or Duplicate AD Integrated DNS zones
http://msmvps.com/blogs/acefekay/arc...dns-zones.aspx

Ace

Hi, Ace,
thanks for your help.
Finally I call Microsoft support. The technician find one of DC is not sync
with PDC. Because of timer server sync wrong. After changed time parameter in
the register file, the DC is sync with PDC, DNS is working fine. Because the
DNS is build in AD.
anyway, thanks for help

George

"Ace Fekay [MVP-DS, MCT]" wrote:

> "George" <> wrote in message
> news:99D9B824-1A97-40DE-AC74-...
> >
> >
> > "Ace Fekay [MVP-DS, MCT]" wrote:
> >
> >> "George" <> wrote in message
> >> news:6A12405C-F89C-4586-8219-...
> >> > My network is forest and domain function 2003. All DNS servers build in
> >> > with
> >> > DC, active-directory-integrated and all DNS servers in the active
> >> > directory
> >> > domain. Three DNS on the one site do not display host records. But
> >> > servers,
> >> > switches, printers and PCs with static IP are displayed. Clients can
> >> > resolve
> >> > their DNS names fine by PING or NSLOOKUP. DHCP is running on the same
> >> > server
> >> > and dynamic updates are enabled. All PCs run XP with sp3. Internet FQDN
> >> > resolution is working. I can not find any error message of DNS from DC
> >> > servers and PCs.
> >> > Any suggestions on how to fix the issue?
> >> > Thanks a lot!
> >> >
> >> > George Wang
> >> >
> >>
> >>
> >> If only one DNS server at one site, assuming it is a DC, is not showing
> >> records of the same zone that other DC/DNS are, then it is telling theer
> >> is
> >> possibly an AD replication problem. This is all assuming that the zone is
> >> AD
> >> integrated.
> >>
> >> To better help, please post the following:
> >>
> >> 1. Unedited ipconfig /all of the bad DC and a working DC.
> >> 2. EventID#s of errors in the event logs of any of the DCs.
> >> 3. Are any DCs multihomed (meaning with more than one NIC installed, more
> >> than one IP, or that has RRAS installed)?
> >>
> >>
> >> --
> >> Ace
> >>
> >> This posting is provided "AS-IS" with no warranties or guarantees and
> >> confers no rights.
> >>
> >> Please reply back to the newsgroup or forum for collaboration benefit
> >> among
> >> responding engineers, and to help others benefit from your resolution.
> >>
> >> Ace Fekay, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE &
> >> MCSA 2003/2000, MCSA Messaging 2003
> >> Microsoft Certified Trainer
> >> Microsoft MVP - Directory Services
> >>
> >> If you feel this is an urgent issue and require immediate assistance,
> >> please
> >> contact Microsoft PSS directly. Please check http://support.microsoft.com
> >> for regional support phone numbers.
> >>
> >>
> >>Hi, Ace,
> > We have four offices sites. Head office has three DCs, One DC is with DNS,
> > WINS and DHCP, other two DCs are with DNS, WINS. Three branch offices have
> > one DC, each of them with DNS, WINS and DHCP. All DCs, DNS, DHCP WINS are
> > working fine. Recently I found most host records at head office are
> > disappeared in all DNS. There is not any error message in DNS log. One
> > static
> > IP is for each of DCs.
> > Also I found pen icon on client PC under "address leases" in DHCP of head
> > office.
> > The picture can not be paste.
> >
> > I open DHCP log from DHCP fold, copy some of them.
> >
> > 30,02/17/10,00:00:24,DNS Update
> > Request,97.20.168.192,Supervisor-ADT.acld.int,,
> > 30,02/17/10,00:00:24,DNS Update
> > Request,98.20.168.192,Codrington-Orette.acld.int,,
> > 30,02/17/10,00:00:24,DNS Update
> > Request,99.20.168.192,Dawson-Jeff.acld.int,,
> > 30,02/17/10,00:00:24,DNS Update
> > Request,101.20.168.192,Treopaldo-Jack.acld.int,,
> > 30,02/17/10,00:00:24,DNS Update
> > Request,102.20.168.192,Alexander-Alan.acld.int,,
> > 30,02/17/10,00:00:24,DNS Update
> > Request,103.20.168.192,FredJonson.acld.int,,
> > 30,02/17/10,00:00:24,DNS Update
> > Request,104.20.168.192,Mckenna-Ver.acld.int,,
> > 30,02/17/10,00:00:24,DNS Update Request,3.123.168.192,Lev-Sup.,,
> > 30,02/17/10,00:00:24,DNS Update Request,4.123.168.192,Lynne-PC.acld.int,,
> > 30,02/17/10,00:00:24,DNS Update Request,5.123.168.192,tastro.acld.int,,
> > 30,02/17/10,00:00:24,DNS Update Request,6.123.168.192,Levittown_5.,,
> > 30,02/17/10,00:00:24,DNS Update
> > Request,7.123.168.192,Shelton-Jeanie.acld.int,,
> > 30,02/17/10,00:00:24,DNS Update Request,8.123.168.192,Levitton_1.,,
> > 30,02/17/10,00:00:24,DNS Update
> > Request,9.123.168.192,lightell-lupe.acld.int,,
> > 30,02/17/10,00:00:24,DNS Update
> > Request,10.123.168.192,Leavy-Joann.acld.int,,
> > 30,02/17/10,00:00:24,DNS Update
> > Request,11.123.168.192,barbara-PC.acld.int,,
> > 30,02/17/10,00:00:24,DNS Update Request,15.123.168.192,kim-moorehead.,,
> > 25,02/17/10,00:00:24,0 leases expired and 0 leases deleted,,,,
> > 25,02/17/10,00:00:24,0 leases expired and 0 leases deleted,,,,
> > 31,02/17/10,00:00:24,DNS Update Failed,192.168.2.37,Sime-Anne.acld.int,-1,
> > 31,02/17/10,00:00:24,DNS Update Failed,192.168.2.39,Landers.acld.int,-1,
> > 31,02/17/10,00:00:24,DNS Update Failed,192.168.2.44,s-karp.acld.int,-1,
> > 31,02/17/10,00:00:24,DNS Update Failed,192.168.2.46,Valentino.acld.int,-1,
> > 31,02/17/10,00:00:24,DNS Update Failed,192.168.2.47,hrnogidni.acld.int,-1,
> > 31,02/17/10,00:00:24,DNS Update Failed,192.168.2.48,storich.acld.int,-1,
> > 31,02/17/10,00:00:24,DNS Update Failed,192.168.2.49,Thibeault.acld.int,-1,
> > 31,02/17/10,00:00:24,DNS Update
> > Failed,192.168.2.50,Emer_Prep_1.acld.int,-1,
> > 31,02/17/10,00:00:24,DNS Update Failed,192.168.2.51,tigerev.acld.int,-1,
> > 31,02/17/10,00:00:24,DNS Update Failed,192.168.2.54,HSC-Lap1.acld.int,-1,
> > 31,02/17/10,00:00:24,DNS Update Failed,192.168.2.55,prested.acld.int,-1,
> > 31,02/17/10,00:00:24,DNS Update Failed,192.168.2.56,Riordan.acld.int,-1,
> > 31,02/17/10,00:00:24,DNS Update
> > Failed,192.168.2.59,Gentile-Linda.acld.int,-1,
> > 31,02/17/10,00:00:24,DNS Update
> > Failed,192.168.2.62,Halstead-Pat.acld.int,-1,
> > 31,02/17/10,00:00:24,DNS Update Failed,192.168.2.64,DMVMT.acld.int,-1,
> > 31,02/17/10,00:00:24,DNS Update
> > Failed,192.168.2.65,Varghese-Liz.acld.int,-
> >
> > I checked DHCP and DNS configuration follow the technet article id:816592.
> > It looks fine.
> >
> > This is one DC with DHCP at head office.
> >
> > Microsoft Windows [Version 5.2.3790]
> > (C) Copyright 1985-2003 Microsoft Corp.
> >
> > C:\Documents and Settings\Administrator.ACLD>ipconfig /all
> >
> > Windows IP Configuration
> >
> > Host Name . . . . . . . . . . . . : phoenix
> > Primary Dns Suffix . . . . . . . : acld.int
> > Node Type . . . . . . . . . . . . : Hybrid
> > IP Routing Enabled. . . . . . . . : No
> > WINS Proxy Enabled. . . . . . . . : No
> > DNS Suffix Search List. . . . . . : acld.int
> >
> > Ethernet adapter Local Area Connection:
> >
> > Connection-specific DNS Suffix . :
> > Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network
> > Connection
> > Physical Address. . . . . . . . . : 00-14-22-45-86-03
> > DHCP Enabled. . . . . . . . . . . : No
> > IP Address. . . . . . . . . . . . : 192.168.2.4
> > Subnet Mask . . . . . . . . . . . : 255.255.255.0
> > Default Gateway . . . . . . . . . : 192.168.2.16
> > DNS Servers . . . . . . . . . . . : 192.168.2.4
> > 192.168.2.23
> > Primary WINS Server . . . . . . . : 192.168.2.4
> > Secondary WINS Server . . . . . . : 192.168.2.23
> > 192.168.2.6
> >
> >
> >
> > This is the DC at branch office.
> >
> > Microsoft Windows [Version 5.2.3790]
> > (C) Copyright 1985-2003 Microsoft Corp.
> >
> > C:\Documents and Settings\Administrator.ACLD>ipconfig /all
> >
> > Windows IP Configuration
> >
> > Host Name . . . . . . . . . . . . : hauppauge1
> > Primary Dns Suffix . . . . . . . : acld.int
> > Node Type . . . . . . . . . . . . : Hybrid
> > IP Routing Enabled. . . . . . . . : No
> > WINS Proxy Enabled. . . . . . . . : No
> > DNS Suffix Search List. . . . . . : acld.int
> >
> > Ethernet adapter Local Area Connection:
> >
> > Connection-specific DNS Suffix . :
> > Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network
> > Connection
> > Physical Address. . . . . . . . . : 00-13-72-3E-98-38
> > DHCP Enabled. . . . . . . . . . . : No
> > IP Address. . . . . . . . . . . . : 192.168.3.6
> > Subnet Mask . . . . . . . . . . . : 255.255.255.0
> > Default Gateway . . . . . . . . . : 192.168.3.30
> > DNS Servers . . . . . . . . . . . : 192.168.3.6
> > 192.168.2.23
> > Primary WINS Server . . . . . . . : 192.168.3.6
> > Secondary WINS Server . . . . . . : 192.168.2.23
> >
> >
> > Thanks
> >
> > George Wang
> >
> >>
>
>
>
> Hello George,
>
> Thank you for posting this info.
>
> First of, and this has nothing to do with DNS issues, but will affect WINS
> if you don't fix it, is that a WINS server can ONLY point to itself. This is
> due to WINS registration ownership data. A WINS server must be aware of it's
> own registered data. It doesn't work like DNS entries. On any of the WINS
> server, only point to itself. Any non-WINS server, you can specify two
> entries. For multiple WINS server in an environment, configure them as
> replication partners.
>
> As for the rest of the ipconfigs, they look ok.
>
> On the head office DC with DNS, is the zone allowed updates (check zone
> properties)?
>
> Did anyone at any time ever manually create the zone acld.int on the head
> office DNS taht his having the trouble?
>
> Do you remember what occured prior to this happening, such as any issues on
> the DC, an app installed, an update, service pack, or any config changes?
>
> Check each DC/DNS server and look at the zone replication scope in each
> server's zone. Please post if any of them are not the same.
>
> Just to make sure, please use ADSI Edit to insure there are no conflicting
> zones in Active Directory. Please read my blog to help guide you (link
> posted below).
>
> Using ADSI Edit to Resolve Conflicting or Duplicate AD Integrated DNS zones
> http://msmvps.com/blogs/acefekay/arc...dns-zones.aspx
>
> Ace
>
>
>
> .
>

"George" <> wrote in message news:7A94B852-4605-4F09-A6D4-...
> Hi, Ace,
> thanks for your help.
> Finally I call Microsoft support. The technician find one of DC is not sync
> with PDC. Because of timer server sync wrong. After changed time parameter in
> the register file, the DC is sync with PDC, DNS is working fine. Because the
> DNS is build in AD.
> anyway, thanks for help
>
> George

I'm happy to hear you got it resovled by calling Microsoft support. Time is definitely an important part of AD authentication. If the clocks between each machine in a domain are off more than 5 minutes, communications failure will occur because authentication failures.

Curious, what occured to cause the time service to stop working? Was there a failed DC, or was the time service settings changed at any time?



--
Ace

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

Please reply back to the newsgroup or forum for collaboration benefit among responding engineers, and to help others benefit from your resolution.

Ace Fekay, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services

If you feel this is an urgent issue and require immediate assistance, please contact Microsoft PSS directly. Please check http://support.microsoft.com for regional support phone numbers.