This guide explains how to access the DNS record creation tool in the client area and how to complete every field in the form.
Before you fill in the form, follow these steps to open the “Create a DNS Record” modal window:
- Sign in to your client area.
- Open the My Domains > My Domain Names menu or go directly to https://www.adhci.com/clientarea.php?action=domains.
- Click the domain name you want to manage.
- Select the DNS Zone tab.
- Click Create a DNS Record.
You can then use the form to add a new DNS record for your domain. Each record is a “rule” that tells the rest of the Internet how your domain should behave (for example, which IP address should serve www.yourdomain.fr
).
Form Fields
1. Type *
Choose the DNS record type you want to create:
Type | Common usage |
---|---|
A | Maps a subdomain to an IPv4 address |
AAAA | Maps a subdomain to an IPv6 address |
CNAME | Points a subdomain to another domain name |
MX | Defines the mail server for your domain |
TXT | Stores text information (SPF, verifications, etc.) |
DKIM, DMARC, SPF | Used for email security |
SRV, TLSA, SSHFP, CAA, etc. | Advanced use cases (VoIP, certificates, DNSSEC…) |
ℹ If you are unsure which type to choose, refer to the instructions provided by your service vendor (web host, email provider, etc.).
2. Subdomain
Enter the subdomain name the record should apply to.
@
→ applies directly to the root domain (e.g.yourdomain.fr
)www
→ will apply towww.yourdomain.fr
test
→ will apply totest.yourdomain.fr
_dmarc
ordefault._domainkey
→ specific cases for DMARC / DKIM records
Do not enter the full domain name here. The system appends it automatically.
3. Target / Value *
This is the record value, which depends on the selected type (see table below).
4. TTL (Time To Live)
This field sets the cache duration for the record in seconds.
- Default: leave the field empty to use the default TTL.
- Custom: enter a value between
60
and86400
seconds.
Example | Meaning |
---|---|
60 |
1 minute — ideal during testing or frequent changes |
3600 |
1 hour — a common production value |
86400 |
24 hours — recommended for stable records |
Lower TTL values allow changes to propagate faster but slightly increase DNS load.
Example Values by Record Type
Type | Subdomain | Value / Target | TTL | Quick explanation |
---|---|---|---|---|
A | test |
192.0.2.1 |
3600 | IPv4 address |
AAAA | ipv6 |
2001:db8::1 |
3600 | IPv6 address |
CAA | @ |
0 issue "letsencrypt.org" |
3600 | Authorises Let’s Encrypt to issue certificates |
CNAME | blog |
example.com. |
3600 | Redirects to another domain name |
DKIM | default._domainkey |
AQ8AIDAQAB |
3600 | DKIM public key |
DMARC | _dmarc |
v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com |
3600 | DMARC policy |
DNAME | subzone |
alias.example.com. |
3600 | Redirects an entire zone |
LOC | @ |
48 51 29.000 N 2 21 07.000 E 100.00m 10.00m 100.00m 10.00m |
3600 | GPS coordinates |
MX | @ |
10 mail.example.com. |
3600 | Mail server with priority |
NAPTR | @ |
100 10 "U" "E2U+sip" "!^.*$!sip:info@example.com!" . |
3600 | For SIP and other services |
NS | @ |
ns1.example.com. |
3600 | Name server |
RP | @ |
hostmaster.example.com. admin.example.com. |
3600 | Technical contact |
SPF | @ |
v=spf1 mx a -all |
3600 | Legacy TXT format still in use |
SRV | _sip._tcp |
10 60 5060 sipserver.example.com. |
3600 | Priority, weight, port, target |
SSHFP | @ |
1 1 123456789a...bcdef67890 |
3600 | SSH fingerprint |
TLSA | _443._tcp |
3 1 1 d2abde240d...10bd7a0dab |
3600 | TLS certificate association |
TXT | @ |
"Hello world" |
3600 | Free text or SPF/DKIM |
Full Example
Field | Value |
---|---|
Type * | A |
Subdomain | test |
Target / Value * | 192.0.2.1 |
TTL | (leave blank) |
➡ Result: an A record is created for test.yourdomain.fr
pointing to 192.0.2.1
with the default TTL.
Common Mistakes to Avoid
- Entering the full domain name in “Subdomain”
- Using an IP address in a CNAME record
- Forgetting the trailing dot (
example.com.
) - TTL outside the 60–86400 range
Helpful RFC References
- RFC 1034 & RFC 1035 — Foundational DNS concepts and records (
A
,CNAME
,MX
,NS
,TXT
, etc.) - RFC 3596 —
AAAA
records for IPv6. - RFC 1876 — Geographical positions with
LOC
records. - RFC 2782 — Service discovery with
SRV
records. - RFC 2915 & RFC 3403 —
NAPTR
records for telecom services. - RFC 4255 — Publishing SSH fingerprints using
SSHFP
. - RFC 6376 — DKIM signatures (
DKIM
). - RFC 6672 — Zone redirection with
DNAME
. - RFC 6698 — TLS certificate association (DANE) with
TLSA
. - RFC 7208 — SPF (
TXT
andSPF
records). - RFC 7489 — Email authentication policy with
DMARC
. - RFC 8659 — Certification Authority Authorization (
CAA
).
Need Help?
If you are unsure about anything, contact our technical support with the relevant service (website, email, etc.).