The domain visiba.com is registered with Cloudflare and uses the Cloudflare nameservers. We have set up DNS records for ns31 and ns32 to point to the correct server IP addresses. Another domain labcompass.com is using the ns31 and ns32 nameservers, but somehow the wrong (read: previous) IP addresses of ns31 and ns32 are returned. All other domains using ns31 and ns32 are correct though.
What steps have you taken to resolve the issue?
Verified the DNS zone of the domain
Contacted cPanel support
Contacted the domain registrar
What feature, service or problem is this related to?
Everything seems to work ok. If the wrong IP address is returned for labcompass.com (not on Cloudflare) you’ll need to check in your two nameservers.
dig +short ns31.visiba.com
107.173.236.146
dig +short ns32.visiba.com
88.218.76.201
dig +trace +nodnssec labcompass.com
; <<>> DiG 9.10.6 <<>> +trace +nodnssec labcompass.com
;; global options: +cmd
. 511729 IN NS a.root-servers.net.
....
. 511729 IN NS m.root-servers.net.
;; Received 239 bytes from 127.0.2.2#53(127.0.2.2) in 0 ms
com. 172800 IN NS j.gtld-servers.net.
....
com. 172800 IN NS m.gtld-servers.net.
;; Received 839 bytes from 2001:7fd::1#53(k.root-servers.net) in 66 ms
labcompass.com. 172800 IN NS ns31.visiba.com.
labcompass.com. 172800 IN NS ns32.visiba.com.
;; Received 120 bytes from 2001:503:83eb::30#53(c.gtld-servers.net) in 24 ms
labcompass.com. 14400 IN A 94.237.44.28
;; Received 59 bytes from 107.173.236.146#53(ns31.visiba.com) in 108 ms
Those errors all relate to how you have set up the zone for labcompass.com in your 2 nameservers. None of those relate to your Cloudflare settings, those are ok.
The lagging IP addresses may due to the long TTL at the com root servers…
Nameserver records returned by the parent servers are:
ns31.visiba.com. ['107.191.109.209'] [TTL=172800]
ns32.visiba.com. ['81.4.110.103'] [TTL=172800]
**a.gtld-servers.net was kind enough to give us that information.**
Sorry to get back to this, but if the .com root servers are not able to pick up the correct IP address of ns31 and ns32, doesn’t that indicate an issue somewhere at Cloudflare?
labcompass does not have glue records. Glue records would mean that nameservers ns1.labcompass and ns2.labcompass.com are registered but that’s not the case here.
We are talking about the nameservers ns31 and ns32 which are managed by Cloudflare.
These are glue records. They are not necessary as the nameservers are from a different zone, but they are set in this case.
You can try and force an update by changing the nameservers at the registrar to say ns33 and ns34 (create them in Cloudflare to point to the same IP addresses as ns31 and ns32). Then wait for them to change at the registry, then set them back to ns31 and ns32 and the registrar may reset the IP addresses automatically.
Otherwise you need to ask your registrar to fix it for you, either to remove the glue or update it.
Do not try… CF simply does not support creating child name servers. I ended up creating support ticket, waited couple days for ticket to be escalated to network or upper level, then they “manually” created nameservers. These took 4-5 days. They also confirmed that is not possible from user control panel.
So I transfered my domain to an other registrar.
I think as this is .com to .com the nameservers nsX.visiba.com need to be registered. I assume you’d have to raise a Cloudflare registrar ticket for visiba.com for that.