{% extends "base.html" %} {% comment %} # SPDX-License-Identifier: AGPL-3.0-or-later {% endcomment %} {% load i18n %} {% block content %}

{% trans "DNS Records for domain:" %} {{ domain }}

{% blocktrans trimmed %} The following DNS records must be added manually on this domain for the mail server to work properly for this domain. {% endblocktrans %}

{% for dns_entry in dns_entries %} {% endfor %}
{% trans "Domain" %} {% trans "TTL" %} {% trans "Class" %} {% trans "Type" %} {% trans "Priority" %} {% trans "Weight" %} {% trans "Port" %} {% trans "Host/Target/Value" %}
{{ dns_entry.domain|default_if_none:"" }} {{ dns_entry.ttl }} {{ dns_entry.class_ }} {{ dns_entry.type_ }} {{ dns_entry.priority }} {{ dns_entry.weight|default_if_none:"" }} {{ dns_entry.port|default_if_none:"" }} {{ dns_entry.get_split_value }}
{% if domain == primary_domain %}

{% trans "Reverse DNS Records for IP Addresses" %}

{% blocktrans trimmed %} If your {{ box_name }} runs on a cloud service infrastructure, you should configure Reverse DNS lookup. This isn't mandatory, however, it greatly improves email deliverability. Reverse DNS isn't configured where your regular DNS is. You should look for it in the settings of your VPS/ISP. Some providers preconfigure the IP address part for you and you only have to set the domain part. Only one of your domains can have Revese DNS lookup configured unless you have multiple public IP addresses. {% endblocktrans %}

{% blocktrans trimmed %} An external service is used to lookup public IP address to show in the following section. This can be configured in the privacy app. {% endblocktrans %}

{% for dns_entry in reverse_dns_entries %} {% endfor %}
{% trans "Host" %} {% trans "TTL" %} {% trans "Type" %} {% trans "Host/Target/Value" %}
{{ dns_entry.domain|default_if_none:"" }} {{ dns_entry.ttl }} {{ dns_entry.type_ }} {{ dns_entry.get_split_value }}
{% endif %} {% endblock %}