add latest dns changes

[DaMandal0rian]

User description

• autonomys.xyz
• subspace.foundation

---

PR Type

enhancement

---

Description

• Updated DNS records for autonomys.xyz, including changes to IP addresses and CNAME values.
• Added new DNS records for blog and community under autonomys.xyz.
• Modified the www record for subspace.foundation from an A record to a CNAME pointing to Notion.
• Added a TXT record for Notion verification under subspace.foundation.

---

Changes walkthrough 📝

Relevant files

Enhancement

autonomys-xyz.tf Update and add DNS records for autonomys.xyz                          dns/autonomys-xyz.tf Updated IP addresses for existing DNS records. Changed CNAME value for www record. Added new DNS records for blog and community. +28/-3    subspace-foundation.tf Modify DNS records and add Notion TXT for subspace.foundation dns/subspace-foundation.tf Changed www record from A to CNAME with a new value. Added a TXT record for Notion verification. +11/-3

---

💡 PR-Agent usage: Comment /help "your question" on any pull request to receive relevant information

[github-actions]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Hardcoded IP The IP address '35.71.142.77' is hardcoded as a dummy IP for the blog record. This could lead to confusion or errors if the IP needs to be changed or if it conflicts with other services. CNAME Change The change from an A record to a CNAME for 'www' under 'subspace.foundation' may affect existing services or integrations that rely on the previous A record configuration.

[github-actions]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Score
Security	Ensure the accuracy and security of IP addresses in DNS records Verify that the IP addresses specified in the DNS records are correct and do not expose any internal infrastructure unnecessarily, especially when marked as dummy or placeholder IPs. dns/autonomys-xyz.tf [42] -value = "35.71.142.77" #this is a dummy IP since we use redirect workers to route this to medium +value = "correct.production.ip" Suggestion importance[1-10]: 7 Why: This suggestion highlights a potential security concern by ensuring that dummy IPs are not exposed in production. It is important to verify IP addresses to prevent accidental exposure of internal infrastructure.	7
Possible issue	Validate external CNAME targets for subdomains Confirm that the CNAME record for 'www' subdomain correctly points to an intended external service, and ensure that the service supports custom CNAME records. dns/subspace-foundation.tf [15] -value = "external.notion.site" +value = "verified.external.service.com" Suggestion importance[1-10]: 6 Why: The suggestion to validate CNAME targets is valid as it ensures that the external service supports custom CNAME records. This can prevent potential misconfigurations or service disruptions.	6
Best practice	Adjust TTL values to optimize DNS update propagation times Ensure that the TTL values for critical DNS records are set appropriately to balance between DNS propagation times and the need to quickly propagate changes. The current TTL of 3600 seconds might be too long for records that might change frequently. dns/autonomys-xyz.tf [4] -ttl = 3600 +ttl = 1800 Suggestion importance[1-10]: 5 Why: The suggestion to adjust TTL values is reasonable for optimizing DNS propagation times, especially if frequent changes are expected. However, the decision to change TTL should be based on specific requirements and operational considerations, which are not detailed here.	5
	Optimize MX record priorities for effective email routing Review the priority setting for MX records to ensure that it aligns with the mail delivery priorities and fallback mechanisms, especially if multiple MX records are used. dns/subspace-foundation.tf [23] -priority = 1 +priority = 10 Suggestion importance[1-10]: 4 Why: While adjusting MX record priorities can be beneficial, the suggestion lacks context on why the priority should be changed to 10. The current priority setting might already align with the intended mail delivery strategy.	4

[teor2345]

Sorry, I'm a protocol developer, so I'm not sure why I was tagged for review here?