Re: DNS Problem

The message about license service replication failure is completely safe and
could be ignored. In fact, you can stop this (license logging) service at
all.

The message about failure registering PTR record should be investigated.
Make sure that this server is using correct DNS server. "Correct" here means
DNS server hosting appropriate reverse lookup zone - would be
100.20.172.in-addr.arpa or something like this for your case - and, with
Dynamic UPdate enabled for this zone. Also, if you are using secure dynamic
updates with DNS, make sure that this particular computer has sufficient
permissions for updating this record.

--
Dmitry Korolyov [d__k@xxxxxxxxxxxxxxxxxxxxxx]
MVP: Windows Server - Directory Services


"dlove106" <dlove106@xxxxxxxxxxxxxxxxxxx> wrote in message
news:38D25694-D6FF-4FAA-8B14-50FA1EF9E4B5@xxxxxxxxxxxxxxxx
>I have 1 w2003 EE parent server and 1 w2003 EE child DC. I receive the
> following error in the event log of the parent server:
>
> Replication of license information failed because the License Logging
> Service on server sdserver.SDSR.Shiprepair.com could not be contacted.
>
> I receive this information from the child DC after trying to update DNS:
>
> The system failed to register pointer (PTR) resource records (RRs) for
> network adapter
> with settings:
>
> Adapter Name : {2010EC99-5529-45B7-9587-C047F52C8E2B}
> Host Name : sdserver
> Adapter-specific Domain Suffix : SDSR.Shiprepair.com
> DNS server list :
> 172.20.100.10
> Sent update to server : 192.175.48.1
> IP Address : 172.20.100.11
>
> The reason that the system could not register these RRs was because of a
> security related problem. The cause of this could be (a) your computer
> does
> not have permissions to register and update the specific DNS domain name
> set
> for this adapter, or (b) there might have been a problem negotiating valid
> credentials with the DNS server during the processing of the update
> request.
>
> You can manually retry DNS registration of the network adapter and its
> settings by typing "ipconfig /registerdns" at the command prompt. If
> problems
> still persist, contact your DNS server or network systems administrator.
>
> I then ran a program called DNSlint which produced the following output
> (small portion only):
>
> Alias (CNAME) and glue (A) records for forest GUIDs from server:
> CNAME: 35881afe-75c4-4f8c-82b6-ad7195205b72._msdcs.Shiprepair.com
> Alias: sddcsrv03.Shiprepair.com
> Glue: 172.20.100.10
>
> CNAME: 7f6280ae-01a4-4f72-8458-3f299e5f1681._msdcs.Shiprepair.com
> Alias: sdserver.sdsr.Shiprepair.com
> Glue: 172.20.100.11
>
> Total number of CNAME records found on this server: 2
>
> Total number of CNAME records missing on this server: 0
>
> Total number of glue (A) records this server could not find: 0
>
> Is there anything in any of this information that looks wrong or
> suspicious?
> The only thing I see is on the 2nd cname record for sdserver. Should the
> end
> look more like this _msdcs.sdsr.ShipRepair.com? This server belongs to the
> child DC.
>
> Thanks in advance for any help.
>
> --
> DLove


.

Loading