DNS IP Check Cpanel Reminder/Notice - dns

everyday i get following email from the cpanel, i dont know what it means and in current configuration, i have a one ip for a ns1.nameserver and one for ns2.nameserver but top level domain nameserver is mapped to one ip address. but there is no way to add a another A record to there (i dont knw how) or i want to disable this notice out, since still all works fine in the network...
The hostname (nameserver.com) resolves to 67.xxx. It should
resolve to 67.xxxx. Please be sure that the contents of
/etc/hosts are configured correctly, and also that there is a
correct 'A' entry for the domain in the zone file.
Some or all of these problems can be caused by /etc/resolv.conf
being setup incorrectly. Please check that file if you believe
everything else is correct.
You may be able to automatically correct this problem by using the
'Add an A entry for your hostname' option under 'Dns Functions' in
your Web Host Manager.

Two ways to resolve the issue.
Add the correct A record for the IP and Fully Qualified Domain name
Per cPanel it is not suppose to function behind a NAT though as many have found this does in fact work. So you can "Fix" or stop this message by going into the contact manager and disable the “Ip address dns check” option

You need to make sure that you have properly added A record for your hostname and assigned it to IP address of your server. For example, if your server hostname is xyz.abcd.com then you need to add xyz A record in abcd.com DNS zone and point it to your server IP address.

Related

What could be the possible reasons if nslookup command for a domain is not showing correct records?

I am not able to access one of my website from office which is hosted in Microsoft azure. When i have tried to lookup for dns lookup.
I is not showing me the correct ip address or showing some thing like mydomainname.kkph.com.
While i can access the same website from other devices around the world.
I have also checked with Godaddy support team but didn't find any issue at their end.
First, you could ensure that you have a correct IP address binds with your website and have a mapping A or CNAME record in your DNS domain provider.
For this issue, you could check the followings:
DNS cache on the local office machine. Use ipconfig/flushdns to clear it.
DNS Suffix Search List. You could check if you have a DNS suffix automatically appended to your hostname when you query. You could check it via 'ipconfig/all' or find the box Append parent suffixes of the primary DNS suffix and DNS Suffix Search List under the Advanced TCP/IP Settings---DNS. Also, to avoid using the search list, always use a Fully Qualified Domain Name (that is, add the trailing dot to the name) when you run nslookup fqdn. Read here.
Try to nslookup on another machine from the office to find if there is something wrong with a specific machine.
If no luck, please show the result of nslookup for further help. I would like to suggest to capture the netmon traces on your local environment.

whois lookup shows correct ip but why my browser can not find IP address of domain?

My website suddenly stopped working.
When I search for the domain name in WHOIS websites it is showing the correct server ip address and correct DNS IP address.
I can reach the website by its IP address but somehow when I am trying the domain name in browser its not working and its showing "This site can’t be reached"!
There is no error in my server log.
I tried different browsers and different systems and it is same issue.
I am really confused. Even when I am sending GET requests with Postman to my domain, it not reachable but sending request to IP is working!
whois and DNS resolution are two separate things and one does not imply anything for the other, so in short, except in very specific cases, if you have a DNS resolution problem you should use DNS troubleshooting tools, not the whois and especially not web-based whois (the only relevant whois is the registry one).
Now you are giving so few details that noone can really help.
Among the possible ideas to check and probable problems:
you forgot to renew the domain, your registrar put it on hold or worse deleted it (that you can see in whois)
you did a change in the DNS resolution and now it does not work anymore, use online troubleshooting tools like Zonemaster or DNSViz; alternatively your registrar and/or webhosting company should be able to help (since you are neither giving here the domain name nor details about the troubleshooting you do: for DNS problems, the browser is not the first tool to use, look instead at dig).
in appear that the problem was DNS on our local system. we changed it to 8.8.8.8 and then we could access to our domain!
it's usually because you use an addon domain, not the main domain for hosting orders that are set up on cpanel whm

How to point a domain without changing name servers

My client has a website at exampleA.com, but want their new domain name exampleB.com to point to the server that hosts exampleA.com.
They have certain emails setup with exampleB.com...so I want to avoid changing the name servers, in case I mess with these settings (I don't know all the info yet).
If I simply want exampleB.com to point to a different server, what DNS records should I change? I have a static IP for the server.
Is it just the A record I need to modify? I'm not good with this DNS malarkey.
Thanks for your help.
Mikey.
Yes, just update the A record. You may have to update the web server config file on exampleA.com server to listen and serve the requests for exampleB.com.
If the static IP address you have is in IPv6 format then you would have to update the AAAA DNS record.
Yes, by changing A record in the domain account will solve the problem. In this case, you do not need to change the nameserver in the domain account

How to test CloudFlare without changing your domain's name server

How can you test CloudFlare without changing your domain's name server?
I would not want to change my domain's name server and wait hours for propagation only to find out there is a issue with the DNS settings.
Can you spoof a nameserver or something on a local hosts file?
Yes, you should be able to test before you change your name servers. Here's what to do:
Signup at https://www.cloudflare.com/sign-up and complete the signup through Step 4 when you're asked to update your name servers.
Note the two name servers you are provided which will be in the format [name].ns.cloudflare.com.
From a terminal, do a lookup to get the IP addresses your domain has been assigned. In Linux/Unix it'd be: dig #[name].ns.cloudflare.com yourdomain.example
Repeat step 3 with all the subdomains you want to check.
Update your localhost record to resolve the domain(s) to the IPs you found with the lookup.
Browse the site from the same machine where you did the localhost update and traffic should pass through CloudFlare.
While this will work for a while, after 24 hours CloudFlare's system may detect that your name servers haven't updated and, in some cases, may return an error. However, this technique should allow you basic testing before you update your name servers.
To save future users from some headache, the above answer doesn't work anymore: https://community.cloudflare.com/t/ip-on-cloudflare-nameserver-is-not-masked-despite-orange-cloud/76137
From my understanding, you now need to change your nameserver.

How does my shared host's nameserver resolve http://servername.com/~username/ to my top level domain?

I recently moved my website to a shared hosting solution at asmallorange.com, but I had to set my domain to use their provided nameservers in order for the site to properly resolve. I was determined to keep control of the domain's DNS but I could find no way to make my top level domain resolve to the shared location which was in the format of
server.asmallorange.com/~username
So I know I'm missing something here, my question is this:
What in their nameservers/DNS entry makes it possible for server.sharedhost.com/~username to serve as a top level domain? (ie. http://topleveldomain.com)
Nothing. DNS simply maps topleveldomain.com to server.sharedhost.com. It's the webserver which looks at the Host: topleveldomain.com header and knows that's equivalent to server.sharedhost.com/~username.
Nothing. They are having your domain name resolve to the same IP that server.asmallorange.com resolves to, but then they are making their web server aware of the domain name topleveldomain.com, and telling the webserver that it is the same as server.asmallorange.com/~username.
Virtual hosts aren't a DNS trick, they're an HTTP trick - the hostname requested is sent by the browser in a Host: field of every request.
apache has a "mod_user" which you can enable in your apache conf file. Using this and virtual hosts is how that is accomplished.
Virtual Hosts in Apache are how this is done.
However just because you set the DNS up to go "mydomain.com resolves to 1.2.3.4", which is their IP address, doesn't mean that you're giving up control of your domain name.

Resources