I am trying to host a website, I changed to Name servers and all, however I am receiving this error
The webserver reported that an error occurred while trying to access the website. Please click here to return to the previous page.
Can some body help me on this?
Thank you
First ensure that the domain is resolving to the IP's you configured, for this you could use tools like dig / drill, or via the web you could use https://intodns.com/
To check the nameservers via command line:
$ dig example.com ns +short
To check for the 'A' records:
$ dig example.com
If you just change the nameservers it may take a while for them to be replicated, you can use the +trace options:
$ dig example.com ns +trace
When tracing is enabled, dig makes iterative queries to resolve the name being looked up. It will follow
referrals from the root servers, showing the answer from each server that was used to resolve the lookup.
If that returns the expected results, check your web server configuration.
Related
I want to get the aliases that is returned by nslookup as below:
F:\>nslookup maans20210630125234.sandbox.operations.test.dynamics.com
Server: UnKnown
Address: 2001:4898::1050:1050
Non-authoritative answer:
Name: apimgmths6q7kyczcrkpvds6u99ofw4apdrqgxc8s7qavl14wy.cloudapp.net
Address: 52.188.3.251
Aliases: maans20210630125234.sandbox.operations.test.dynamics.com
d365-ops-dev-gwy-eastus-eus2-2.azure-api.net
apimgmttm0hgnv1tmdyrtilrp0hcvphjwrq4gtyzzfdqehnzfn.trafficmanager.net
d365-ops-dev-gwy-eastus-eus2-2-eastus-01.regional.azure-api.net
nslookup
I want equivalent of above in c sharp. I already tried Dns.GetHostEntry. It does not return aliases as mentioned in official document. How do I get the aliases in C# / .NET?
Dns.GetHostEntry(hostNameOrAddress)
"Aliases" are DNS CNAME records. So you need to find out how to query for DNS CNAME records from your DNS library. You probably need to use a low level DNS library that lets you control all low level details of a DNS query, because high level calls like GetHostEntry are designed to just give you the final answer and hiding the intermediate steps (the CNAME chain resolution).
On the command line the equivalent are:
$ dig maans20210630125234.sandbox.operations.test.dynamics.com +short
d365-ops-dev-gwy-eastus-eus2-2.azure-api.net.
apimgmttm0hgnv1tmdyrtilrp0hcvphjwrq4gtyzzfdqehnzfn.trafficmanager.net.
d365-ops-dev-gwy-eastus-eus2-2-eastus-01.regional.azure-api.net.
apimgmths6q7kyczcrkpvds6u99ofw4apdrqgxc8s7qavl14wy.cloudapp.net.
52.188.3.251
This follows all the intermediate CNAME and gives you the final IP address (as dig does A record type queries by default)
But if you specify record type CNAME you get only the first answer (and hence you will have to do yourself a loop to find out all intermediate CNAME until you get an error or the final answer):
$ dig maans20210630125234.sandbox.operations.test.dynamics.com CNAME +short
d365-ops-dev-gwy-eastus-eus2-2.azure-api.net.
I'm trying to set up my root domain as my link in the link settings form.
when I put it I get this warning.
Domain is incorrectly set up; please use the nameservers below as your
NS record. A CNAME record is not required. If you've already done
this, note that it can take up to several hours to propagate.
ns-907.awsdns-49.net.
ns-1438.awsdns-51.org.
ns-1683.awsdns-18.co.uk.
ns-401.awsdns-50.com.
So I changed my ns in goddady to those
now if I run $ host -t NS getgogro.com I get 2 different outputs randomly
getgogro.com name server ns64.domaincontrol.com.
getgogro.com name server ns63.domaincontrol.com.
I believe this 2 are still godaddy's default dns, but I dont always get that output
and http://getgogro.com/ already takes me to branch.io
but in the Link Settings section I sell get the same warning
Domain is incorrectly set up; please use the nameservers below as your
NS record. A CNAME record is not required. If you've already done
this, note that it can take up to several hours to propagate.
ns-907.awsdns-49.net.
ns-1438.awsdns-51.org.
ns-1683.awsdns-18.co.uk.
ns-401.awsdns-50.com.
Thanks for reaching out to Branch. Let me follow up with you directly via email!
I don't know how to ask this question appropriately.Maybe it is a duplicate one, if so, please let me know.
When I use dig to resolve www.google.com and google.com, it gives me different answer.Why? Please refer me to articles relative to this.Thanks:-)
www.google.com and google.com are separate DNS entries and can point to two different servers. For most sites one is just a CNAME of the other, meaning that they both end up pointing to the same server, but this is not a requirement.
Historically NASA has been reluctant to support nasa.gov for www at all, and this blog post makes an interesting read.
I setup a couple of nameservers and updated my domain to use them, and as far as I can tell everything went fine and the nameservers have been updated, or so says every whois and dnstools type site ive used, (intodns, who.is etc are all saying the same thing: the new nameserrvers are in effect, and the site points to the new ip just fine). Problem is that The site is not showing up, and dig tells me that the old ip/nameservers are still effective.
In my DNS Records I have:
domain. A IN NS ns1.newnameserver
domain. A IN NS ns2.newnameserver
ns1 IN A newipaddress
ns2 IN A newipaddress
domain. IN A newipaddress
I'm very short on time and haven't found anything on the interweb, so any help would be much appreciated
The old IP address is probably being cached by the server you queried. First of all, check that BOTH your new authoritative nameservers are publishing the correct address by querying them directly with dig:
dig #ns1.newnameserver domain. a
dig #ns2.newnameserver domain. a
Assuming those queries give correct answers, dig some other servers that aren't:
dig domain. a # Use the system's default resolvers
dig #8.8.8.8 domain. a # Use Google's public resolver
dig #some.other.ip.address domain. a
If it gives the old answer, look at the TTL. That's the numeric field listed in the answer just after the name and before "IN". That's how many seconds you have to wait until the server you queried discards its cached data and will query the authoritative servers again.
Ask those same nameservers where they think "domain." is delegated:
dig domain. ns # Use the system's default resolvers
dig #8.8.8.8 domain. ns # Use Google's public resolver
dig #some.other.ip.address domain. ns
You want to see 2 NS reocrds for "domain.", one pointing to "ns1.newnamserver" and the other one to "ns2.newnameserver", but the resolvers likewise cache that information so they might still have the old nameservers. If so, look at the TTL on those NS records too. If the TTL on those records is longer than the TTL on the A records, those resolvers may still go to the old nameservers to get "domain."'s A records even when their currently cached copy expires... so you may need to wait for that TTL to expire first, and then for the TTL on the actual A record to expire again!
Another thing you can do is query some of the authoritative nameservers for the PARENT domain of your domain to see if they are indeed delegating it to "ns1.newnameserver" and "ns2.newnameserver". This will verify that the delegation in DNS matches what's in WHOIS.
dig com. ns # If your domain's parent domain is "com."
dig #<one-of-the-servers-that-resulted-from-that-query> domain. ns
Again, you want to see 2 NS reocrds for "domain.", one pointing to "ns1.newnamserver" and the other one to "ns2.newnameserver".
If the old nameservers are still running, either:
make sure they aren't, or
make sure they've also got the new zone data
Some people will still be talking to the old nameservers, and until they either stop answering or give the right answer, they won't learn the new nameservers from the parent zone.
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.