Have several domain controllers both 2000 and 2003 we are using Lucent QIP
for dns
For what ever reason we are seeing that some of the records are disappearing
from dns
I would have to restart the netlogon service for this to get fixed.
If you ran a dcdiag /test:dns I will get an error that states:
Error: Missing CNAME record at DNS server xx.xx.xx.xx
Warning: Missing DC SRV record at DNS server xx.xx.xx.xx:
_ldap._tcp.dc._msdcs.xxxxx.com
There is no scavenging occurring on the dns server.
Does anybody have any ideas? I know that this is not Windows DNS but maybe
someone has run into something similar.

In news:ee%23rRcp3HHA.5852@TK2MSFTNGP02.phx.gbl,
Barrycuda <barrycuda@newgroup.nospam> typed:
> Have several domain controllers both 2000 and 2003 we are using
> Lucent QIP for dns
> For what ever reason we are seeing that some of the records are
> disappearing from dns
> I would have to restart the netlogon service for this to get fixed.
> If you ran a dcdiag /test:dns I will get an error that states:
> Error: Missing CNAME record at DNS server xx.xx.xx.xx
> Warning: Missing DC SRV record at DNS server xx.xx.xx.xx:
> _ldap._tcp.dc._msdcs.xxxxx.com
> There is no scavenging occurring on the dns server.
> Does anybody have any ideas? I know that this is not Windows DNS but
> maybe someone has run into something similar.

It sounds like you are trying to create a CNAME of an existing record, or
more than one CNAME for the blank domain name or also known as the LDAP or
LdapIpAddress. That is the blank record that each DC registers into DNS. In
Windows DNS, it shows up as:
(same as folder) A 192.168.10.10

Of course restarting the netlogon service will re-register these records as
well as all the SRV folders. We actually restart the netlogon service when
there is a possibility of an issue with SRV records.

I'm not sure what you are trying to create or do, but whatever it is, it
appears to be conflicting with the default records that the DCs create. Can
you elaborate on what type of records you might be creating or doing in DNS
to possibly cause the conflict?




--
Regards,
Ace

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 MVP - Directory Services
Microsoft Certified Trainer

Infinite Diversities in Infinite Combinations

Having difficulty reading or finding responses to your post?
Try using Outlook Express or any other newsreader, configure a news
account, and point it to news.microsoft.com. Anonymous access. It's
easy and it's free:

How to Configure OEx for Internet News
http://support.microsoft.com/?id=171164

"Life isn't like a box of chocolates or a bowl of cherries or
peaches... Life is more like a jar of jalapenos. What you do today
may burn your butt tomorrow." - Garfield

"Ace Fekay [MVP]" <PleaseAskMe@SomeDomain.com> wrote in message
news:%23yGhPIv3HHA.1184@TK2MSFTNGP04.phx.gbl...
> In news:ee%23rRcp3HHA.5852@TK2MSFTNGP02.phx.gbl,
> Barrycuda <barrycuda@newgroup.nospam> typed:
>> Have several domain controllers both 2000 and 2003 we are using
>> Lucent QIP for dns
>> For what ever reason we are seeing that some of the records are
>> disappearing from dns
>> I would have to restart the netlogon service for this to get fixed.
>> If you ran a dcdiag /test:dns I will get an error that states:
>> Error: Missing CNAME record at DNS server xx.xx.xx.xx
>> Warning: Missing DC SRV record at DNS server xx.xx.xx.xx:
>> _ldap._tcp.dc._msdcs.xxxxx.com
>> There is no scavenging occurring on the dns server.
>> Does anybody have any ideas? I know that this is not Windows DNS but
>> maybe someone has run into something similar.
>
> It sounds like you are trying to create a CNAME of an existing record, or
> more than one CNAME for the blank domain name or also known as the LDAP or
> LdapIpAddress. That is the blank record that each DC registers into DNS.
> In Windows DNS, it shows up as:
> (same as folder) A 192.168.10.10
>
> Of course restarting the netlogon service will re-register these records
> as well as all the SRV folders. We actually restart the netlogon service
> when there is a possibility of an issue with SRV records.
>
> I'm not sure what you are trying to create or do, but whatever it is, it
> appears to be conflicting with the default records that the DCs create.
> Can you elaborate on what type of records you might be creating or doing
> in DNS to possibly cause the conflict?
> Regards,
> Ace
>
> 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 MVP - Directory Services
> Microsoft Certified Trainer
>
> The solution ended up that our particular version of QIP was not correctly
> registering the dynamic records.
When ever a dns update was performed on the dns servers it would erase the
dynamic records.

In news:O6nT2DN4HHA.5740@TK2MSFTNGP04.phx.gbl,
Barrycuda <barrycuda@newgroup.nospam> typed:

> The solution ended up that our particular version of QIP was not
> correctly registering the dynamic records.
> When ever a dns update was performed on the dns servers it would
> erase the dynamic records.

Interesting. I guess a new or upgraded version is required.

Cheers!

Ace