by Stephen DeLorme
DNS records tell peopleβs computers how to get to your website, email, etc.
DNS converts example.com into 205.142.35.67
@ IN A 172.134.55.67 ; example.com
Company or organization that registers your domain. They point to your name servers.
Where your DNS records are hosted. DNS records point to your host.
There are lots of nameservers in the world. Your nameservers are the authority for your domain.
Your host is where your website lives.
(Or we could be talking about a service provider, like in
the case of email or a digital marketing tool).
Youβre trying to migrate to a new host and are worried about experience downtime.
Use your DNS to establish a subdomain. Setup site at new host under the subdomain and get it running. Once running, point the main domain to same place as subdomain. When the propagation is complete, users will seamlessly be directed to the cloned site without noticing. π
NAME TYPE POINTS TO
@ IN A 172.134.55.67 ; example.com - TacoHost Server
staging IN A 164.55.78.125 ; staging.example.com - Our new hosting server
Create a clone of your website on the staging server. This could be done manually by copying the files and database of your WordPress site, or using a migration plugin.
NAME TYPE POINTS TO
@ IN A 164.55.78.125 ; example.com - Our new hosting server
staging IN A 164.55.78.125 ; staging.example.com - This can be deleted now
In a shell, run the command:
dig example.com a
Or just go to whatsmydns.net π
Then π»
Your host cancels your account. Or your host messes something up. Or a malicious threat cyber-actor [insert current jargon] hacks the crap out of your zone file. π±
You can actually copy the text of the zone file if you like, or you can just take a screenshot of the DNS records as you see them in the browser. πΎ
If you only take away one thing from this talk, let it be this.
Somebody with access to your DNS manipulates the records to point your traffic somewhere else. π€¬
For further reading: What Is DNS Hijacking?
Pay close attention to who has access to your DNS records. Donβt give out the password all willy nilly. Basic security hygiene. π
Can be due to the host (most common, in my personal experience). But also people have to do a DNS lookup to get there, and slow DNS just adds to the time it takes. π΄
Switch to a professional DNS provider thatβs separate from your registrar or host. π₯
Your mail is not coming from the same server as your website is hosted on. So any email from your WP site goes to spam. π©
This establishes at the DNS level which servers can send mail on your behalf (with the IP, not the domain). Add any server you want to send mail from to the SPF records. π§
In this example, only spf.protection.outlook.com, salesforce.com, and some server at 201.56.71.59 can send mail on behalf of your domain.
NAME TYPE VALUE
example.com. IN TXT "v=spf1 include:spf.protection.outlook.com include:salesforce.com 210.56.71.59 ~all"
DKIM is a technique for digitally signing emails. It uses a private key on the mail server and a public key that is published in the DNS records.
tl;dr It helps your email client verify that the email you are looking at really cames from where it says it did.
Offload all of your site's mailing to a 3rd party provider. They typically support SPF and DKIM.
You will likely need to modify your DNS records to use a 3rd party service. It will vary from provider to provider, but will likely involve adding MX records and TXT records. π©