Skip to content

Commit

Permalink
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Update core/mondoo-dns-security.mql.yaml
Browse files Browse the repository at this point in the history
Co-authored-by: Letha <[email protected]>
Signed-off-by: Tim Smith <[email protected]>
tas50 and misterpantz authored Dec 16, 2024

Partially verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
We cannot verify signatures from co-authors, and some of the co-authors attributed to this commit require their commits to be signed.
1 parent ce089e7 commit 6c96e58
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions core/mondoo-dns-security.mql.yaml
Original file line number Diff line number Diff line change
@@ -79,10 +79,10 @@ queries:
Risks of using IP addresses in NS and MX records include:
* Lack of Flexibility: Pointing to an IP address directly ties your DNS or mail configuration to a specific server, making it difficult to manage changes, such as server migrations or load balancing.
* Potential Downtime: If the server IP address changes and DNS records are not updated promptly, services dependent on these records (e.g., email or domain resolution) may experience downtime.
* Non-compliance with DNS Standards: DNS resolvers expect NS and MX records to point to hostnames. Using IPs can lead to unpredictable behavior or DNS resolution failures.
* Security Risks: Directly exposing IP addresses can make your infrastructure more vulnerable to attacks, such as DDoS or reconnaissance efforts.
* Lack of flexibility: Pointing to an IP address directly ties your DNS or mail configuration to a specific server. This makes it difficult to manage changes, such as server migrations or load balancing.
* Potential downtime: If the server IP address changes and DNS records are not updated promptly, services dependent on these records (e.g., email or domain resolution) can experience downtime.
* Non-compliance with DNS standards: DNS resolvers expect NS and MX records to point to hostnames. Using IPs can lead to unpredictable behavior or DNS resolution failures.
* Security risks: Directly exposing IP addresses can make your infrastructure more vulnerable to attacks, such as DDoS or reconnaissance efforts.
remediation: |
For NS records: Always configure them to point to the authoritative DNS server’s FQDN (e.g., ns1.example.com).

0 comments on commit 6c96e58

Please sign in to comment.