Mobile app version of vmapp.org
Login or Join
Reiling115

: Nameserver problem I recently bought a new VPS, and I was trying to set private nameservers in my domain cPanel. I went ahead and added 4 A records: ns1.mydomain.com - points to my IP ns2.mydomain.com

@Reiling115

Posted in: #Dns #Domains #Nameserver #Vps

I recently bought a new VPS, and I was trying to set private nameservers in my domain cPanel.

I went ahead and added 4 A records:


ns1.mydomain.com - points to my IP
ns2.mydomain.com - points to my IP mydomain.com - points to my IP
mydomain.com - points to my IP


and changed the nameservers to ns1 and ns2.mydomain.com. The problem is that now
while typing ns1.mydomain.com and ns2.mydomain.com in the browser, it points to the correct IP address, but the mydomain.com domain is returning an error:

The webpage at mydomain.com/ might be temporarily down or it may have moved permanently to a new web address.
Error 137 (net::ERR_NAME_RESOLUTION_FAILED): Unknown error.


The error message above was received in Chrome.

10.01% popularity Vote Up Vote Down


Login to follow query

More posts by @Reiling115

1 Comments

Sorted by latest first Latest Oldest Best

 

@Kevin317

What happens when you run your domain through intodns.com? That can help you spot errors in your setup.

A common mistake is including or not including a dot on the left hand side of the entries in zone setup.

Consider this entry with a dot



This creates a record "testing" pointing to the specified IP address. Probably not not what you want.

Consider this entry with out a dot:



In this case, if your domain was "domain.com", the resulting A record would be:
testing.domain.com pointing to the specified IP address.

10% popularity Vote Up Vote Down


Back to top | Use Dark Theme