search for: forestdczones

...> # dig _ldap._tcp.dc._msdcs.chester-dc.example.com srv @10.4.4.155 >> [...] >> > > For me I had to use ADSI edit to remove the entries. > I've managed to locate the entries using ADSI edit ( for any future archive readers, open ADSI edit, and then connect using "DC=ForestDCZones,dc=chester-dc,dc=example,dc=com" as the naming context, the records are under CN=MicrosoftDNS). The thing is, if I open, say DC=_ldap._tcp.dc and then look at dnsRecord the entries are using some kind of encoding (a series of backslash prefixed 2 digit hex values). I'm unsure which recor...

...ster-dc.example.com srv @10.4.4.155 >>> [...] >>> >> >> For me I had to use ADSI edit to remove the entries. >> > I've managed to locate the entries using ADSI edit ( for any future > archive readers, open ADSI edit, and then connect using > "DC=ForestDCZones,dc=chester-dc,dc=example,dc=com" as the naming > context, the records are under CN=MicrosoftDNS). > > The thing is, if I open, say DC=_ldap._tcp.dc and then look at dnsRecord > the entries are using some kind of encoding (a series of backslash > prefixed 2 digit hex values). &gt...

...>>> [...] > >>> > >> > >> For me I had to use ADSI edit to remove the entries. > >> > > I've managed to locate the entries using ADSI edit ( for any future > > archive readers, open ADSI edit, and then connect using > > "DC=ForestDCZones,dc=chester-dc,dc=example,dc=com" as the naming > > context, the records are under CN=MicrosoftDNS). > > > > The thing is, if I open, say DC=_ldap._tcp.dc and then look at > > dnsRecord the entries are using some kind of encoding (a series of > > backslash prefixed...