I am trying to set up a custom nameserver in Cyberpanel, the following is what I've done:
I have a GoDaddy account which have my primary domain(e.g primarydomain.com), the nameservers for this domain(primarydomain.com) is managed by Godaddy, I've added two 'A' records, this points to the IP address where my Cyberpanel is installed (its a digital ocean droplet, all required ports are open):
Then i have added the nameserver details(of primarydomain.com) into the cyberpanel (i've followed these steps: https://forums.cyberpanel.net/discussion/257/super-simple-nameserver-creation) and it also tells me that nameservers have been added successfully.
Also the DNS zone is added (because when i try to add it shows dupliacation error)
But the issue is after successful addition of nameservers(as follows):
when I try to check if they are added successfully or not (via going into menu DNS -> Add/Delete Records) it shows nothing:
I've tried following the following tuts:
https://forums.cyberpanel.net/discussion/257/super-simple-nameserver-creation
https://cyberpanel.net/docs/1-manage-dns/
I've almost created and destroyed 3 droplets thinking it might be the issue with cyber panel installation.
Related
There seems to be a conflict between the DNS settings SquareSpace needs in order to set up a connection to the SquareSpace Analytics Search Console and what DNS settings Ionos will allow.
On Square Space the relevant setting are found at Home > Analytics > Connect followed by logging in with a gmail account and then clicking on Allow. At which we get the error message
Something went wrong
Sorry, something went wrong there. Please try again
I raised a query with SquareSpace and their response boils down to
There's one DNS record missing. You'd need to go into your domain's
DNS settings in your domain provider's end and then add the following
record:
Type: CNAME
Host: www
Points To: ext-cust.squarespace.com
Over to IONOS where the domain is registered and into the DNS settings which are currently
MX # mx00.1and1.co.uk
MX # mx01.1and1.co.uk
TXT # "v=spf1 include:_spf.perfora.net include:_spf.kundenserver.de -all" -
CNAME _domainconnect _domainconnect.1and1.com Standard Record
CNAME autodiscover adsredir.1and1.info Standard Record
A ftp 198.185.159.144
and attempt to add a new record as per SquareSpace's instructions above, only to get the error message
A CNAME record can only be set for a subdomain. To alias your main domain please use Redirect
But looking at redirect I'm worried that, if I set this up, all the email addresses that use the same domain and Ionos' mail servers will fail. I seem to remember trying this exercise about 2 years ago, but managed to kill everyone's email accounts (!) until I removed it again.
Has anyone had this problem and solved it? It seems specific to SquareSpace / Ionos as they both give a standard set of instructions which they expect to work.
Later
After working with Ionos' customer service desk, they managed to add the required Squarespace DNS entry and they now read
TYPE HOST NAME VALUE SERVICE ACTIONS
CNAME autodiscover.www adsredir.1and1.info Standard Record
CNAME www ext-cust.squarespace.com -
CNAME autodiscover adsredir.1and1.info Standard Record
CNAME _domainconnect _domainconnect.1and1.com Standard Record
TXT # "v=spf1 include:_spf.perfora.net include:_spf.kundenserver.de -all" -
MX # mx01.1and1.co.uk -
MX # mx00.1and1.co.uk -
A # 198.185.159.144
But the problem persists, something is still wrong when I try to attach the Google search console (AKA Squarespace Analytics Search Console -
Squarespace call it two different names in different parts of their site).
Having fixed the DNS entries to satisfy Squarespace, the "allow" error still persisted.
Squarespace customer service then suggested clearing the browser cache or using a different browser. Clearing the Chrome cache didn't work, but switching from Chrome to MS Edge did. Logging into our Squarespace account on Edge finally let the process run to completion.
I presume there must have been some information still cached in Chrome that Squarespace didn't like, I only cleared the temporary files, not the cookies or the history as I wanted to keep these for other sites.
The cause of the problem remains a mystery.
Recently, I just purchased a domain from AWS by using Route 53. The problem is that I want to point this domain to a wordpress website that lies in Vultr host, but even thought I changed the NS record on Route 53 to Vulture's and test it by using https://www.dnswatch.info/, it still cannot open my website when I enter new domain to browser. I got little knowledge when it comes to DNS so please help ..
This is Vultr's DNS setting
and Route53 setting (I have changed the sensetive info)
I believe the issue here is you are attempting to add the Vultr Nameservers as NS records in Route53. So, Route53 would still be your primary nameservers.
Instead you want to specifically change over the primary Nameservers / glue records (separate UI / settings area than DNS records). See the final section on this page for details on how to do this -
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-name-servers-glue-records.html#updating-name-servers-other-dns-service
My client has server which we developed a new website on. We are trying to point an external domain on another server to this website. Do we just update the A record with the highlighted IP or? See image attached
Probably your WHM control just have the option to do it (update DNS records) automaticaly. But, if don't. Try adding at A records:
ns1.gandlp.com > 162.144.250.139
ns2.gandlp.com > 162.144.250.140
at your DNS Zone Editor control on CPanel
I recently changed NS of one domain to another host and created a domain using Helm Control Panel.
The problem is that when I type domain name (ie. www.MyDomain.com) instead of opening the coresponding website, it opens host webmail page which is served by smarter mail.
I have cleared dns cache, rebuilt and updated it. also I removed the domain and added it again.
Pinging the domain name returns server's IP address and it's up.
The hosting OS is windows server 2003.
I appreciate any comments to solve the problem.
Edit 1:
Though this was a long last headache, I solved the problem by removing domain's DNS entry alongside with all alias domains attached to it directly in DNS Server console, restarting server and then rebuilding DNS Zone via Helm Control Panel. I'm not sure if this was the best practice but it seems there was a mix of domain's DNS, alias domains' DNS, Hosting software, Caching problems.
Edit 2:
Actually this error was not about the DNS stuff, it is a failure of Helm Control Panel adding/removing alias domains. To share the experience, I Add a answer to this question.
This was not a DNS error.
I found the answer when examining IIS where i noticed the website was stopped.
Forcing the website to start, this error message poped up:
IIS was unable to start the site, another site may already be using the port you configured for this site.
Further investigation revealed that one same domain alias has previously added to another domain/host.
Removing this alias from IIS > Website Properties > Website > Advanced > Advanced Website Identification, fixed the problem.
What led me to assume a dns problem mistakenly was that default IP of server is set to mail server by default. so, when a website is stopped the domain points to mail server.
Hope this help for future.
I'm attempting to satisfy the Cookieless domain suggestion of Google's Page Speed plugin and am running into a wall with my host who can't be bothered with the details of why it's not working. Accessing st1.dgcstatic.com should be the same as accessing st1.defunctgames.com; however, this is not the case.
Have I missed a step of configuration? Do I need to wait for DNS propagation? You can see below my steps of experimentation.
DNS Setup:
Created CNAME of st1.dgcstatic.com to point to st1.defunctgames.com on dgcstatic.com
Created A record of st1.defunctgames.com on defunctgames.com
Created sub-domain of st1.defunctgames.com on defunctgames.com
When I run a tracert st1.dgcstatic.com it produces the following result:
C:\Users\Patrick>tracert st1.dgcstatic.com
Tracing route to st1.defunctgames.com [50.22.11.10]
When I run a host st1.dgcstatic.com it produces the following result:
patrick:~ patrick$ host st1.dgcstatic.com
st1.dgcstatic.com is an alias for st1.defunctgames.com.
st1.defunctgames.com has address 50.22.11.10
And finally, using this site it seems to produce the same results of showing things configured correctly.
http://www.mxtoolbox.com/SuperTool.aspx?action=mx%3ast1.dgcstatic.com
According to all these results, the world can see my DNS changes, my host on the other hand gave me the "Wait for propagation" rigmarole When asked why this isn't working.
It looks to me that your domain names are set up correctly (st1.dgcstatic.com is an alias of st1.defunctgames.com), but the web host needs to have a mapping or configuration to know how to serve st1.dgcstatic.com content.
Both domains are resolving to 50.22.11.10, but that is most likely a shared IP address host. (Visiting http://50.22.11.10 demonstrates that it's shared - it can't resolve to your site just by the IP address.)
You'll need to configure through your webhost provider the second domain. Hosting companies do this differently; in my case it's just a matter of adding a new domain to my account (extra $1/mo), and configuring the path for HTML source files.