Default DNS server resolves to 127.0.1.1

Virtualmin
1

This is on a blank install, nothing was modified anywhere.

Linux 6.1.0-32-cloud-amd64 on x86_64
Debian Linux 12
Virtualmin version 7.40.0
Webmin version 2.501
Usermin version 2.400

I tested the install on a clean Debian 11 , the ports error is gone but this one persists:

BIND DNS server is installed, however, the default primary DNS server resolves to IP address 127.0.1.1 which does not resolve to an IP address of a network interface on this system.

Probably he edited etc/hosts to remove the 127.0.1.1 reference that makes BIND not working properly

The entire BIND/DNS/SSL generation complex is broken in this last version, at least on Debian

Works fine out of the box in 7.30 versions but not in 7.40

2

What has that got to do with 2 instances of the same port being defined in ports.conf, please elaborate

3

My new VPS DNS was not working despite doing all the usual steps (new install, debian 12, changed ip’s for nameservers at registrar, etc)

BIND check returned this
BIND DNS server is installed, however, the default primary DNS server resolves to IP address 127.0.1.1 which does not resolve to an IP address of a network interface on this system.

suggested fix was to edit etc/hosts file

in the host file there was a 127.0.1.1 vpshost line and another line real-ip vpshost, deleted the 1st one with 127.0.1.1

restarted server then i got that error too, multiple listeners (80 was on 3 lines, etc)

didnt modified that too because for a new instalation (7.40.0) there shouldnt be so many issues

i will wait for a stable release

ADD: and before anyone gets upstet, between Sept 1 and Sept 7 i installed 12 VPS servers with Debian 12 and Virtualmin 7.30.8 and all of them worked perfectly, with the same steps (install Virtualmin, change IP and registrar, add domains on VPS)

yesterday was the 1st day whe 7.40.0 was default and didnt worked at all

5

i told you the steps to get that error, doesnt help you but it helps the devs

6

That can not cause that error note the point ‘syntax error at line 3 in ports.conf’ is the error and nothing else, explain how altering the hosts file could stop apache from starting ?

7

Yet, I also see this warning. @Jamie, do you remember this discussion on GitHub? Just checking—what do we do if a hostname is set to an internal non-resolvable externally name? I think the current warning is actually correct, right?

@Evcro You can configure correct “Primary DNS server hostname” on “System Settings ⇾ Server Templates: Edit Server Template” page.

8

Yes it is correct - Virtualmin needs an externally resolvable hostname to use in NS records.

9

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.