How can i solve dns confusion problem in my domain? - dns

I have a dns confusion problem in my domain, there are more than 2 months that I changed the nameservers of my domain to cloud housting vps but sometimes I find that the domain displays the page of my previous host namecheap as shown in the picture how can I always force the domain to give the google server and not the namecheap server?
enter image description here

Usually, I check the status of my domain propagation using this tool:
whatsmydns.net
Checking yours, I see that all servers are pointing to the right NS, as well as the A records are always responding with the same two IP addresses from cloudflare, which seems correct. I would recommend doing a full cache clear on the device you are testing and try again.

Related

How can I point my domain from Godaddy to another web server without using # and losing email services?

I have access to a Godaddy account where the company has all their domains. One of those I need to point to another web server running Apache. The person that used to work here before me solved this pointing to the new server IP using the record:
A # the.ip.addr.ess 1 hour
and in the webserver end I get it with Apache and as far as the webserver goes, it runs flawlessly. I even have some subdomains using the same A record structure.
But...now I have two issues. First, I lost email reception. I can send via smtp and webmail but anything sent to my domain gets bounced back after 24 hours, even if sent to an alias or forwarder.
The second issue is that I need to verify the domain with Firebase and even thou I created the TXT record, it cannot be found by Google. I'm sure it's because of the same reason.
What can I do? I understand a little about DNS and records, but not enough for this. I just want all html traffic to reach my webserver as it is now and keep the emails and other domain services working as they were.
As contacting Godaddy support, they said it is not their purview as it is external. I think they just don't know. Go figure.
Are you using GoDaddys NameServers? If not and these are pointing elsewhere no matter what DNS records you set in GoDaddy won't be picked up during DNS lookips. This may explain why the TXT record verification is failing. However if this was true changing the A record wouldn'd disrupt DNS.
# just means the root domain so no subdomain/prefix, mydomain.com.
www is a common subdomain used so you could have an A record which like:
A www the.ip.addr.ess 1 hour
so www.mydomain.com would resolve to the.ip.addr.ess
MX records are used to direct emails to your mail server. Make sure this is pointing to the mail server. If it's pointing at your A record then updating the A record will disrupt this.
Set the MX record to point to the.ip.addr.ess rather then mydomain.com, or an A/CNAME record other then your root domain (which you are updating)
Other considerations may need to be taken, if you have an SPF record (TXT record) this may also need updating, depending on it's current value.
I finally found what I had to do. I needed an A record named 'mail' pointing to the original Godaddy server IP address.
A mail my.ip.add.ress. 1 hour
Thank´s for all the help.

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

My domain name is pointing to different places on difference device

I bought the domain from GoDaddy and hosting from Hostgator. I am using that domain as the add-on domain in the Hostgator. I have updated the nameserver of HostGator in GoDaddy 30 hours before. It got propagated. But on some devices, it is showing the website content in Hostgator, but on other devices, it shows the GoDaddy page. I do not know what is the issue. i have cleared the cache, restarted the device, did everything but nothing solved the issue
sorry to say that i do not know what is mean by SOA serial number.If you give the right link i will learn that. My problem got solved by the following way. when i ping the website, i did not get the IP address of my hosting. Then i flushed the DNS through cmd. Then the website loaded. Thanks for the reply.
Could anyone say what is the IP address that i got before the flush. Is that belongs to domain registrars (GoDaddy)?

current domain linked to email hosting, wish to add different web hosting

I have setup web-hosting for the domain name, 'www.domainName.com' (forExample) and had it working fine, but when I removed the existing nameservers and placed in my web-hosting nameServers, it broke the 3rd party email hosting, which unbeknown to me was actively being used. To rectify this, my nameServers were removed, and the mail-hosting namerServers were added back:
ab1_mailNameServer_etc
ab2_mailNameServer_etc
Nothing else was changed but I now get a 'ERR_NAME_NOT_RESOLVED' error when i venture to the 'www.domainName.com' through my browser.
I looked up the domain A-Records using MXtoolBox and it tells me that no name servers can be found, although i have an A-Record for, domainName.com & www.domainName.com that point to the correct IP. I also have the correct A-Records in my hosting, and i know this because this all worked before my hosting nameServers were removed.
My question is, can I simply add back in my web-hosting nameServers under the existing email nameServers without breaking email-hosting link?
I am a lil frightened to do so, as I cannot risk breaking the email twice in one week.
Thanks in advance peeps! ;)
After changing back to mail-hosting's nameservers, if your emails have started working, then there's no problem with DNS propagation. In this case, an error "ERR_NAME_NOT_RESOLVED" is more likely a local computer problem and can be fixed by the flushing DNS and clearing the browse cache/cookies.
As long as primarily set nameservers (mail-hosting nameservers) are resolving correctly, adding hosting nameservers under to existing won't create any difference.
So apparently you can only have one set of nameservers (not sure if that's across the board, or just with this registrar) listed, then you need to add the 'MX entry', relevant CNAME, TXT-Records in your web hosting via cPanel and ur mail and web hosting should work in unity. Peace, hope that helps someoene, cause it took me freakn ages to find that out!

Setup CNAME alias from one domain to another

I'm attempting to satisfy the Cookieless domain suggestion of Google's Page Speed plugin and am running into a wall with my host who can't be bothered with the details of why it's not working. Accessing st1.dgcstatic.com should be the same as accessing st1.defunctgames.com; however, this is not the case.
Have I missed a step of configuration? Do I need to wait for DNS propagation? You can see below my steps of experimentation.
DNS Setup:
Created CNAME of st1.dgcstatic.com to point to st1.defunctgames.com on dgcstatic.com
Created A record of st1.defunctgames.com on defunctgames.com
Created sub-domain of st1.defunctgames.com on defunctgames.com
When I run a tracert st1.dgcstatic.com it produces the following result:
C:\Users\Patrick>tracert st1.dgcstatic.com
Tracing route to st1.defunctgames.com [50.22.11.10]
When I run a host st1.dgcstatic.com it produces the following result:
patrick:~ patrick$ host st1.dgcstatic.com
st1.dgcstatic.com is an alias for st1.defunctgames.com.
st1.defunctgames.com has address 50.22.11.10
And finally, using this site it seems to produce the same results of showing things configured correctly.
http://www.mxtoolbox.com/SuperTool.aspx?action=mx%3ast1.dgcstatic.com
According to all these results, the world can see my DNS changes, my host on the other hand gave me the "Wait for propagation" rigmarole When asked why this isn't working.
It looks to me that your domain names are set up correctly (st1.dgcstatic.com is an alias of st1.defunctgames.com), but the web host needs to have a mapping or configuration to know how to serve st1.dgcstatic.com content.
Both domains are resolving to 50.22.11.10, but that is most likely a shared IP address host. (Visiting http://50.22.11.10 demonstrates that it's shared - it can't resolve to your site just by the IP address.)
You'll need to configure through your webhost provider the second domain. Hosting companies do this differently; in my case it's just a matter of adding a new domain to my account (extra $1/mo), and configuring the path for HTML source files.

Resources