Is there a direct option to have a custom domain on Oracle cloud free tier (the always free options)?
There are threads talked about accomplishing that through installing a compute instance and installing a web server but it was at year 2017. So, I thought there could be a better solution now.
If you go to the VM instance ( Compute > Instances > Instance details), under "Primary VNIC" you should be able to see the instance Subnet.
Clck on it to open subnet details, and there you will see subnet's DNS name:
(DNS Domain Name).
Each instance's DNS name should be:
Instance FQDN: <hostname>.<subnet-DNS-label>.<VCN-DNS-label>.oraclevcn.com
Source & more details: https://docs.oracle.com/en-us/iaas/Content/Network/Concepts/dns.htm
Please see:
Free Oracle Cloud: Custom Domain Name (URL) with your own ORDS on the Webserver
Introducing Vanity URLs for APEX and ORDS on Oracle Autonomous Database
Related
I have the following network setup and try to join EC2 instances with an on-prem active directory.
Ec2 running inside a private non-routable subnet
Ad connector runs in a on-prem connected subnet
the domain is dns resolvable throughout the whole VPC
In this setup is it possible to join the ec2 instance through the AD connector without having the instance a direct connection to the on-prem AD?
When the AD Connector is up and running with status active, should it show up in the on-prem directory as domain controller?
Anyone experience which Windows Server versions are supported for the AD connector? Server 2019?
After a dive deep in this topic i have answers, which might help others looking into topics arround AD on AWS.
The AD Connector only helps with joining an instance to your AD
The wording proxy is meant literally (not a technical proxy server), it is the proxy which creates the computer object inside your AD for you, afterwards you need to join the instance (mostly done using a AWS Systems Manager AWS-JoinDirectoryServiceDomain document.
The Ec2 instance in fact needs direct network connectivity with the domain controller, of course the domain (fully qualified) needs to be resolvable as well.
Details on the plugin for joining can be found here: https://docs.aws.amazon.com/systems-manager/latest/userguide/ssm-plugins.html#aws-domainJoin
One important feature for me is, you can define a OU were the computer object should be created!
I have installed gitlab on a gcp debian vm instance. Now I have a domain name lets say xyz.com that is hosted on a different shared hosting platform which has my personal website. Now I want to add gitlab.xyz.com to my gcp instance. I followed the tutorial by gitlab and edited
/etc/gitlab/gitlab.rb
But it doesn't seem to work. I am new to this so, if anyone could outline the steps I need to perform then it would be really helpful.
To solve your issue you should reserve a static external IP address for your VM instance and configure DNS record for your subdomain.
I am trying to replicate the steps in this post. However, When I get to the step where I create the ad connector, it fails with the following error:
Connectivity issues detected: DNS unavailable (TCP Port 53) for IP 10.0.0.4, DNS unavailable (TCP Port 53) for IP 10.0.0.5. Please ensure that the listed ports are available and retry the operation
I am very proficient with AWS. However, I'm struggling with Azure and feel I may have misconfigured something. I have carried out the following steps thus far:
In Azure, I used an existing resource group and created "Azure AD Domain Services" instance using default configuration
Basics
Name: sy******k.com
Subscription: Pay-As-You-Go
Resource Group:
Default Region: UK South
SKU: Standard Forest type: User
Network
Virtual network: (new) aadds-vnet
Subnet: (new) aadds-subnet
Subnet Address: 10.0.0.0/24
Network Security Group: (new) aadds-nsg
I created a site to site vpn connection with azure virtual network. However, I am not sure about this step in the post: "The tunnels must be configured to allow traffic from your AADDS endpoints and the Subnets" How exactly do I do this?
In AWS VPC cidr is 10.1.0.0/16 and both tunnels between AWS VPC and Azure Virtual Network are up and connected. I tried to contact the post author: "Justin Stokes" directly but can't find any emails for him. I cannot find a single online guide on how to set this up step by step along with the site to site ipsec setup. It would be very very helpful if someone can provide a video tutorial for this step by step from A-Z instead of leaving a chunk of the steps out of the guide.
The troubleshooting guide here suggest that the firewall i.e. network security group is not allowing port 53TCP/UDP inbound for AD Connector. But I updated the networks security group as a test with a rule to allow any source, any destination and any port and still I'm getting the same error.
I am not the expert in both AWS and Azure but succeeded to setup VPN using this guide.
Then set up AD Connector and had to take tip of creating DHCP Option set from this post.
AD Connector created successfully now. EC2 instances launch with correct DNS server and suffix however they are not joined to AD, that's where I am now. If you have anything or completed this setup, please share.
I've (hopefully) successfully set up Cpanel on AWS with clustering following the instructions: https://blog.cpanel.com/part-1-how-i-built-a-cpanel-hosting-environment-on-amazon-aws/
I've been using CPanel/WHM on a dedicated server for a few years before I set up this new Cpanel installation on AWS. My issues comes from how new accounts are set up differently on a dedicated server vs the AWS way.
My first issue:
When I created a new account on my dedicated WHM, I was provided IP Addresses from the server farm that I assigned to newly created accounts. Once assigned, I can access the site with either the IP or the domain name. Now with this new AWS way, there's no info in the tutorials about how I obtain new IP Addresses. I tried adding a new local IP like 10.0.0.30 (because it says it's in NAT mode and use local IP) and assigning this as a dedicated IP to the newly created accounts but I don't understand how anybody can access the site through that IP since its a local IP. So how do I access the domain through custom IP and domain like I did before? I must be missing something fundamental.
My second issue:
On my dedicated WHM after I created a new account, I would typically go to DNS Functions -> Edit DNS Zone and edit the zone to customize my nameserver as so:
mynewdomain.com
ns1.mynewdomain.com
ns2.mynewdomain.com
anothersite.com
ns1.anothersite.com
ns2.anothersite.com
thirdsite.com
ns1.thirdsite.com
ns2.thirdsite.com
and then in my register I would add these custom nameservers into the register and point them to the dedicated IPs of each domain. But with the AWS way, the only way I was able to set this up was to use the new cluster nameservers as the nameserver for ALL accounts in this new WHM installation.
Like this:
mynewdomain.com
ns1.awsnameserver.com
ns2.awsnameserver.com
anothersite.com
ns1.awsnameserver.com
ns2.awsnameserver.com
thirdsite.com
ns1.awsnameserver.com
ns2.awsnameserver.com
Is this the correct / the only way I can set up accounts now through this set up?
Is there a way to have custom nameservers names like I did in dedicated WHM?
In my case, I have a DNS server outside of Amazon so I'm not sure it would answer your question but it might lead you somewhere.
First to figure out what your public IP is you can:
Go to the AWS console and look at the instance detail of your server.
Look for the "endpoint". This points to your public address so you can do a PING or NSLOOKUP to find out what your IP is.
However, AWS does not recommend you hard-coding the public address as it could change. So what I did instead was to create a CNAME in my DNS that points to that "endpoint".
I hope that helps.
I'm new to Amazonaws. created a Mysql DB instance on RDS. with a free account.
Now when trying to connect from local machine by MySqlWorkbench.
below is the endpoint of my db instance
XXXXXXXXXX.XXXXX.us-west-2.rds.amazonaws.com:3306
using the same as above as hostname and port on local still not able to connect.
Does it has anything to do with the region? I mistakenly selected Oregon(west) region whereas I'm in New Jersey(east)
There are two primary solution candidates.
Firewall
Go into VPC Security Groups (I guess that is where you control the firewall. My paid account uses Security Groups). Ensure that your public IP (and only your public IP) is allowed through the firewall.
MySQL Permissions
On the local machine, check that your remote machine is allowed to connect. It's also possible that MySQL is not running. You'll discover if that is the case while checking permissions locally.
Thanks a lot guys, Following are the steps to correct.
Go to MySQL instance. ]
click on security Icon.
Click on security Group
at bottom click on Inbound
Click Edit
Add your IP for MYSQL db or any DB instance you have.