I’m trying to park my own domain to it but I ha ve a problem. On the Parked Domain Management (Aliases) page there is a message saying that I have to point my own domain to these 2 NS:
I can see that there are also Register.it nameservers over Byet ones. However, to add a domain into your account, you must change the nameservers, and after adding it, you can safely change them to Register.it ones.
Yes, I didn’t remove register.it nameservers because, as I said before, If I do this operation they 'll remove all my additional services (email, PEC and so on).
Is this the problem?
Is there another way to point my domain? This method for domain’s ownership check is not so good because if that domain is not mine I can’t create on that registar an A record! It is unuseful
I agree it would be nice to have a domain ownership validation method which does not require nameservers to be changed beforehand. Not only does it avoid having to bring down any website or other service currently on the domain while the nameserver settings propagate, it also helps people whose registrar or registry simply doesn’t allow them to change the nameservers in advance.
I agree (and repeat) that having some other options to validate the ownership of your domain would be good to have, but I am certain that having some domain ownership validation is necessary.
If you add a domain which is not yours, then whoever owns that domain will not be able to host the domain with us because it’s already hosted with us. Which is worse, because it stops users for a reason they had no part of and have no way to do anything about. In your case, you still have the option to accept some downtime on your domain or move to a registrar which does allow you to set your nameservers the way you want them to.
And I cannot recall how many times I’ve seen issues with people unable to send email to gmail.com or hotmail.com because someone else on the server though it would be funny to add that domain to their own account, which caused the local mail server to get confused and try to deliver the mail to the local hosting account.
So I know how annoying it is that you have to change your nameservers beforehand, but simply removing that requirement is not an option.
Did you read the article @Ergastolator1 posted? It explains this exact issue.
The TL;DR is that yes, it is a known limitation that you cannot host domain names with us if the registrar or registry requires the nameservers to be configured beforehand.
And, for the third time, yes, it would be useful to have other verification methods for many different reasons, most importantly the reason you’re experiencing right now.
Yes, you don’t need to repeat that the .it registry requires this. You’ve made that abundantly clear. We know that this prevents you from using your domain name with us. In fact, so many people have had this issue that we decided to write a knowledge base article about it. So you don’t need to repeat that this system is suboptimal, because many people over many years have told us about this already.
But you have to keep in mind that this is a design limitation, not a bug. So we can’t quickly bugfix this, because the “fix” is an alternative verification system.
“…many people over many years have told us about this already…”
And you don’t made a correct configuration of your DNS server… The limitation now is not that we must point our domains to yours nameservers but that yours nameservers are not correctly configured like the standardization requires.
Anyway, no problem, I’ll use your service for a testing purpose, thanks, I appreciate your replies
We’ve got hundreds of thousands of people using free hosting, and only a small team to build new features for this service. As much as we would love to build every improvement people suggest to us, that’s simply not possible. An alternative domain verification method is on our wish list, but not something we’ve gotten around to implementing yet.
Our nameservers will be configured correctly as soon as the domain name is added to an account. It’s not that our nameservers are configured badly for your domain, because they are not configured for your domain at all.
