Questions tagged [fcrdns]

Forward Confirmed reverse DNS is the practice of using PTR records that are authenticated by matching A or AAAA records to demonstrate ownership of an IP address.

Forward Confirmed reverse DNS is a practice employed by several protocols and applications to tie domain ownership to network ownership. This is considered more reliable than using the WHOIS databases provided by IP assigning organizations (ARIN, RIPE, etc.) which cannot be considered accurate beyond the immediate network carrier.

Example of DNS records that might be defined in a valid FCrDNS scenario:

$ORIGIN example.com.
mail                                     IN A        203.0.113.1
mail                                     IN AAAA     2001:db8::1

$ORIGIN 113.0.203.in-addr.arpa.
1                                        IN PTR      mail.example.com.

$ORIGIN 0.0.0.0.0.0.0.0.8.b.d.0.1.0.0.2.ip6.arpa.
1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0          IN PTR      mail.example.com.

mail.example.com identifies itself as being associated with IPv4 address 203.0.113.1 and IPv6 address 2001:db8::1. If a remote mail server were to look up the reverse DNS entry for either of those IP addresses, it would find a PTR record associating the address to mail.example.com.

This provides a remote server with a reasonable amount of faith that both the domain and network are controlled by the same parties, but there is no way of knowing whether a malicious configuration has been inserted into any of the involved mail servers or name servers.

7 questions
41
votes
3 answers

Why multiple PTR records in DNS is not recommended?

I often read that using multiple PTR records in a DNS configuration is not recommended. However, the reasons are often vague, or not so obvious, naming: "it can cause problems", "can trigger bugs in programs expecting a single answer" : it's the…
Totor
  • 2,876
  • 3
  • 22
  • 31
27
votes
1 answer

Do internet standards require reverse DNS for every device?

The requirements surrounding reverse DNS are confusing! People frequently talk about everything breaking if reverse DNS is not present, and that sounds scary. Even in cases where applications don't require reverse DNS, RFCs are frequently cited in…
Andrew B
  • 31,858
  • 12
  • 90
  • 128
1
vote
0 answers

FCrDNS for a mail server that also runs other services (http, ftp etc)

I am learning how to administer productive internet-facing machines and services, and towards that end setting up mail, web, and a couple other services, all on the same box (budget constraints and simplicity). My question relates to: SPF, FCrDNS,…
ArjunShankar
  • 111
  • 4
0
votes
1 answer

Does FCRDNS need the RDNS to be the same hostname than the first forward query?

Does forward confirmed reverse dns (fcrdns) only lookup ip to hostname and then hostname to ip or does it compare to the first hostname as well (especially in spam filtering)? Let's say i have these records: A reverse.somedomain: 127.0.0.1 A…
allo
  • 1,524
  • 1
  • 19
  • 35
0
votes
1 answer

Which DNS name is checked for TLS on a mailserver?

Let's say i have these records: A mail.somedomain: 127.0.0.1 A mail.mailserverdomain: 127.0.0.1 MX somedomain: mail.somedomain A MTA connects mail.somedomain for delivering mail to somedomain and gets a certificate for mail.mailserverdomain…
allo
  • 1,524
  • 1
  • 19
  • 35
0
votes
0 answers

iprev check for multiple ipv6 addresses

Can I add multiple PTR records mapping multiple IPV6 addresses to the same domain, and add multiple AAAA records mapping the same domain to to the same set of IPV6 addresses, to let pass the iprev check?
William
  • 69
  • 2
  • 10
-3
votes
3 answers

FCrDNS With Separate Host and Mail Server

I have an "A" record on my DNS which points to an IP, specifically the IP my website is hosted on. I use a separate IP for my email server. This causes my emails to fail the Forward Confirmed Reverse DNS test because of the following: My email…