I want to upload my local wordpress to the domain I bought and make it live. But I don't know how to add domain and add dns in oracle cloud.
Unfortunately, there's no simple answer to your question. The general documentation on using Oracle Cloud DNS Service can be found here. Below is a quick summary of tasks that need to be completed:
Note the public IP address assigned to your compute instance that's hosting the web server. Assign one if necessary. The compute instance must be on a public subnet to be assigned one.
In your tenant's root compartment, create a Zone for your domain, e.g. example.com.
Create an "A" zone record, e.g. www.example.com => 123.123.123.123
Publish the record.
On your Registrar's DNS management console, update the name server records to point to Oracle Cloud's name servers assigned to the zone.
Related
I need to transfer DNS management to AWS Route53 so I can host multiple Wordpress sites with different domains on a Lightsail instance using Plesk Obsidian. I've already set up one domain and its website. The next domain I need to setup for a Wordpress site that'll run on the Lightsail instance has an existing subdomain that's used for an app running on an EC2 instance. That EC2 instance's URL doesn't use a Route53 zone, i.e., it just has an A record that associates the subdomain to the EC2's static IP address.
My question is whether I need to create a Route53 zone for the subdomain after I move DNS record management to Route53, or is just keeping the A record for the subdomain in the Route53 DNS records sufficient without creating a separate Route53 zone?
Hopefully my question/concern makes sense. My concern stems from whether Route53 behaves like any other DNS manager or if it has peculiarities I need to be aware of for what I want to do.
I figured I'd just have to learn by trial and error since no one answered.
I created the A record on Route53 to point to the subdomain and switched to AWS nameservers ... and voila, it worked without having to add the subdomain as a Route 53 zone. My security certificate even resumed working on the subdomain after a 10 minute period in which it couldn't find the CNAME record of the certificate issuer.
So long story short, Route53 works just fine for pointing to subdomains outside of the Route53 zone. One A record does the trick.
I have created a SAS in Alibaba cloud with ghost template as the image for SAS. I have also created a domain name on domain.com and now I am trying to configure the domain name to the ghost app running on SAS. But when I add the domain name the Resolution Status for this domain still shows as Unresolved. The below error message is displayed on the top of the console.
Domain name, which uses Alibaba Cloud DNS, can be resolved here directly. Other domain should be resolved manually with corresponding DNS service provider.
I have also added the domain name on Alibaba Cloud DNS so I am not sure why this is still not getting resolved. Any help will be much appreciated.
Contact your registrar to establish an A record that maps your domain name to the IP address of Alibaba Cloud SAS (Simple Application Server).
Refer:
https://www.alibabacloud.com/help/doc-detail/59080.htm
I'm trying to do something pretty simple. I have a domain on godaddy. I want to use Azure Dns to host the domain and connect it to an azure website.
I have it working for www.mydomain.com with the CNAME approach. However I cannot get the root domain, i.e. my domain.com to work with this approach. I tried adding an * A record but that didn't work. I also tried to do CNAME with # but that didn't work either.
Does anyone know how to get the root domain to work? This seems pretty basic but there is no documentation and it is not obvious.
Thanks
Thanks for feedback on this one!
If you need to create the isolated deployment with the static IP, take a look at the Service Environment. The reference first and second.
As you mentioned Azure DNS, i assume that you refer to the Azure DNS service. If so, then it is possible if you have the needed access. Reference for the DNS zones.
Regarding your question about www and CNAME, there are some nuances that should be taken into account and set up. Please refer to that post.
You can set up a DNS 'A' record in Azure DNS to point to the IP address listed for the site in the Web Apps portal (as per the screenshot provided by an earlier answer). The Web Apps team provide the IP address for precisely this purpose, and they know that they can't change these IP addresses because DNS entries would break.
Note that there's no need to use a wildcard record (name = '*'). You should instead use an A record at the domain apex (name = '#', or if using the Azure Portal you can also leave the name blank).
If your hosted your WebAPP in free website plan didn't have any option for adding * A record. You have to Change your web App plan to at least Shared Plan instead of free Plan.
I am having troubles with setting up custom domain for my heroku app.
here is my heroku app:
https://evening-beyond-1234.herokuapp.com/
and let's say it is my domain:
my-fake-domain.com
So I want my app being able at this domain.
I've added this domain to heroku app domains:
$ heroku domains
=== evening-beyond-1234 Heroku Domain
evening-beyond-1234.herokuapp.com
=== evening-beyond-1234 Custom Domains
Domain Name DNS Target
---------------- ---------------------------------
my-fake-domain.com evening-beyond-1234.herokuapp.com
And on the site where I've bought the domain I can change DNS, so I did this:
1) Type of DNS -> DNS from other hosting provider
2) 1st DNS server (*required) -> evening-beyond-1234.herokuapp.com
3) 2nd DNS server (*required) -> evening-beyond-1234.herokuapp.com
I put the same for the second DNS, because it is marked as required, so I need to specify two DNS.
It's been a few days after these changes and it does not work.
There is also another option for changing DNS: extended DNS editor.
I can specify CNAME entries and others there.
Any ideas what I am doing wrong?
I am completely new to this area, it should be just a silly mistake from my side %)
Your configuration is incorrect. What you are doing is that you are changing the name server of your domain, hence moving the delegation to Heroku.
However, Heroku is not an authoritative name server, hence you can't delegate your domain to them.
What you need to do is restore the delegation at your hosting provider and, instead, check the documentation of your hosting/DNS provider to learn how to create an A or CNAME record to point your domain to Heroku.
Also note that you will not be able to point your apex domain (hence my-fake-domain.com to Heroku unless you use one of these DNS providers that support a CNAME-like capability for the apex domain.
Regardless who you use, you can create a CNAME record to point www.my-fake-domain.com to evening-beyond-1234.herokuapp.com.
For my-fake-domain.com you either create an ALIAS/ANAME according to one of those provider documentation, or you redirect the domain to the www version.
I have a server that I have assigned an external IP address to it and NAT'd through in my firewall. Then I have assigned with my domain host provider and made a DNS name to point to that external. All is great from the outside, and inside if I point to the local IP address of that server.
My problem is that the software that is on the server I cannot access certain Java features outside of the network because the local IP address is hardcoded into the software and Java wont read both internal and external IP address. So tech support on the software said we can put in a DNS name into the software.
So I went into the DNS of my domain controller and put in an Host (A) entry of subdomain.domain.com and the local IP address. Well it doesnt resolve right because DNS made the entry I put in as subdomain.domain.com.local so again Java doesn't read it right. How do I make DNS read this entry right as subdomain.domain.com?
Is this a windows DNS solution and domain controller? if so, the A record should just be "subdomain" (windows will add on domain.com since that is the domain for the domain controller). If this is the case, try that A record, and it should work.
UPDATE
Based on comments below, it sounds like you need to do this:
Create a new zone using your external domain name.
Open DNS console.
Click on Forward Lookup Zones.
Right-click, choose new Zone, type in the name of the external
domain name (srb1.com).
Once created, right-click the zone you just created, choose New Host
Record.
Type in 'software' (without the quotes), and provide the internal Private
IP address of your internal webserver.
These instructions were pulled from here: Scenario 2