O.K. and I showed you the Records… But, you still won’t tell me if I have to records to every single sub created…
O.K. You’re right. Thanks
If you want them to work you do.
If you want Virtualmin to manage your DNS records, you need to make your Virtualmin server the authoritative server for your zone(s). Right now, it is not.
1 Like
O.K. now you’re saying something. What tab is that under?..
Again, it is not a Virtualmin problem. It’s not in Virtualmin.
Glue records (the records that tell the world what the authoritative servers are for your zone) are configured at your domain registrar.
I’m sorry for wasting your time Joe, but I think I’m the only one here that only has two places to edit in my domain in Godaddy. 1. the NS 2. the Hostnames… Anyways… Have a great day.
Yes. The name servers. That’s where you set the authoritative name servers for your zone.
Correct. The NS goes to the DO Droplet… I only have issues with the hostname domain. Unrelated domains have no issues with subs or ssl…
$ whois intrelligent.net|grep Name
Domain Name: intrelligent.net
Name Server: NS1.DIGITALOCEAN.COM
Name Server: NS2.DIGITALOCEAN.COM
Name Server: NS3.DIGITALOCEAN.COM
Your name servers are Digital Ocean name servers. Virtualmin cannot manage those records, you’ll have to do it yourself.
If you want Virtualmin to manage your DNS records, you’ll have to set that to your Virtualmin server (and preferably the IP of your slave DNS server that is also managed by Virtualmin, though if your server has two IP addresses you could just have one DNS server…but most registrars will refuse to allow you to only have one name server address).
I’m not telling you what to do, whether to host your DNS at DO or on your Virtualmin system. I am just telling you how it works. Either way can work fine, but you need to understand the fundamental concepts of DNS (really, in either case, you need to understand the basics, or you’ll never make anything work and everything will seem mysterious and random, and you’ll blame things like the OS and Virtualmin for problems completely out of their control and that can’t be fixed by messing around with them).
I don’t know what you mean here, but I know that if Digital Ocean is hosting your DNS for a given domain, you will need to add records at Digital Ocean for every name you create in that domain. Right now DO is authoritative for intrelligent.net. If you want any subdomain of intrelligent.net to work, it needs an A record in DOs name servers.
This is fundamental DNS stuff, unrelated to Virtualmin. Virtualmin can manage DNS records, but they’ll only work if the world knows to ask your Virtualmin server for answers. Right now that is not the case. The world is asking DO, and DO doesn’t have the information it needs to answer.
1 Like
O.K. That makes sense, but please understand, I have not done anything differently than when I had Centos 7. The main host domain was also at Godaddy, and in godaddy, I set up the NS to Digitalocean. Once I installed the domain to the droplet, I also created the A records for my own custom NS, which are the ones I included in every other domain hosted in VM. And I’ve never had any issues creating subservers or servers on any of the domains, including the host domain. I was being sarcastic when I said that I must’ve had an unknown version of VM… In that set up, I’ve never had to go into DO in create a record for subdomains. Now, if there’s a feature in VM I need to turn on, then it’s a different ordeal. It’s been a while since I set up this control panel.
I don’t know what to tell you. The way DNS works has not changed since you installed a different operating system. If DO was authoritative for your zone(s), you had to configure your records there; Virtualmin can’t do it on Ubuntu and it couldn’t when you were running CentOS.
It may be that they have a wildcard option that you enabled for your domain, and it made all subdomains work (sort of, I don’t like wildcards in DNS, but it’s possible and means you’d only need one record for all sites on the same IP). Perhaps that’s the best option for you, if DO allows it.
Hi Joe, if you’re not too busy, I’d like to ask you one more question. I finally got this running smoothly, actually, I have Centos 8 and Ubuntu running on separate droplets smoothly. My question is, I’ve tried installing phpmyadmin in Ubuntu but, I got this error , and I can’t find the right solution for it. I tried enabling Msql anf I got this error. Thank you for your help.
This script cannot be installed, as this virtual server does not meet its requirements : phpMyAdmin requires a MySQL database, phpMyAdmin requires MySQL version 5.5 or later
`sudo: systemsctl: command not found
root@ns1:~# systemctl status mysql.service
● mysql.service - LSB: Start and stop the mysql database server daemon
Loaded: loaded (/etc/init.d/mysql; generated)
Active: failed (Result: exit-code) since Tue 2021-07-27 18:17:21 UTC; 41s >
Docs: man:systemd-sysv-generator(8)
Process: 83063 ExecStart=/etc/init.d/mysql start (code=exited, status=1/FAI>
Jul 27 18:16:50 ns1.lavision.miami systemd[1]: Starting LSB: Start and stop the>
Jul 27 18:16:50 ns1.lavision.miami mysql[83063]: * Starting MariaDB database s>
Jul 27 18:16:50 ns1.lavision.miami /etc/init.d/mysql[83110]: /etc/init.d/mysql:>
Jul 27 18:17:21 ns1.lavision.miami mysql[83063]: …fail!
Jul 27 18:17:21 ns1.lavision.miami systemd[1]: mysql.service: Control process e>
Jul 27 18:17:21 ns1.lavision.miami systemd[1]: mysql.service: Failed with resul>
Jul 27 18:17:21 ns1.lavision.miami systemd[1]: Failed to start LSB: Start and s>
root@ns1:~# systemctl start mysql.service
Job for mysql.service failed because the control process exited with error code.
See “systemctl status mysql.service” and “journalctl -xe” for details.
root@ns1:~# journalctl
– Logs begin at Tue 2021-07-27 15:59:03 UTC, end at Tue 2021-07-27 18:30:01 UT>
Jul 27 15:59:03 ubuntu kernel: Linux version 5.4.0-73-generic (buildd@lcy01-amd>
Jul 27 15:59:03 ubuntu kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73->
Jul 27 15:59:03 ubuntu kernel: KERNEL supported cpus:
Jul 27 15:59:03 ubuntu kernel: Intel GenuineIntel
Jul 27 15:59:03 ubuntu kernel: AMD AuthenticAMD
Jul 27 15:59:03 ubuntu kernel: Hygon HygonGenuine
Jul 27 15:59:03 ubuntu kernel: Centaur CentaurHauls
Jul 27 15:59:03 ubuntu kernel: zhaoxin Shanghai
Jul 27 15:59:03 ubuntu kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 fl>
Jul 27 15:59:03 ubuntu kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE re>
Jul 27 15:59:03 ubuntu kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX re>
Jul 27 15:59:03 ubuntu kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]>
Jul 27 15:59:03 ubuntu kernel: x86/fpu: Enabled xstate features 0x7, context si>
Jul 27 15:59:03 ubuntu kernel: BIOS-provided physical RAM map:
Jul 27 15:59:03 ubuntu kernel: BIOS-e820: [mem 0x0000000000000000-0x00000000000>
Jul 27 15:59:03 ubuntu kernel: BIOS-e820: [mem 0x000000000009fc00-0x00000000000>
Jul 27 15:59:03 ubuntu kernel: BIOS-e820: [mem 0x00000000000f0000-0x00000000000>
Jul 27 15:59:03 ubuntu kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000dff>
Jul 27 15:59:03 ubuntu kernel: BIOS-e820: [mem 0x00000000dfffb000-0x00000000dff>
Jul 27 15:59:03 ubuntu kernel: BIOS-e820: [mem 0x00000000feffc000-0x00000000fef>
Jul 27 15:59:03 ubuntu kernel: BIOS-e820: [mem 0x00000000fffc0000-0x00000000fff>
Jul 27 15:59:03 ubuntu kernel: BIOS-e820: [mem 0x0000000100000000-0x000000011ff>
lines 1-23…skipping…
– Logs begin at Tue 2021-07-27 15:59:03 UTC, end at Tue 2021-07-27 18:30:01 UTC. –
Jul 27 15:59:03 ubuntu kernel: Linux version 5.4.0-73-generic (buildd@lcy01-amd64-019) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #82-Ubuntu SMP Wed Apr 14 17:>
Jul 27 15:59:03 ubuntu kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic root=UUID=e17a595e-18f3-45e3-8f22-e0d1005fbae1 ro console=tty1 console=ttyS0
Jul 27 15:59:03 ubuntu kernel: KERNEL supported cpus:
Jul 27 15:59:03 ubuntu kernel: Intel GenuineIntel
Jul 27 15:59:03 ubuntu kernel: AMD AuthenticAMD
Jul 27 15:59:03 ubuntu kernel: Hygon HygonGenuine
Jul 27 15:59:03 ubuntu kernel: Centaur CentaurHauls
Jul 27 15:59:03 ubuntu kernel: zhaoxin Shanghai
Jul 27 15:59:03 ubuntu kernel: x86/fpu: Supporting XSAVE feature 0x001: ‘x87 floating point registers’
Jul 27 15:59:03 ubuntu kernel: x86/fpu: Supporting XSAVE feature 0x002: ‘SSE registers’
Jul 27 15:59:03 ubuntu kernel: x86/fpu: Supporting XSAVE feature 0x004: ‘AVX registers’
Jul 27 15:59:03 ubuntu kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
Jul 27 15:59:03 ubuntu kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using ‘standard’ format.
Jul 27 15:59:03 ubuntu kernel: BIOS-provided physical RAM map:
Jul 27 15:59:03 ubuntu kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable
Jul 27 15:59:03 ubuntu kernel: BIOS-e820: [mem 0x000000000009fc00-0x000000000009ffff] reserved
Jul 27 15:59:03 ubuntu kernel: BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff] reserved
Jul 27 15:59:03 ubuntu kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000dfffafff] usable
Jul 27 15:59:03 ubuntu kernel: BIOS-e820: [mem 0x00000000dfffb000-0x00000000dfffffff] reserved
Jul 27 15:59:03 ubuntu kernel: BIOS-e820: [mem 0x00000000feffc000-0x00000000feffffff] reserved
Jul 27 15:59:03 ubuntu kernel: BIOS-e820: [mem 0x00000000fffc0000-0x00000000ffffffff] reserved
Jul 27 15:59:03 ubuntu kernel: BIOS-e820: [mem 0x0000000100000000-0x000000011fffffff] usable
Jul 27 15:59:03 ubuntu kernel: NX (Execute Disable) protection: active
Jul 27 15:59:03 ubuntu kernel: SMBIOS 2.4 present.
Jul 27 15:59:03 ubuntu kernel: DMI: DigitalOcean Droplet, BIOS 20171212 12/12/2017
Jul 27 15:59:03 ubuntu kernel: Hypervisor detected: KVM
Jul 27 15:59:03 ubuntu kernel: kvm-clock: Using msrs 4b564d01 and 4b564d00
Jul 27 15:59:03 ubuntu kernel: kvm-clock: cpu 0, msr 6f601001, primary cpu clock
Jul 27 15:59:03 ubuntu kernel: kvm-clock: using sched offset of 1792692308 cycles
Jul 27 15:59:03 ubuntu kernel: clocksource: kvm-clock: mask: 0xffffffffffffffff max_cycles: 0x1cd42e4dffb, max_idle_ns: 881590591483 ns
Jul 27 15:59:03 ubuntu kernel: tsc: Detected 2294.592 MHz processor
Jul 27 15:59:03 ubuntu kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jul 27 15:59:03 ubuntu kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
Jul 27 15:59:03 ubuntu kernel: last_pfn = 0x120000 max_arch_pfn = 0x400000000
Jul 27 15:59:03 ubuntu kernel: MTRR default type: write-back
Jul 27 15:59:03 ubuntu kernel: MTRR fixed ranges enabled:
Jul 27 15:59:03 ubuntu kernel: 00000-9FFFF write-back
Jul 27 15:59:03 ubuntu kernel: A0000-BFFFF uncachable
Jul 27 15:59:03 ubuntu kernel: C0000-FFFFF write-protect
Jul 27 15:59:03 ubuntu kernel: MTRR variable ranges enabled:
Jul 27 15:59:03 ubuntu kernel: 0 base 00E0000000 mask FFE0000000 uncachable
Jul 27 15:59:03 ubuntu kernel: 1 disabled
lines 1-43
Please open new topics for new problems.
Also, I just answered an identical question yesterday or the day before. Should be easy to find with a forum search.
O.K. thank you.
This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.