Hi, I entered the nameservers indicated by this host in my domain panel, but 7 days have passed and they don’t update, very strange because it works with other nameservers…
Hi and welcome to the forum
Please tell us the domain name
Hi, since I saw that it didn’t work, I changed host, I have to wait a few days to return the nameservers
Often customers do not confirm the e-mail they receive from the domain registrar when they buy a domain
or the domain registrar has protection against NS changes and must be additionally confirmed
or the domain has some form of lock, etc.
So there are many reasons…
But generally, when changing NS… after 1 hour (actually less than 15 min. but I took some safe value), our system should recognize it and allow you to add the domain here to the system.
Hi, my domain provider would also like the ip of the nameservers
Hi, I changed the nameservers this morning but they didn’t change and yet I didn’t do anything wrong
This is domain venturecraft.it
unless this is the case
then
If DNSSEC is active, the name servers can not be changed without breaking the DNS zone
Disable DNSSEC at your DNS provider
Wait 24 hours
Switch name servers.+
Wait 24 hours
? *(1)Re-enable DNSSEC
I also see that you are using Cloudflare NS
so check there dnssec as well
*(1)basically you should do this when you add the domain here to the system and then return it to Cloudflare and then enable dnssec
Okay
these are your NS currently visible
ns1.register.it
ns2.register.it
and you have a pending update status
DNSSEC is no longer signed and that’s ok
Wait for a while and if NS is not changed to ns1&2.epizy.com then I assume that it has not been approved by the authority
As a last resort, you can ask support for clarifications and answers
it Come modificare i DNS - Register.it
eng Come modificare i DNS - Register.it
Even if DNSSEC is being updated, can I change nameservers?
It’s best to contact support and explain everything you want to them
and let them give you the answer
in the article (it) I linked…you have this:
so please click and talk to them.
We can’t know what’s wrong with your provider and why it’s taking so long and if it’s even possible to change NS, etc.
<domain>venturecraft.it.</domain>
<status>FAILED</status>
<validationId>7693b910-f3b3-43a3-831b-4659017ec9a3</validationId>
<validationDate>2023-04-30T09:54:53.877+02:00</validationDate>
<nameservers>
<nameserver name="ns1.epizy.com.">
<address type="IPv4">198.251.86.154</address>
</nameserver>
<nameserver name="ns2.epizy.com.">
<address type="IPv4">198.251.86.152</address>
</nameserver>
</nameservers>
<tests>
<test name="NameserversResolvableTest" status="SUCCEEDED">
<nameserver name="ns1.epizy.com." status="SUCCEEDED"/>
<nameserver name="ns2.epizy.com." status="SUCCEEDED"/>
</test>
<test name="IPCompareTest" status="SUCCEEDED">
<nameserver name="ns1.epizy.com." status="SUCCEEDED"/>
<nameserver name="ns2.epizy.com." status="SUCCEEDED"/>
</test>
<test name="SOAQueryAnswerTest" status="FAILED">
<nameserver name="ns1.epizy.com." status="FAILED">
<detail status="FAILED" queryId="1">'REFUSED' returncode</detail>
</nameserver>
<nameserver name="ns2.epizy.com." status="FAILED">
<detail status="FAILED" queryId="2">'REFUSED' returncode</detail>
</nameserver>
</test>
<test name="SOAMasterCompareTest" status="WARNING">
<nameserver name="ns1.epizy.com." status="WARNING">
<detail queryId="1">Test skipped for 'REFUSED' returncode</detail>
</nameserver>
<nameserver name="ns2.epizy.com." status="WARNING">
<detail queryId="2">Test skipped for 'REFUSED' returncode</detail>
</nameserver>
</test>
<test name="IPSoaTest" skipped="true"/>
<test name="NSQueryAnswerTest" status="FAILED">
<nameserver name="ns1.epizy.com." status="FAILED">
<detail status="FAILED" queryId="3">'REFUSED' returncode</detail>
</nameserver>
<nameserver name="ns2.epizy.com." status="FAILED">
<detail status="FAILED" queryId="4">'REFUSED' returncode</detail>
</nameserver>
</test>
<test name="NSCompareTest" status="WARNING">
<nameserver name="ns1.epizy.com." status="WARNING">
<detail queryId="3">Test skipped for 'REFUSED' returncode</detail>
</nameserver>
<nameserver name="ns2.epizy.com." status="WARNING">
<detail queryId="4">Test skipped for 'REFUSED' returncode</detail>
</nameserver>
</test>
<test name="NSCountTest" status="WARNING">
<nameserver name="ns1.epizy.com." status="WARNING">
<detail queryId="3">Test skipped for 'REFUSED' returncode</detail>
</nameserver>
<nameserver name="ns2.epizy.com." status="WARNING">
<detail queryId="4">Test skipped for 'REFUSED' returncode</detail>
</nameserver>
</test>
<test name="MXQueryAnswerTest" status="FAILED">
<nameserver name="ns1.epizy.com." status="FAILED">
<detail status="FAILED" queryId="5">'REFUSED' returncode</detail>
</nameserver>
<nameserver name="ns2.epizy.com." status="FAILED">
<detail status="FAILED" queryId="6">'REFUSED' returncode</detail>
</nameserver>
</test>
<test name="MXCompareTest" status="WARNING">
<nameserver name="ns1.epizy.com." status="WARNING">
<detail queryId="5">Test skipped for 'REFUSED' returncode</detail>
</nameserver>
<nameserver name="ns2.epizy.com." status="WARNING">
<detail queryId="6">Test skipped for 'REFUSED' returncode</detail>
</nameserver>
</test>
<test name="MXRecordIsPresentTest" status="WARNING">
<nameserver name="ns1.epizy.com." status="WARNING">
<detail queryId="5">Test skipped for 'REFUSED' returncode</detail>
</nameserver>
<nameserver name="ns2.epizy.com." status="WARNING">
<detail queryId="6">Test skipped for 'REFUSED' returncode</detail>
</nameserver>
</test>
<test name="CNAMEHostTest" status="WARNING"/>
</tests>
<queries>
<query id="1">
<queryFor>venturecraft.it.</queryFor>
<type>SOA</type>
<destination>ns1.epizy.com./[198.251.86.154]</destination>
<result>
;; - HEADER - opcode: QUERY, status: REFUSED, id: 1558
;; flags: qr ; qd: 1 an: 0 au: 0 ad: 0
;; QUESTIONS:
;; venturecraft.it., type = SOA, class = IN
;; ANSWERS:
;; Message size: 33 bytes
venturecraft.it.
SOA
ns2.epizy.com./[198.251.86.152]
;; - HEADER - opcode: QUERY, status: REFUSED, id: 13452
;; flags: qr ; qd: 1 an: 0 au: 0 ad: 0
;; QUESTIONS:
;; venturecraft.it., type = SOA, class = IN
;; ANSWERS:
;; Message size: 33 bytes
venturecraft.it.
NS
ns1.epizy.com./[198.251.86.154]
;; - HEADER - opcode: QUERY, status: REFUSED, id: 5896
;; flags: qr ; qd: 1 an: 0 au: 0 ad: 0
;; QUESTIONS:
;; venturecraft.it., type = NS, class = IN
;; ANSWERS:
;; Message size: 33 bytes
venturecraft.it.
NS
ns2.epizy.com./[198.251.86.152]
;; - HEADER - opcode: QUERY, status: REFUSED, id: 1672
;; flags: qr ; qd: 1 an: 0 au: 0 ad: 0
;; QUESTIONS:
;; venturecraft.it., type = NS, class = IN
;; ANSWERS:
;; Message size: 33 bytes
venturecraft.it.
MX
ns1.epizy.com./[198.251.86.154]
;; - HEADER - opcode: QUERY, status: REFUSED, id: 26962
;; flags: qr ; qd: 1 an: 0 au: 0 ad: 0
;; QUESTIONS:
;; venturecraft.it., type = MX, class = IN
;; ANSWERS:
;; Message size: 33 bytes
venturecraft.it.
MX
ns2.epizy.com./[198.251.86.152]
;; - HEADER - opcode: QUERY, status: REFUSED, id: 55164
;; flags: qr ; qd: 1 an: 0 au: 0 ad: 0
;; QUESTIONS:
;; venturecraft.it., type = MX, class = IN
;; ANSWERS:
;; Message size: 33 bytes
ns1.epizy.com.
A
local resolver
;; - HEADER - opcode: QUERY, status: NOERROR, id: 55843
;; flags: qr rd ra ; qd: 1 an: 1 au: 0 ad: 0
;; QUESTIONS:
;; ns1.epizy.com., type = A, class = IN
;; ANSWERS:
ns1.epizy.com. 83176 IN A 198.251.86.154
;; Message size: 47 bytes
ns1.epizy.com.
AAAA
local resolver
;; - HEADER - opcode: QUERY, status: NOERROR, id: 15502
;; flags: qr rd ra ; qd: 1 an: 0 au: 1 ad: 0
;; QUESTIONS:
;; ns1.epizy.com., type = AAAA, class = IN
;; ANSWERS:
;; Message size: 75 bytes
ns2.epizy.com.
A
local resolver
;; - HEADER - opcode: QUERY, status: NOERROR, id: 45515
;; flags: qr rd ra ; qd: 1 an: 1 au: 0 ad: 0
;; QUESTIONS:
;; ns2.epizy.com., type = A, class = IN
;; ANSWERS:
ns2.epizy.com. 79516 IN A 198.251.86.152
;; Message size: 47 bytes
ns2.epizy.com.
AAAA
local resolver
;; - HEADER - opcode: QUERY, status: NOERROR, id: 28633
;; flags: qr rd ra ; qd: 1 an: 0 au: 1 ad: 0
;; QUESTIONS:
;; ns2.epizy.com., type = AAAA, class = IN
;; ANSWERS:
;; Message size: 79 bytes
</dnsValidator:result>
That output is expected. The .it registry servers do a bunch of checks to make sure that DNS records are provisioned for your domain on the new nameservers. That only happens on our end when the domain is added to an account, which is only possible after the nameservers have already changed. Hence the catch-22 described in the article that @Oxy linked to a few days ago:
You’re welcome to try to make it work. But I think it’s unlikely that the .it registry will make an exception for you to change the nameservers anyways, and I know we cannot make an exception for you to host your domain with us anyways.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.