How can I make a child zone on Oracle Cloud with DNSSEC , which it apparently doesn't support? - dns

A few years ago, I moved my domains to a registrar that supports DNSSEC for .co.uk domains when I realised that Google Cloud Platform supported DNSSEC and SSHFP records. That worked fine on GCP.
Now I am doing a lot of work with Oracle Cloud. According to their DNS FAQ, DNSSEC is not supported. However, their DNS hosting on Oracle Cloud supports DNSKEY, DS, CDS and CDNSKEY as well as SSHFP records.
So how can I set SSHFP records for Oracle Cloud instances? If I keep the DNS hosting done on Google Cloud, can I use CDS/CDNSKEY records (or whatever) as a child zone on Oracle DNS?
I currently have DNS being done on Google Cloud, with NS records for specific hosts pointing at Oracle Cloud. There are NS records for every host. It works, but I don't know if there's a better way to do this, and DNSSEC obviously doesn't work.

Related

Azure DNS for country Domain

I want to use my country domain which is mydomain.id after setting up in my azure DNS and domain provider, I still cannot validate my domain in App Service. I already double-check everything and I think my settings are already correct. Now I wonder can we use the Country domain in my azure DNS because I'm afraid if it's that the problem.
First of all, I assume you are using a public domain. As Martheen's comments mentioned that you just need to create DNS records to map your app service IP or hostname like webapp.azurewebsites.net in your DNS provider so that you can add custom domains in your App Service. This is tutorial.
Azure DNS is a hosting service for DNS domains that provides name resolution by using Microsoft Azure infrastructure. By hosting your domains in Azure, you can manage your DNS records by using the same credentials, APIs, tools, and billing as your other Azure services. You have the option to host your records on Azure DNS.
After adding the DNS records, you can use the local tool nslookup or websites https://dnschecker.org/ to check the DNS propagation. It can take up to 72 hours to propagate worldwide, although it typically takes a few hours.

Azure VM: too frequent DNS lookup [TTL 60]

I have a VM setup on Azure (classic VM running CentOS). I am developing my mobile app that connect with RESTful API's hosted on Azure VM. My mobile app performance was slow and on investigation, I found DNS lookup to the FQDN of my Azure VM is too long (about 5-5.5 seconds per lookup) and very frequent. Attached is the output of "dig" tool on my Mac.
Dig tool output
Is there a way I can control TTL for the Azure VM's? Would it help if I buy a static IP and map it to my Azure VM's FQDN? Also, is there a way to reduce the DNS lookup time?
Thanks,
Giri
The TTL is associated to the domain name. If you want to increase the TTL you would need to purchase a domain name and associate it with the domain. With your own domain name you can set whatever TTL you require.
You would be far better developing against a domain name as this will give you the most flexibility with regards to developing against it, since you are able to move the location that your application points to, and should your app be particularly successful you would need a domain name for load balancing etc.

using own DNS server - how to configure

Currently I own a new VPS server and running my websites. For example I own www.auraquotes.com and that is running in this VPS server.
Currently I have issues with my hosting provider and I have switched to ovh unmanaged service provider. As the name 'unmanaged service provider' they will just help me in giving physical machines and that is all they will help.
how will I setup DNS server in my new VPS machine and adjust the nameserver settings appropriately?
Venkat.
DNS is a complicated service to set up and run, it is far easier to use an online DNS service, who will give you a nice web front end to configure things with.
The process is largely similar though, you need to configure your domain registrar with the name of your DNS server, or your DNS provider.
From there you configure the records you need and everything should work!

Use Google DNS service as a secondary/slave to an internal linux BIND9 DNS server

The company I work for is considering some changes to our DNS. We host an internal linux BIND9 DNS for primary and secondary authoritative DNS. We are thinking of changing either to hosting our public DNS externally, or keeping the primary on-site and move the secondary to a service like Google. I know it doesn't really make sense to keep our public DNS on-site or splitting it up, but the business owners would like to consider all possible options. I have looked through the documentation on-line and have contacted Google directly, but none of the sources I have checked will tell me if Google will allow us to use their DNS service to replicate a primary DNS server housed on-site and act as a secondary DNS for our domains. Does anyone here know if this is possible, and if it is what specifics they require to make it work. Any assistance that can be offered is appreciated.
Having a name server be a secondary authoritative name server for a domain of yours requires some cooperation from the owner of that server, so the only people who can tell you for sure if Google offers that service are Google themselves.

DNS problem, whois shows new servers, dig and soa nslookup show old older dns

I recently began migrating an old site to Drupal, and the hosting service I was using was really cheap and wouldn't have worked with all the modules I installed. I already hired a hosting account at a new (Drupal friendly) service and changed my DNS settings to point to their servers,... but the problem is that it's been a couple of days and the domain still points to the old account. When I whois my domain I can see in the domain servers section that the new servers show up, but if I nslookup or dig the domain I find the older servers. How could this be?
There are few possible reasons:
Your ISP is still resolving you domain name to the old servers
You have a local DNS server with a long TTL
You have a record in your host file pointing to the old server
The DNS change wasn't done correctly

Resources