new.IP/whm going to cprapid.com:2087 why? and worst: my DNS no load

000

Well-Known Member
Jun 3, 2008
317
14
68
hello

I rent new.IP + new.VPS

my OldDomain load fine by years

but this week I config in registrar:

ns1.OldDomain -> new.IP
ns2.OldDomain -> new.IP

also we config:

OldDomain with:

ns1.OldDomain
ns2.OldDomain

we are waiting "propagation DNS", but
now is more of 5 days with OldDomain totally offline

somw idea about what is bad?

in the past we do this process more of 30 times
and never we have troubles

only now we have this strangle behaviour of:

1// new.IP/whm going to cprapid.com:2087 (and all load fine)
2// DNS in registrar = ok
3// DNS in domain = ok
4// domain OFF LINE but server = ok

how we can fixed this ?


Thanks
 

andrew.n

Well-Known Member
Jun 9, 2020
519
138
43
EU
cPanel Access Level
Root Administrator
Have you changed the IP address of the name servers registered at the domain registrar? If not then this could be a problem. Depends on the domain registrar its called "private nameservers" or "private hosts".
 

000

Well-Known Member
Jun 3, 2008
317
14
68
Have you changed the IP address of the name servers registered at the domain registrar? If not then this could be a problem. Depends on the domain registrar its called "private nameservers" or "private hosts".
Thanks @andrew.n

sure, we create DNS in registrar:
...

but this week I config in registrar:

ns1.OldDomain -> new.IP
ns2.OldDomain -> new.IP

also we config:

OldDomain with:

ns1.OldDomain
ns2.OldDomain
 

cPRex

Jurassic Moderator
Staff member
Oct 19, 2014
4,831
597
273
cPanel Access Level
Root Administrator
As far as the hostname, that is just the default hostname we assign so users can access their WHM login securely when visiting the server for the first time. You can find more details on that here:


I'm not sure about the other DNS issues, but it does sound like there is a problem. Since you have the records set up properly, you may want to check and see if port 53 is open on your server to serve those records. You can do that with either of the following commands:

Code:
telnet x.x.x.x 53
where "x.x.x.x" is the IP address of the new machine, or you can do this:

Code:
dig domain.com @x.x.x.x
If both of those don't work, that would indicate the port is closed so the DNS records will not work properly on that new system.