Verify sdnog.sd domain with google Postmaster Tools - Revision history

Admin at 09:57, 11 August 2024

2024-08-11T09:57:51Z

2024-08-11T09:55:27Z

2021-10-25T15:23:40Z

2021-10-25T15:20:40Z

‎Troubleshooting

2021-10-25T15:19:20Z

‎Troubleshooting

2021-10-25T15:18:48Z

‎Troubleshooting

2021-10-25T10:54:54Z

‎Troubleshooting

2021-10-25T10:36:15Z

2021-10-25T10:35:04Z

2021-10-25T10:34:45Z

@@ Line 1: / Line 1: @@
 [[Category:SdNOG]]
 [[Category:SdNOG_KnowBase]]
 ==How to steps==
 We have noticed some participants subscribe to [https://sdnog.sd/index.php/mailing-list sdnog mailing list] using gmail accounts. and they do not receive some of the list's email and some being forwarded to the Junk folder. this because the DKIM and DMARC fail with domain gmail.com

@@ Line 1: / Line 1: @@
 [[Category:SdNOG]]
 ==How to steps==
 We have noticed some participants subscribe to [https://sdnog.sd/index.php/mailing-list sdnog mailing list] using gmail accounts. and they do not receive some of the list's email and some being forwarded to the Junk folder. this because the DKIM and DMARC fail with domain gmail.com

← Older revision		Revision as of 15:23, 25 October 2021
Line 1:		Line 1:
		+	[[Category:SdNOG]]
	==How to steps==		==How to steps==
	We have noticed some participants subscribe to [https://sdnog.sd/index.php/mailing-list sdnog mailing list] using gmail accounts. and they do not receive some of the list's email and some being forwarded to the Junk folder. this because the DKIM and DMARC fail with domain gmail.com		We have noticed some participants subscribe to [https://sdnog.sd/index.php/mailing-list sdnog mailing list] using gmail accounts. and they do not receive some of the list's email and some being forwarded to the Junk folder. this because the DKIM and DMARC fail with domain gmail.com

← Older revision		Revision as of 15:20, 25 October 2021
Line 49:		Line 49:
	sdnog.sd. 60 IN TXT "google-site-verification=FijZa4-e16D4V2Vqe6gnMgWa5fALU6tozOzWeOtOtgo"		sdnog.sd. 60 IN TXT "google-site-verification=FijZa4-e16D4V2Vqe6gnMgWa5fALU6tozOzWeOtOtgo"
	</nowiki>		</nowiki>
		+
		+	and all the secondaries are synced :
		+
		+	<nowiki>
		+	$ dig soa sdnog.sd +nssearch \| awk -F ' ' ' {print $4, $10, $11}'
		+	2021102409 server 185.70.56.53
		+	2021102409 server 193.110.181.53
		+	2021102409 server 206.220.228.134
		+	2021102409 server 196.216.2.1
		+	2021102409 server 196.10.54.53
		+	2021102409 server 196.10.55.53
		+	2021102409 server 196.10.52.53
		+	</nowiki>
		+	<br>

@@ Line 43: / Line 43: @@
 after fixing some configuration here, we updated the "Serial" time for the zone and restarted the service.
 and now everything is fine <br>
-<nowiki>
+ <nowiki>
   $ dig txt sdnog.sd
   ;; ANSWER SECTION:
   sdnog.sd.		60	IN	TXT	"v=spf1 mx a ip4:196.10.53.12 ip6:2001:43f8:1f3:a00::12  a:mail.sdnog.sd ~all"
-  sdnog.sd.		60	IN	TXT	"google-site-verification=FijZa4-e16D4V2Vqe6gnMgWa5fALU6tozOzWeOtOtgo" </nowiki>
+  sdnog.sd.		60	IN	TXT	"google-site-verification=FijZa4-e16D4V2Vqe6gnMgWa5fALU6tozOzWeOtOtgo"

← Older revision		Revision as of 15:18, 25 October 2021
Line 39:		Line 39:
	2021051905 server 196.10.52.53		2021051905 server 196.10.52.53
	</nowiki>		</nowiki>
		+
		+	so we checked the acl section and " allow-transfer" option to know if we have any limitation on how the zone could be transferred.<br>
		+	after fixing some configuration here, we updated the "Serial" time for the zone and restarted the service.
		+	and now everything is fine <br>
		+	<nowiki>
		+	$ dig txt sdnog.sd
		+	;; ANSWER SECTION:
		+	sdnog.sd. 60 IN TXT "v=spf1 mx a ip4:196.10.53.12 ip6:2001:43f8:1f3:a00::12 a:mail.sdnog.sd ~all"
		+	sdnog.sd. 60 IN TXT "google-site-verification=FijZa4-e16D4V2Vqe6gnMgWa5fALU6tozOzWeOtOtgo" </nowiki>

← Older revision		Revision as of 10:54, 25 October 2021
Line 19:		Line 19:
	<br>		<br>
	==Troubleshooting==		==Troubleshooting==
		+	the above steps seems very easy to do. but while we are doing this for sdnog.sd we found some issues.
		+	We added the TXT record to the zone, but it was not propagated to DNS secondaries:
		+
		+	<nowiki>
		+	$ dig txt sdnog.sd
		+	;; ANSWER SECTION:
		+	sdnog.sd. 60 IN TXT "v=spf1 mx a ip4:196.10.53.12 ip6:2001:43f8:1f3:a00::12 a:mail.sdnog.sd ~all"
		+	</nowiki>
		+
		+	so we noticed not all sdnog secondaries servers are synced, using "dig soa sdnog.sd +nssearch" command:
		+	<nowiki>
		+	$ dig soa sdnog.sd +nssearch \| awk -F ' ' ' {print $4, $10, $11}'
		+	2021051905 server 185.70.56.53
		+	2021051905 server 193.110.181.53
		+	2021102409 server 206.220.228.134
		+	2021051905 server 196.10.54.53
		+	2021102409 server 196.216.2.1
		+	2021051905 server 196.10.55.53
		+	2021051905 server 196.10.52.53
		+	</nowiki>

@@ Line 1: / Line 1: @@
 We have noticed some participants subscribe to [https://sdnog.sd/index.php/mailing-list sdnog mailing list] using gmail accounts. and they do not receive some of the list's email and some being forwarded to the Junk folder. this because the DKIM and DMARC fail with domain gmail.com
 <br>
@@ Line 16: / Line 17: @@
 . after few minutes, the domain will be verified.
 [[File:The Domain has been verified.png|400px|center]]
 <br>

← Older revision		Revision as of 10:34, 25 October 2021
Line 12:		Line 12:

	2. then copy the TXT record and add this to your DNS zone file , and then click on verify.		2. then copy the TXT record and add this to your DNS zone file , and then click on verify.
−	~~it will take few minutes and the domain will be verified.~~
	[[File:Add TXT record to DNS.png\|300px\|center]]		[[File:Add TXT record to DNS.png\|300px\|center]]
		+
		+	3. after few minutes, the domain will be verified.
		+	[[File:The Domain has been verified.png\|300px\|center]]
		+
		+	<br>
		+	<br>