I have the domain 'alexdollard.xyz' registered with Google domains
I added the custom resource record 'wp' as a type A, and pointed it to my digitalOcean droplet (a Wordpress instance)
I then added a CNAME record for www, and pointed it at my Netlify-hosted site. (This Netlify site is a gatsby/react site which will query my wordpress instance for blog-post data)
When I ping the IPv4 address of the wp subdomain in my terminal, I get a response. But when I ping 'wp.alexdollard.xyz', I get unknown host. And when I run it in the browser I get "wp.alexdollard.xyz’s server IP address could not be found."
I've been working with this subdomain for a while now and this issue just started. wp.alexdollard.xyz was working until yesterday.
I have already tried renewing my DHCP Lease, flushing my dns cache, and changing my DNS servers to public servers. For context, this issue didn't start until I deployed the site to Netlify, and pointed the google DNS name servers for alexdollard.xyz to the Netlify name servers. But wp.alexdollard.xyz should still point to this digitalOcean droplet since it's a subdomain, right?
I'm sorry if this question is sophomoric or dumb, it's possible that I really just don't understand the basics of DNS configuration. Seems like something simple is going on. What is causing this issue with my DNS?
DNS entry seem correct:
dig a wp.alexdollard.xyz
;; ANSWER SECTION:
wp.alexdollard.xyz. 3600 IN A 134.209.73.194
it is also resolving globally: https://www.whatsmydns.net/#A/wp.alexdollard.xyz
I can see two options here:
your local DNS is stil propagating or needs to be flushed
your droplet is not accepting this domain
I developed a wordpress website on localhost but when trying to host the website i get this error. www.medina.com took too long to respond.
Search Google for medina 8080. Any idea why this is happening?
I have edited my wp_options to the site url.
For running your website on local machine you need to use IP Address, your request is something like that
http://YourIPAddress:PortNo
If you want to use your own HostName, For that you need to put a entry in host file.
Right now I have a domain ex: foobar.com hosted on Bluehost.
I created an instance on AWS and fortunately, I used (wordpress by bitnami) to migrate my foobar.com to the aws site.
I created an elastic ip and associated it with my instance.
This is where I am stuck. I've read tons of tutorials telling me to go into my Bluehost and add a DNS record which I haved.
My first attempt was to do a URL redirect on foobar.com, which worked but only for the homepage because when I would navigate to another page, it would display the elastic ip (ex: 53.13.153.12/about).
I am unsure how to go about this problem.
Setup an A Record, not a URL redirect. You'll need to then configure the vhost on your server to understand that domain (I think you may have already done this step).
Bluehost has some documentation here
I have a domain registered in Australia. The site is hosted on VPS server on Rackspace. I wanted this domain to point to the VPS and so changed the ip address in Plesk Panel. Having made these changes I tried loading the domain but it doesn't and instead loads my ISP's site not found error.
So I did a ping and the results response indicate that the domain is pointing to my Rackspace ip as intended. I checked Apache's access and error logs but no haven't found any entries to indicate that the request was received by Apache.
I have been at this for a few days but can't seem to figure out what is wrong. Would appreciate any help to have this resolved.
I'm setting up a (ASP.NET) website to be used internally at my company. In IIS, I've turned on Integrated Windows authentication and turned off anonymous access. Once I've done this, the website pops up the "enter your username/password" box whenever you visit the site, but won't log you in even if the username/password are correct. This happens even if you're logged in to your computer with a domain account as opposed to a local account.
However, if I enter the IP of the site in my hosts file, the site works perfectly (logs the user in without the additional challenge).
I guess I have two questions.
1) Why does the hosts entry have this affect?
2) How can I get the site to succeed without a) forcing everyone to edit their hosts file or b) the site challenging them and failing to log them in?
EDIT: I checked, and we do have our DNS server set up to point those URLs to the correct servers. That's why pinging the URL displays the right IP. However, it appears that in addition to having that DNS entry, we also have to have the hosts file entry for the site to work.
You probably are having an issue with Kerberos authentication.
Since you're using a url of Site.DomainName.com, I'm assuming DomainName.com is your AD's name also.
On the server that's running IIS, copy SetSPN.EXE from the resource kit tools and run the following:
setspn -A http/site.domainname.com IISServerName
Where SITE is your URL and IISServerName is the name of the server.
This sure sounds like a dns problem. Does the dns server know about the hostname you are using? Sounds like the dns server does not know the forward lookup (hostname to ip) for the host you are trying to connect to.
We recently set up an intranet site with windows authentication here. The network guys setup a group policy and pushed changed to IE and Firefox.
For IE, it added the site to "Intranet Sites" and for Firefox it modified the configuration file so that our intranet..com would be trusted.
So... we got it to work. Here's what happened.
While looking around at the DNS Manager on test.DOMAINNAME.com, my coworker noticed that a different site on the same server was set up as a "Host (A)" entry, whereas the site we were working on was set up as an "Alias (CNAME)" entry. Several other sites on that computer were also set up as Alias entries, and he mentioned that the one site with the Host entry was "rock-solid", and he'd had sporadic issues with at least one other site that was set up as an Alias.
We talked to the AD/DNS admin, and as a test, he switched our entries from Alias to Host, and once we cleared our local DNS caches, it worked perfectly (without requiring entries in our .hosts file).
So the question still sorta stands. This was a Win2k3 box serving as one of three internal DNS servers, and making this modification fixed our problem. If anyone can add any additional information, we'd be very grateful, but in the meantime, we're debating going back and fixing all our other sites.