testing
This commit is contained in:
parent
7d10f5dd46
commit
6fd5bdeced
@ -1,6 +1,6 @@
|
||||
# Common DNS issues
|
||||
|
||||
## Nameserver differences
|
||||
## - Nameserver differences
|
||||
|
||||
One of the most common DNS issues that can occur is when the nameservers in the DNS zone point to a different server then the one in the DNS zone
|
||||
|
||||
@ -31,7 +31,7 @@ The easiest way to tell this is to use the [dig](/Commands/dns#dig) command alon
|
||||
|
||||
I highly recommand also doing a `dig NS +short 'nameserver address'` for each of the sets to make sure they resolve to the same servers
|
||||
|
||||
## I updated my A record and now my mail is broken
|
||||
## - I updated my A record and now my mail is broken
|
||||
|
||||
This one is quite common in cPanel setups that have the MX records use the root domain
|
||||
|
||||
@ -44,7 +44,7 @@ $ dig MX +short benjamyn.love
|
||||
|
||||
In the above example the mail is using the root A record so you would update the DNS zone to use mail.benjamyn.love as the MX record and then make sure the mail. subdomain resolves directly to the server and is not another CNAME to the root
|
||||
|
||||
## DNS zone is not propagating but all the nameservers are correct
|
||||
## - DNS zone is not propagating but all the nameservers are correct
|
||||
|
||||
#### DNS records are not syncing at all
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user