search for: 44985

Displaying 8 results from an estimated 8 matches for "44985".

Did you mean: 4495
2016 Nov 04
2
debugging bind9_DLZ
...-5ec24df2dbf9 > objectCategory: CN=Dns-Node,CN=Schema,CN=Configuration,DC=samdom,DC=example,DC > =com > dc: 180 > whenChanged: 20161104144426.0Z > dnsRecord:: IQAMAAXwAAAKAAAAAAAOEAAAAAAWnzcAHwQKZGV2c3RhdGlvbgZzYW1kb20HZXhhbX > BsZQNjb20A > dNSTombstoned: FALSE > uSNChanged: 44985 > distinguishedName: DC=180,DC=0.168.192.in-addr.arpa,CN=MicrosoftDNS,DC=DomainD > nsZones,DC=samdom,DC=example,DC=com > > So, adapt it for your setup and see if the record does exist in AD. > > Rowland Aha!! 0 records . . . but, doesn't the "xxx.168.192.in-addr.arpa&...
2016 Nov 04
2
debugging bind9_DLZ
...-5ec24df2dbf9 > objectCategory: > CN=Dns-Node,CN=Schema,CN=Configuration,DC=samdom,DC=example,DC =com > dc: 180 > whenChanged: 20161104144426.0Z > dnsRecord:: > IQAMAAXwAAAKAAAAAAAOEAAAAAAWnzcAHwQKZGV2c3RhdGlvbgZzYW1kb20HZXhhbX > BsZQNjb20A dNSTombstoned: FALSE > uSNChanged: 44985 > distinguishedName: > DC=180,DC=0.168.192.in-addr.arpa,CN=MicrosoftDNS,DC=DomainD > nsZones,DC=samdom,DC=example,DC=com > > So, adapt it for your setup and see if the record does exist in AD. > > Rowland Aha!! 0 records . . . but, doesn't the "xxx.168.192.in-addr....
2016 Nov 04
1
debugging bind9_DLZ
...-5ec24df2dbf9 > objectCategory: > CN=Dns-Node,CN=Schema,CN=Configuration,DC=samdom,DC=example,DC =com > dc: 180 > whenChanged: 20161104144426.0Z > dnsRecord:: > IQAMAAXwAAAKAAAAAAAOEAAAAAAWnzcAHwQKZGV2c3RhdGlvbgZzYW1kb20HZXhhbX > BsZQNjb20A dNSTombstoned: FALSE > uSNChanged: 44985 > distinguishedName: > DC=180,DC=0.168.192.in-addr.arpa,CN=MicrosoftDNS,DC=DomainD > nsZones,DC=samdom,DC=example,DC=com > > So, adapt it for your setup and see if the record does exist in AD. > > Rowland > Aha!! 0 records . . . but, doesn't the "xxx.168.192.in-...
2016 Nov 04
2
debugging bind9_DLZ
On 2016-11-04 10:55, Rowland Penny via samba wrote: > On Fri, 04 Nov 2016 08:04:44 -0500 > Bob of Donelson Trophy via samba <samba at lists.samba.org> wrote: > >> On wiki page >> https://wiki.samba.org/index.php/BIND9_DLZ_DNS_Back_End#Reconfiguring_the_BIND9_DLZ_Back_End >> in the "Debugging the Bind Module" the section discusses the location >>
2016 Nov 04
0
debugging bind9_DLZ
...> > CN=Dns-Node,CN=Schema,CN=Configuration,DC=samdom,DC=example,DC =com > > dc: 180 > > whenChanged: 20161104144426.0Z > > dnsRecord:: > > IQAMAAXwAAAKAAAAAAAOEAAAAAAWnzcAHwQKZGV2c3RhdGlvbgZzYW1kb20HZXhhbX > > BsZQNjb20A dNSTombstoned: FALSE > > uSNChanged: 44985 > > distinguishedName: > > DC=180,DC=0.168.192.in-addr.arpa,CN=MicrosoftDNS,DC=DomainD > > nsZones,DC=samdom,DC=example,DC=com > > > > So, adapt it for your setup and see if the record does exist in AD. > > > > Rowland > > Aha!! 0 records . . . bu...
2016 Nov 04
0
debugging bind9_DLZ
...> > CN=Dns-Node,CN=Schema,CN=Configuration,DC=samdom,DC=example,DC =com > > dc: 180 > > whenChanged: 20161104144426.0Z > > dnsRecord:: > > IQAMAAXwAAAKAAAAAAAOEAAAAAAWnzcAHwQKZGV2c3RhdGlvbgZzYW1kb20HZXhhbX > > BsZQNjb20A dNSTombstoned: FALSE > > uSNChanged: 44985 > > distinguishedName: > > DC=180,DC=0.168.192.in-addr.arpa,CN=MicrosoftDNS,DC=DomainD > > nsZones,DC=samdom,DC=example,DC=com > > > > So, adapt it for your setup and see if the record does exist in AD. > > > > Rowland > > Aha!! 0 records . . . bu...
2016 Nov 04
0
debugging bind9_DLZ
...80 objectGUID: 85c0aade-15c9-48a8-822e-5ec24df2dbf9 objectCategory: CN=Dns-Node,CN=Schema,CN=Configuration,DC=samdom,DC=example,DC =com dc: 180 whenChanged: 20161104144426.0Z dnsRecord:: IQAMAAXwAAAKAAAAAAAOEAAAAAAWnzcAHwQKZGV2c3RhdGlvbgZzYW1kb20HZXhhbX BsZQNjb20A dNSTombstoned: FALSE uSNChanged: 44985 distinguishedName: DC=180,DC=0.168.192.in-addr.arpa,CN=MicrosoftDNS,DC=DomainD nsZones,DC=samdom,DC=example,DC=com So, adapt it for your setup and see if the record does exist in AD. Rowland
2003 Mar 22
0
ext3 oops with 2.4.20
Bug report follows. Please CC me if you want me to read the reply, as I'm not subscribed to ext3-users. [1.] One line summary of the problem: Ext3 has just causing filesystem corruption which required fsck to fix. [2.] Full description of the problem/report: I just had my machine lock up with an ext3 oops, preceeded by a bunch of error messages in the logs. On rebooting, after replaying the