search for: 6b01

Displaying 4 results from an estimated 4 matches for "6b01".

Did you mean: 601
2019 Sep 17
2
OT: DMARC / DKIM Failure Reports
...or more information about this format please seehttp://tools.ietf.org/html/rfc6591 . Feedback-Type: auth-failure User-Agent: Lua/1.0 Version: 1.0 Original-Mail-From:centos-bounces at centos.org Original-Rcpt-To:obodor at vub.sk Arrival-Date: Tue, 17 Sep 2019 15:56:25 +0200 Message-ID:<5502e8ac-6b01-18dd-e028-7d2dd666063b at intar.cz> Authentication-Results: dmarc=fail (p=none, dis=none) header.from=intar.cz Source-IP: 208.100.23.70 Delivery-Result: smg-policy-action Auth-Failure: dmarc Reported-Domain: intar.cz ------------ This is the seconf report: This is an authentication failure rep...
2019 Sep 17
0
OT: DMARC / DKIM Failure Reports
...> seehttp://tools.ietf.org/html/rfc6591? . > > Feedback-Type: auth-failure > User-Agent: Lua/1.0 > Version: 1.0 > Original-Mail-From:centos-bounces at centos.org > Original-Rcpt-To:obodor at vub.sk > Arrival-Date: Tue, 17 Sep 2019 15:56:25 +0200 > Message-ID:<5502e8ac-6b01-18dd-e028-7d2dd666063b at intar.cz> > Authentication-Results: dmarc=fail (p=none, dis=none) header.from=intar.cz > Source-IP: 208.100.23.70 > Delivery-Result: smg-policy-action > Auth-Failure: dmarc > Reported-Domain: intar.cz > > ------------ > This is the seconf report...
2018 Jun 08
3
Samba, AD, 'short' name resolving...
...ain.tld Jun 8 11:54:31 named[440]: samba_dlz: starting transaction on zone primarydnsdomain.domain.tld Jun 8 11:54:31 named[440]: samba_dlz: allowing update of signer=LOC1-PC01L12\$\@KERBEROS.DOMAIN.TLD name=loc1-pc01l12.primarydnsdomain.domain.tld tcpaddr= type=AAAA key=1140-ms-7.1-6b6e.f0d97c7a-6b01-11e8-94bf-f04da2f88948/160/0 Jun 8 11:54:31 named[440]: samba_dlz: allowing update of signer=LOC1-PC01L12\$\@KERBEROS.DOMAIN.TLD name=loc1-pc01l12.primarydnsdomain.domain.tld tcpaddr= type=A key=1140-ms-7.1-6b6e.f0d97c7a-6b01-11e8-94bf-f04da2f88948/160/0 Jun 8 11:54:31 named[440]: samba_dlz: allo...
2018 Jun 08
4
Samba, AD, 'short' name resolving...
Mandi! Rowland Penny via samba In chel di` si favelave... > This is probably where you are going wrong. AD lives and dies on DNS, > your DC MUST be authoritative for the AD domain. ...but *is* authoritative! Simply DHCP server assign the ''old'' DNS, where all resolution fr the AD (sub)domain are forwarded to AD DNS... > Your AD clients should be using the DC as