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)
Related
In Azure, I have purchased a Custom Domain and the configuration has been done automatically - all good till now however the site is accessible only using: www.sitename.com
If I access it using http://sitename.com only, it is not working.
For info, I tried to remove the CNAME however didnt allow.
Suppose I dont want to use the wwww, how can I do ?
Thanks.
If you want to access your website with http://sitename.com, you have to create the A record and enable the A record mapping in the app. For how to map an A record, this doc is for your reference.
1.Copy the app's IP address
2.Create the A record
An A record to map to the app's IP address.
A TXT record to map to the app's default hostname.
3.Enable the A record mapping in the app
The custom domain you configured is not secured. You'd better click on "Add binding" to bind an existing custom SSL certificate to your app. For more details, you can refer to the doc.
The in the DNS for domain sitename.com the A record to is what make http://sitename.com works.
If you want http://www.sitename.com to work you HAVE TO have a www CNAME record.
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
I am trying to set up a secondary azure website in a different subscription.
When creating the Custom Hostname for the new site location, I am forced to validate the hostname.
Azure complains that the hostname is registered against a different CNAME and prevents me from adding it.
This is true, but I don't care, I want this to swap over from the old website to
the new one when the DNS records propagate.
I the old IIS world, I'd have just added the hostname to two servers and when the dns pointed to the correct one, it worked.
Now in Azure it validates that the Azure Hostname I am pointing it to is correct and that the cname record already exists, it isn't 'valid' until I change the DNS.
I have to disassociate the current cname, then add to my new site.
I'm sure the only issue here is the "validation", there is no reason why I can't have the name in two places, dns decides which it goes to, not the end point web site.
I'd like to be able to set this alias, whether valid or not, so that when it becomes valid, it works.
The result I get is validation prevent me adding the hostname.
- I have to ask the client to change the DNS Record
- when they manage to do that, they will tell me
- only then I can go in to Azure and add the hostname to make my site work.
There is documentation for this exact scenario: https://learn.microsoft.com/en-us/azure/app-service/app-service-custom-domain-name-migrate
You can create a TXT record with host:
awverify.register.tourofmargaretriver.com
and value:
cyclingeventuresregistration-production-webapp.azurewebsites.net
This verifies domain ownership without directing traffic to it.
How can I make so when a user goes to my website, they should not use their local ISP DNS to resolve my website IP, rather they should use Google DNS i.e 8.8.8.8
How can I configure this on my web server?
I'm not sure if I misunderstand but how would someone get to your site in the first place without using their current DNS? You can't change someones DNS they can only change it themselves.
Could someone explain the difference between an A Record and a CNAME, and what I should be telling my users to do if I am building a site that allows for custom domains to point to a subdomain on my hosted service?
A record... www.rabbot.com -> 123.123.123.123 (ie. an actual IP address)
CNAME record... www.philip.com -> www.rabbot.com (ie. more like an alias)
Your life will be much simpler if you have your users to use a CNAME as they can point their domains to yours. Then if you need to update your server's IP address you can simply update the single A record you have instead of making all your users update their DNS entries.
This is true regardless of what web framework you are using...