Can I connect Digital Ocean droplet/ digital ocean app(serverless) to domain that I bought in wix? - server

I have a domain that I bought in wix, Now I want to host my website in DIgital Ocean, How to connect droplet to wix domain

Yes.
Wix will probably use its name servers to ensure your domain's records are published. Wix provides a mechanism to manage your domain's records. You are able to add e.g. A, CNAME, TXT records.
See: Adding DNS records in your Wix account.
Droplets will generally be published on the Internet using IP(v4) addresses. You will want to add A(ddress) DNS records to alias your chosen host name in your domain to the Droplet's IPv4 address. For exmaple, to reference your droplet as droplet.[your-domain-name], you would create an A record with host name droplet with value set to the droplet's IP address.
Apps are published using SOMETHING.ondigitalocean.app (DNS) name. You will want to add CNAME DNS records to alias your chosen host name in your domain to the App's DNS name. For example, to reference your DigitalOcean Apps as app.[your-domain-name], you would create a CNAME record with host name app with value set to the app's SOMETHING.ondigitalocean.app name.

Related

How to Setup Reverse DNS On Linode for Your Instance when you use Cloudflare to Provide DNS

Hi Our site is based on Smartphone, Laptop, Gadgets Specs, Price
and we are using Linode server to get host our site but same sit opening in Linode rDNS, due to this most of our links such as https://www.pdevice.com/product/samsung-galaxy-s20-ultra-5g-price-specs opening with Linode domain address, we also contacted to them they have told us that, It looks like "pdevice.com" is your domain name but since it's pointing to CloudFlare's IP, you would need a work around in regards to setting reverse DNS. An option would be to create a subdomain and point this to your server's IP address. You may be able to get around this by having the "www" record for your domain point to your server's IP addresses rather than Cloudflare's IP addresses. and as we told we are using Cloudflare to provide CDN and DNS so how to solve this isse we can't recognize, because it shows issue while past RDNS to Subdomain.pdevice dot com, so how to do this with our server.

GKE Kubernetes external domain provider

I built simple cluster in GKE with two services using this tutorial
https://cloud.google.com/kubernetes-engine/docs/tutorials/hello-app
After finishing that I'm able to access my service using external IP address. So I bought domain for using this IP address. After setup A record in DNS settings to that IP address, domain doesn't work, it still loads and then show ERR_CONNECTION_TIMED_OUT. Do I need to do something in google console, or how I can make this IP public and accessed through domain?
Please refer to official documentation, which describes steps you need to take to configure domain names with static IP.
There are steps that you need to cover:
Go to NETWORKING section at GCP console, than VPC Network -> External IP addresses to ensure that you are running static IP address, not ephemeral one.
Go to Network services -> Cloud DNS. You need to create DNS zone, where at DNS name line you have to wright your domain name. After creation you will see Add record set, where you need to paste your external IP address.
There is also a good tutorial at YouTube with setting up custom domain on GCP. Let me know if it works for you.

How to identify a small Company's Public IP

I want to identify the Public IP address of a local company. More specific, i need the IP address where the offices are located. Because it's a small company, i assume they only have 1 public IP. The only thing i had, was the domain name. But i already did some investigation in DNS based on that domain name.
Result of the investigation based on domain name:
The company has 1 website, hosted by a hosting company. In DNS i did a lookup and i fetched the IP address of the website (A record), but it's the IP of the hosting company.
I found the domain name and IP address of 2 DNS servers registered for the domain, but they both are DNS servers of the hosting company which hosts the domain (NS records).
I found the domain name and IP address for 1 mail server registered for the domain (MX record). it seems that the company uses outlook as a mail server because the (MX record) is: domainname.com01c.mail.protection.outlook.com.
As you can see the results i already got are useless because they all point to services that are not hosted in the company's local offices but elsewhere.
Is there another way or method that i can use to identify the public IP used from the company's local offices? Or can i do more investigation based on the results i already found in DNS?
Use their Domain name to do a Whois Lookup:
https://whois.domaintools.com/
For example, with Google:
https://whois.domaintools.com/google.co.uk
You can also Use Maltego for more in-depth information on this but this is probably a question for https://security.stackexchange.com/
Maltego: https://www.paterva.com/web7/

