: New DNS record won't resolve on a custom name server that is functioning I'm having trouble moving the DNS for a site. We migrated our site from a shared-hosting server to a virtual private
I'm having trouble moving the DNS for a site. We migrated our site from a shared-hosting server to a virtual private server (VPS). The custom name server for the VPS account has been running domains properly for two years. But now it won't resolve for the domain of the site we migrated.
The hosting company and our registrar keep pointing fingers at each other and won't fix whatever the issue is.
I know very little about DNS and have just relied the records the host adds to VPS when we migrate a domain -- or the Add DNS Zone feature in the accounts WHM dashboard.
I've tried to compare the DNS records of the newly migrated site to the records for the domain that ARE resolving from the same custom name server. Here's what I've found:
The new, non-resolving domain has a record that none of the working domains have:
test 14400 IN A (ip address)
All but one of the working domains have the following records that the non-resolving domain doesn't have:
autoconfig 14400 IN A (ip address)
autodiscover 14400 IN A (ip address)
_autodiscover._tcp 14400 IN SRV 0 0 443 cpanel.maildiscovery.net.
The one working domain that doesn't have the above records has:
ftp 14400 IN A (ip address)
default_domainkey 14400 IN TXT (long character string)
Can anyone tell me what's going on? Do I need to add autoconfig, autodiscover and _autodiscover._tcp to the domain that's not working?
More posts by @Cugini213
1 Comments
Sorted by latest first Latest Oldest Best
The extra records that you found shouldn't effect whether or not the domain name resolves. To get your domain name to resolve:
Make sure your domain registrar is pointing the NS records to your DNS servers
Ensure that your DNS servers are all returning the correct IP address when queried for the hostname and subdomains.
I recommend testing this with the command line tool dig. If you don't have it on the command line, it is also available through a web interface: toolbox.googleapps.com/apps/dig/
Check the name server (NS) records first. Substitute your domain name instead of example.com. Check the answer section and make sure that the DNS servers listed are what you expect. The DNS servers for example.com are a.iana-servers.net and b.iana-servers.net. You should have at least two DNS servers and may have as many as four. The name server host names are supplied by your DNS host, but entered into your domain registrar. If any of the NS information is incorrect it will need to be changed through your domain registrar.
$ dig NS example.com
;; ANSWER SECTION:
example.com. 5457 IN NS a.iana-servers.net.
example.com. 5457 IN NS b.iana-servers.net.
Next check each of the DNS servers for the domain name. Check both the bare domain name, the www subdomain, and other subdomains you have active. Ensure that the IP address returned in the answer section is the correct IP address for your webserver in all cases. From the commands below, we see that the IP address for example.com is 93.184.216.34. Substitute your domain name for example.com and a.iana-servers.net for your dns server when running the commands below. The IP address for your site is supplied by your web host, but needs to be entered into the settings on your DNS server. If any of the IP address records are wrong, they need to be changed with you DNS host.
$ dig @a .iana-servers.net example.com
;; ANSWER SECTION:
example.com. 86400 IN A 93.184.216.34
$ dig @a .iana-servers.net example.com ;; ANSWER SECTION: example.com. 86400 IN A 93.184.216.34
$ dig @b .iana-servers.net example.com
;; ANSWER SECTION:
example.com. 86400 IN A 93.184.216.34
$ dig @b .iana-servers.net example.com ;; ANSWER SECTION: example.com. 86400 IN A 93.184.216.34
Your domain registrar, and your DNS host each have to have the correct settings and records for your domain name to resolve to your webserver. With the dig tool, it isn't hard to check that each has the correct settings.
Terms of Use Create Support ticket Your support tickets Stock Market News! © vmapp.org2024 All Rights reserved.