I have a domain name on Google Domains that I want to point to my website running on my raspberry pi server at home. My public IP address is dynamic, and I cannot figure out how to keep the domain pointing at my IP when the IP is updated. Is anyone familiar with Google Domains dynamic DNS configuration?
I initially configured a "Custom Resource Record" on the DNS tab of Google Domains because the description says "Resource records define how your domain behaves. Common uses include pointing your domain at your web server or configuring email delivery for your domain." That works until my IP changes, then the domain name no longer points to the correct IP.
Next, I tried adding a "Dynamic DNS" Synthetic record to my Google Domains DNS configuration. I have a cron job that runs on my server every 5 minutes and runs the following (with USERNAME and PASSWORD set to match the credentials generated by Google Domains synthetic record):
curl https://$USERNAME:$PASSWORD#domains.google.com/nic/update?hostname=$HOSTNAME&myip=
When the curl command runs, it does successfully update the IP address in the Synthetic Record, as I would expect. But, the IP address in the "Custom Resource Record" does not update and the domain no longer points to the correct IP. I need to manually change the Custom Resource Record to the correct IP for it to work again.
Actually figured this out. I was giving the synthetic record a made up subdomain because I thought I had to and the solution was to simply leave it blank.
If you want to configure the entire domain, rather than just a subdomain, place '#' (without the quotes) in the sub-domain field. This will redirect everything
Related
From what I understand an A record maps a domain name to an IP of a machine that serves content/provides API.
When I look up my DNS records I get two A records. One points to my machine and another one points to an IP belonging to Namecheap company (ipinfo.io). The second A record is not shown in the "Advanced DNS" panel on their website in my account, so I can't delete it. Why do I have the second A record? What is the point of it?
I think I figured it out. In admin panel on namecheap.com I added redirects, so that when a user types example.com their browser redirects them to https://example.com.
In the DNS system there's no special records that handle redirects like that, so a company like namecheap adds an A record and points it to its own dedicated server that redirect users to a destination point in my case https://example.com
I'm trying to deploy my website and bind dns to this website. So, the dns was used by the old website and now I need to access the dns setting page and modify its A Record and pair its domain name to its new ip address. The domain name is managed by yahoo small business. So I log in and done the changeup like this.
however, When I type the "vbridgetech.com" it does show the apache default page. But when I type "www.vbridgetech.com" it still goes to the old webpage. I thought the only thing I have to do is to change the old ip to new ip. Anyone has idea about it?
If 59.120.185.12 is you new site's IP address, then just add another CNAME record:
CNAME record www.vbridgetech.com vbridgetech.com
(There are other ways to do this, but this should be the safe one)
I think I have just successfully connected my domain to my web host and have done so by following an article. There seems to be 2 different ways of doing so and I wonder if there is a difference between the two.
method 1
Go to your domain provider. Create an A record that points to your web host's ip address.
method 2
Go to your domain provider and edit the nameservers according to what your web host indicated. Go back to your web host and add a DNS record indicating the domain.
I have followed method 1 and it works. Is it any different from the second method? In addition, when typing out a record at the domain provider, what does #, www, and * mean?
The A record maps a name to one or more IP addresses, when the IP are known and stable.
# * are same as known as domain name (e.g. yourdomain.com) some domain registrar using # instead of entire domain and some uses *. In hosting control panel under DNS records there domainname is mentioned instead of # OR *
If you work with method 1 and changing A record then you will have to change A record to WWW as well to work your domain with www else your domain with www will ended up with no result. You will also have to change all required records such as CNAME (if you have any subdomain), mail (if it is working through hosting provider).
So best practice is to use namererver so you don't need to change every record under Domain Control Panel.
My client have a dedicated server on liquedweb cloud service and we my web app is hosted on that server. We want our users to map their domain to our server. So they can enjoy our web app by using their domain name. What information I need to provide to my user so he can map domain and what information I need from them?
I don't know much(in fact anything) about domain mapping
thanks
It depends if the server has a dedicated IP address or is natted.
If the server has a dedicated IP address you can ask your clients to point their entire domain to you server by adding the following A records:
Host TTL Protocol Type IP Address
# 300 IN A 1.1.1.1
www 300 IN A 1.1.1.1
Not all domain hosts ask for TTL,if not dont worry about it.
If you want just their subdomain to point to your server (subdomain.website.com)
subdomain IN A 0.0.0.1
TTL is optional in some systems, in this case the default will be used.
Generally it is recommended that you use an IP for the Apex record and not a domain name. EG: example.com is the apex, www.example.com is the www subdomain.
A typical configuration would be below:
Host TTL Protocol Type Result
# 300 IN A 1.1.1.1
www 300 IN CNAME example.com
This is the same config as the top example but using CNAME example.com. It is the same as using A 1.1.1.1, it just means you only need to change one record.
If your server details are a hostname and not an IP address, most systems will not let you use the hostname for the apex so you will need to find out the IP address. (A simple method is to use the nslookup command or dig command).
TTL is how long in seconds a record last before it expires. If you are unsure what you are doing I recommend lowering this so you can correct mistakes more quickly.
Different methods for the different servers. For most of the servers, you have to change the nameservers of your domain.
This mostly needs when your domain registrar and hosting provider both are different.
First Login into your hosting account, navigate to the account details,
then copy the nameservers from there...which would be like :- dns1.hostingprovider.com
dns2.hostingprovider.com
After that, Go to control panel of your domain. Navigate to the nameservers
You will see the link:- dns1.domainregistrar.com
dns2.domainregistrar.com
Paste the above links at the place of below links.
They need the IP address (and possibly instructions on how to configure their DNS servers (which means a variety of different sets of instructions for different servers and control panels)).
You need the domain name.
I'm totally new about hosting website and I register a domain in network solution and hosted by hostgator. I tried to register my name server by going to Domain name server option in network solution and enter my name sever's name.However,by going to leafdns.com, I found out that the name servers don't pointing to the right ip addresses as provided by hostgator welcome email. Besides, network solution does not prompt you for a ip input for those name servers, and the domain still point to a construction page.
What would be the problem?
It's not enaught to set up Name Servers for domain, you need add records in it. If you setup hostgator hosting NameServers for your domain, just park your domain on hosting panel and NS records add apear automatically.