hi all, I was using vesta since two years but the project is dead. I tried vesta fork hestia but I faced many problems than I want to try ispconfig. I followed this tutorial, https://www.howtoforge.com/tutorial...sl-pureftpd-bind-postfix-doveot-and-ispconfig and I didn't faced any problems. ispconfig web panel is working without any problem. I've a domain which held by godaddy. when I was using vesta cp, my vps was ubuntu 16.04 and I decided to jump 20.04 for clean install. so my vps ip address changed. I logined godaddy and change my domain dns ns name ip address with the new one. then I added my domain to isp config and I added dns-zone about this domain. it's been 12 hours passed since I added my domain and dns-zone but still no answer from dns servers. I noticed that in web domain properties ip address is shown * only and I couldn't figured out how I can write there a real ip address? Did I missed something?
Are you using ISPConfig for serving the DNS zone of your domain, or do you use the nameservers of GoDaddy?
I'm using ISPConfig for serving the DNS zone of my domain. godaddy domain dns settings are like this below, this setup was working serving dns-zone with vesta cp.
See https://intodns.com/cembol.com to check your DNS issues. Also, you should have 2 separate nameservers on separate connections, for redundancy.
Yes, but both nameservers are on the same IP, so they are most likely the same server and surely on the same connection. Please run the script from https://www.howtoforge.com/community/threads/please-read-before-posting.58408/ and share the output.
Code: ##### SERVER ##### IP-address (as per hostname): ***.***.***.*** [WARN] could not determine server's ip address by ifconfig [INFO] OS version is Ubuntu 20.04.2 LTS [INFO] uptime: 02:28:47 up 7:18, 1 user, load average: 0.00, 0.00, 0.00 [INFO] memory: total used free shared buff/cache available Mem: 981Mi 588Mi 80Mi 11Mi 312Mi 229Mi Swap: 2.2Gi 1.1Gi 1.1Gi [INFO] systemd failed services status: UNIT LOAD ACTIVE SUB DESCRIPTION â— snap.lxd.activate.service loaded failed failed Service for snap application lxd.activate LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB = The low-level unit activation state, values depend on unit type. 1 loaded units listed. [INFO] ISPConfig is installed. ##### ISPCONFIG ##### ISPConfig version is 3.2.2 ##### VERSION CHECK ##### [INFO] php (cli) version is 7.4.3 ##### PORT CHECK ##### ##### MAIL SERVER CHECK ##### ##### RUNNING SERVER PROCESSES ##### [INFO] I found the following web server(s): Apache 2 (PID 156130) [INFO] I found the following mail server(s): Postfix (PID 151215) [INFO] I found the following pop3 server(s): Dovecot (PID 705) [INFO] I found the following imap server(s): Dovecot (PID 705) [INFO] I found the following ftp server(s): PureFTP (PID 1100)
Your nameserver seems to work. Are you sure the zone is created on your ISPConfig server, it is activated, and there are no errors? It seems you are missing the A records for ns1 and ns2, which would cause BIND to fail loading your zone.
yes, you are right. there is A records are missing but dns-zone wizard is automaticly adding this A record ns1.xyz.com but it should be written only ns1 in A record. thank you very much for your help and patience.
Records in a BIND zone file can use the short syntax e.g. 'ns1' or the long syntax, e.g. 'ns1.yourdomain.tld.' but when you use the long syntax, then you must ensure that the domain you enter ends with a dot as shown in my example. So using the long syntax is perfectly fine, as long as you enter the domain name correctly with a dot at the end.
so the zone you're trying to get working on ispconfig is cemxxx.com, and the nameservers are ns1.cemxxx.com and ns2.cemxxx.com in that case, apart from having those nameservers set for the domain with your registrar, you also need: 1. A records for those nameservers in your cemxxx.com zone. 2. NS records for those nameservers in your cemxxx.com zone. 3. glue records for your nameservers configured with your registrar, ie, they need to know the ip's of your nameservers, not just the fqdn's. it sounds like 1 and 2 may already be done. but even with everything else correct, when using nameservers within the same zone they are the authority for, unless you have item 3 configured, there is no way for anything on the internet to locate the actual ip's for your nameservers, so none of it will work.