Google Cloud Platform - Vanity Nameservers

I'm in the process of moving my DNS to Google Cloud Platform and wish to set up vanity nameservers.
Is this possible with gloud?
I have two domains currently in my project
abc-net.co.uk (vanity)
abc.co.uk (company domain)
I have set 4 records of
ns1.abc-net.co.uk A -> 216.239.32.109 (ns-cloud-d1.googledomains.com)
ns2.abc-net.co.uk A -> 216.239.34.109 (ns-cloud-d2.googledomains.com)
ns3.abc-net.co.uk A -> 216.239.36.109 (ns-cloud-d3.googledomains.com)
ns4.abc-net.co.uk A -> 216.239.38.109 (ns-cloud-d4.googledomains.com)
I have compiled all records in my project for abc.co.uk but when I run a dig against #ns1.abc-net.co.uk it tells me recursion is not allowed
Can I not set up vanity nameservers?
NS Specification
NS records must point to address records (e.g. A and AAAA) and not to alias records (e.g. CNAME).
- see RFC 2181 section 10.3
Summary
Correctly creating Google Cloud vanity nameservers is possible, but does require the risk of future server down-time if Google changes any nameserver IP addresses associated with your vanity nameservers. If such a risk does not bother you, use the following directions to create them.
Directions
Note: The following directions were provided at a time when IPv4 A and IPv6 AAAA records ruled the web.
Get each nameserver's IPv4 and IPv6 address.
``` $ host ns-cloud-x0.googledomains.com ```<br/><br/>
Create A and AAAA records for each vanity nameserver at your domain's local DNS zone.
Register each vanity nameserver's FQDN, IPv4, and IPv6 with your domain's registrar (e.g. Enom and GoDaddy).
Wait for your registrar to confirm the addition of your vanity nameservers.
Wait 24-72 hours to allow the new DNS records time to propagate.
Update the NS and SOA records of your domains to point to your vanity servers.
Yes, it is perfectly doable with Google Domains.
In the Custom resource records section, create A records and point them to Google DNS servers (ns1.abc-net.co.uk A -> 216.239.32.109, etc.), exactly as you did above
In the Registered hosts section, create glue records (ns1.abc-net.co.uk, etc.), pointing them to the same Google servers
In the Nameservers section, enter your custom name servers (ns1.abc-net.co.uk, etc.).
Wait for DNS propagation (it will be near instant if you use Google or Cloudflare DNS resolver).
Note that you won't be able to have DNSSEC active.
Hope this helps.
Instead of A records hardcoding the IPv4 address of ns-cloud-d#.googledomains.com, create 4 CNAME records, ns#.abc-net.co.uk, pointing to the ns-cloud-d#.googledomains.com servers. Then, your NS record would be all four of the ns#.abc-net.co.uk names that you made CNAME records for. I just did this with my domain and it is working great.
This allows the IP addresses of Google's resolver servers to change without breaking your DNS functionality. Additionally, IPv6 clients will resolve over IPv6.

Confusion about MX records

I'm very confused by the fundamentals of DNS records (in this case MX records). Right now I have registered a domain name (let's call it example.com). This domain is configured to my linode's IP via their nameservers.
The default MX record that is in the Domain Manager is 'mail.example.com'. Fair enough.
I followed this tutorial about setting up a exim server.
Exim Tutorial in Linode Library
and I'm kind of confused. My default hostname on the machine is 'antares' and thus the FQDN is 'antares.example.com'. In this tutorial I don't see how this 'mail.example.com' is coming into play? Where do I specify this? Or should I point the mail MX record to antares.example.com?
I'm very new to DNS records and even more new to mail records. Any hints to clarify my misunderstanding would be invaluable.
the DNS server for your domain will by default serve up the www or .domain.com entry to web browsers etc but it actually hosts a bunch of name pointers for other services, one of which is mail exchange.
Services which need your mx record value know how to look it up from your DNS server, so in this case they will find mail.domain.com when you supply the domain.com part.
If you need to set up a mail server you will need to change the mx record in your domain manager to point to your machine ip, this can be different from your default www host name/ip on the same domain as every service can be served by a different host (any ip).