Control Web Panel
WebPanel => CentOS 7 Problems => Topic started by: asifashi on August 05, 2019, 03:49:12 AM
-
I have set up the private nameserver for CWP and also registered nameserver from Namecheap. I have added these NS to CWP panel and still, it's not resolved.
https://imgur.com/KNkFWdn
https://imgur.com/R29cXqs
My private NS are
ns1.worldthenews.com
ns2.worldthenews.com
and both are point to my server IP
But in the My CWP panel, both are still not resolved
ns1.worldthenews.com resolves to
ns2.worldthenews.com resolves to
For kind information, I was registered these NS 2 day ago
I am also creat new user account and add the same domain as the main domain and install WordPress and unable to access my website.
-
As you have not added an A record into DNS file of your website, it will not propagate.
Add two A records by using Edit Records option in DNS file of said website in CWP.
-
Thanks, My issue is resolved
-
I am having the same issue, even got a new vps and glued domain and everything. Where are these zones found? I have tried adding my domain and says domain exists. CAN SOMEONE PLEASE HELP ME! I have been struggling with this for weeks now.
-
From CWP. /admin/index.php?module=dns_list_zones
You should have a zone ns1.(yourdomain) and ns2.(yourdomain) zones. IF you don't you need to create them with the following
; Zone file for ns1.(yourdomain)
$TTL 14400
ns1.(yourdomain). 86400 IN SOA ns1.(yourdomain). info.centos-webpanel.com. (
2013071600 ;serial, todays date+todays
86400 ;refresh, seconds
7200 ;retry, seconds
3600000 ;expire, seconds
86400 ;minimum, seconds
)
ns1.(yourdomain). 86400 IN NS ns1.(yourdomain).
ns1.(yourdomain). 86400 IN NS ns2.(yourdomain).
ns1.(yourdomain). 14400 IN A (yourip)
; Zone file for ns2.(yourdomain)
$TTL 14400
ns2.(yourdomain). 86400 IN SOA ns1.(yourdomain). info.centos-webpanel.com. (
2013071600 ;serial, todays date+todays
86400 ;refresh, seconds
7200 ;retry, seconds
3600000 ;expire, seconds
86400 ;minimum, seconds
)
ns2.(yourdomain). 86400 IN NS ns1.(yourdomain).
ns2.(yourdomain). 86400 IN NS ns2.(yourdomain).
ns2.(yourdomain). 14400 IN A (yourip)
-
When I edited the server ips, those were created automatically. I just checked and they are there. I really do not know what to do at this point. I have had several people look into it and they cannot seem to find an issue. I contacted my domain registrar and they have confirmed the glu records are correct. I had used own nameservers on a previous VPS, but left that provider because they overcharged too much to manage and my servers kept going down. This has been an issue for almost a month now.
-
What is your domain name and nameservers. Perhaps we can find the issue.
-
Right now I am using domain registrar servers. My domain is rosalinebettencourt.com. I would LOVE to have this resolved.
-
First you have to have the DNS registered (aka glue records created), this is pretty simple with Namecheap & GoDaddy.
Here is an article how to do it at GoDaddy: https://my.starburstservices.com/index.php?fuse=knowledgebase&controller=articles&view=article&articleId=16
Thought I had one for Namecheap, guess I have to add that to my to do list now.
But registrar's like Cloudflare don't offer it, unless you pay for one of their higher level of service.
And I'm not sure how other registrar's may or may not handle it.
Once they are registered, and point to the corresponding IP's.
It's just a matter of creating the A records, and the PTR record at your bandwidth upstream.
-
I already have the domains glued to the IP, what are the PTR records? I have never heard this term before, sorry.
-
When I try to test your DNS server, I get a connection timeout. Make sure port 53 is open on your firewall and bind/named is running on the server.
-
Here is my firewall
https://imgur.com/a/Pl0N7Q4
https://imgur.com/dlxzbax
-
How about CSF firewall, and make sure named is running
-
Your CSF config looks like Default, which is good.
Tried to open Port 53/UDP on the other firewall.
http://leafdns.com/ and https://dnschecker.org/all-dns-records-of-domain.php are good tools.
Most of your domain comes back to hostinger.in & dns-parking.com
The main WHOIS is showing GoDaddy just has the domain name 'parked'.
So I'm thinking your ns are not created or glued anywhere.
As when they are, you need to have 2 A records created also with ns1.worldthenews.com & ns2.worldthenews.com, which currently also do not exist.
-
How about CSF firewall, and make sure named is running
How do I see named? And which of these csf am I checking:
https://imgur.com/a/F0DWptk
Where do I find named?
-
Your CSF config looks like Default, which is good.
Tried to open Port 53/UDP on the other firewall.
http://leafdns.com/ and https://dnschecker.org/all-dns-records-of-domain.php are good tools.
Most of your domain comes back to hostinger.in & dns-parking.com
The main WHOIS is showing GoDaddy just has the domain name 'parked'.
So I'm thinking your ns are not created or glued anywhere.
As when they are, you need to have 2 A records created also with ns1.worldthenews.com & ns2.worldthenews.com, which currently also do not exist.
I used leafdns and that is how I noticed that the nameservers were not working, but at the time they also confirmed the IP were glued to that ip but not resolved to them (if I am understanding the tables correctly).
The dns-parking website seems down. I did use the dnschecker domain one, but do not seem to see what you are seeing (but I am also currently not using my nameservers since they are not functioning and I need access to my website, I am using on another website):
https://dnschecker.org/all-dns-records-of-domain.php?query=rosalinebettencourt.com&rtype=ALL&dns=google
Here is the website that is pointing to target and desired nameservers:
pandiderpanda.com (which show ns2 as the old ip address still)
Here is the glu, which the domain registrar has confirmed are glued:
https://imgur.com/z6We7SH
I added an additional IP address, see if this is fixed. Perhaps my registrar has changed their policy on having same ips. I am not sure how this would affect, since it worked on my old VPS.
-
It resolved! I do not know if it was switching off of Ionos or because I added a secondary IP to my new VPS. Either way, it is now resolving.
-
I was looking up the domain name in you original post (worldthenews.com).
Glad all if working, but DNS does need UDP & TCP port 53 open.