DNS Records Supported by Joker.com Nameservice

Overview of supported records and brief explanations. You can enter these records for your domain by accessing the "DNS" menu item in the domain list on Joker.com.

URL Forwarding	Redirects your domain to an external website (URL). For more information, refer to this article on how to use the web/URL forwarding feature of Joker.com
Email Forwarding	Creates email addresses for your domain, forwarding emails to your existing external mail account. Learn how to configure email forwarding in the provided guide
A Record	Binds your domain or hosts within the domain to an IPv4 address. Allows you to create entries like 'www.your-domain.com' that point to an external IP address.
DYNA Record	Part of the Dynamic DNS Service - associates your domain or host with your provider's temporary IP address. The IP can be automatically updated using your router device or a client program. Make sure Dynamic DNS (DynDNS) is enabled for your domain.
MX Record	Specifies the email server responsible for accepting emails for your domain. Additional details about MX records can be found here.
AAAA Record	Associates your domain or host within the domain with an IPv6 address.
DYNAAAA Record	Part of the Dynamic DNS Service - associates your domain or host with your provider's temporary IPv6 address. The IP can be automatically updated using your router device or a client program. Ensure that Dynamic DNS (DynDNS) is enabled for your domain.
CNAME Record	Maps your domain or hostname to another domain or hostname. This is useful for creating aliases such as 'www.your-domain.com' and 'blog.your-domain.com', alongside an A record for your-domain.com. More information about CNAME records can be found here.
ALIAS	Somehow similar to CNAME, it allows to ALIAS can also be applied to the domain itself. Note that ALIAS records are not compatible with DNSSEC. More information can be found here.
DNAME	Similar to CNAME, but DNAME applies to all subordinate hosts (subdomains) of an entry. Additional details about DNAME records can be found here.
SPF Record	Sender Policy Framework - used to detect email spoofing and prevent spam. There are various free online SPF record creators available, such as the one found here. Please see below, how to define an SPF record.
TXT Record	Creates a TXT record for handling specific tasks, including requesting Let's Encrypt SSL certificates. See here for more information about TXT records.
SRV Record	Specifies the location of server(s) for a specific protocol and domain. More details about SRV records can be found here.
NAPTR Record	Specifies a regular expression-based rewrite rule that generates a new domain label or URI when applied to an existing string. Refer to this resource for additional information on NAPTR records.
NS Record	Specifies the responsible nameserver for a subdomain and is not allowed at top-level. More details about NS records can be found here.
CAA Record	Allows you to specify which Certification Authority (CA) is permitted to issue SSL certificates for your domain or hostname. See here for more information about CAA records.
TLSA Record	Validates certificates used for DNS-based Authentication of Named Entities (DANE). Additional details about TLSA records can be found here.
SSHFP Record	Specifies SSH fingerprints served by DNS. Refer to this resource for more information on SSHFP records.
SMIMEA Record	Secures SMIME (Secure/Multipurpose Internet Mail Extensions) with certificates. More information about SMIMEA records can be found here.

How to Define SPF Record

---

SPF means "Sender Policy Framework", and can be used to avoid forging of sender's addresses in emails. It is not a record type of its own, but uses TXT records for this.

There should always be only one SPF policy record for a domain, while the SPF definition may contain several different rules, and can be split over multiple TXT records with different names, if needed.

There are many tools online available to help with creating a SPF record for a specific domain, e.g. this one.

For instance, your Joker.com-domain is "example.com", and you want to allow emails from Gmail, you have to create a DNS record of type "TXT" for your domain "example.com", and enter this line:

v=spf1 include:_spf.google.com ~all

In case you want to make use of a SPF record for a Joker.com domain, and want to make sure that emails from Joker.com will reach email addresses using your Joker.com domain, you need to add (include) this additional rule to your SPF policy:

include:_spf.joker.com

resulting in this SPF policy:

v=spf1 include:_spf.google.com include:_spf.joker.com ~all

You can create more than one TXT record to split the SPF policy rules, then the records should all start with v=spf1 to define one SPF policy and every record must have a different name, or in other words - for every unique name (including domain itself) only one record starting with v=spf1 is allowed:

Correct:

example.com	TXT "v=spf1 include:_spf.google.com ~all"
spf1.example.com	TXT "v=spf1 include:_spf.joker.com ~all"

Incorrect:

example.com	TXT "v=spf1 include:_spf.google.com ~all"
example.com	TXT "v=spf1 include:_spf.joker.com ~all"

DNS PTR Records

---

A DNS pointer record (PTR for short) provides the domain name associated with an IP address.

A DNS PTR record is exactly the opposite of the A-record, which provides the IP address associated with a domain name.

DNS PTR records are used in reverse DNS lookups. When a user attempts to reach a domain name in their browser, a DNS lookup occurs, matching the domain name to the IP address.

A reverse DNS lookup is the opposite of this - it searches for a domain name with the given IP address.

This also means that PTR records can not be defined using the name servers of the domain, but have to be requested at the provider of the IP address, in case the provider supports this.