Migrating from SME 9.2 - nethserver-hotsync

@schulzstefan

As to stability of Proxmox servers, here’s a typical sample:

HW: Thomas Krenn / Supermicro, 8 Cores, 64 GB RAM, about 7 years old…

Not bad, for a Server set up in March 2020… :slight_smile:
The UPS came a little later, that’s why a reboot was needed…

:slight_smile:

My 2 cents
Andy

1 Like

@Andy_Wismer

I’m still struggling with the virtual NS. Looking in the messages brings me to a couple of questions. Let’s start with an easy one. Do you have a NS in a VM as a backup-server for a real hardware NS running? If so, how is the VM configured?

For mine it looks like this, where 192.168.42.200 is the proxmox pve and 205 is the VM NS backup-server:

and

DNS are 1.1.1.1 and 9.9.9.9

After a reboot of the VM:

Why is there a redirect to GOOGLE?

edit:

network config in pve looks like this, while 192.168.42.1 is the OPNSense:

@schulzstefan

Hi

Could you show a screenshot of how that Nethserver VM has (sees) it’s own network?

As to the google redirect: you are using Google as DNS…

Why actually? With OPNsense and NethServer you do not need any other DNS Servers…
Most people are under the misconception that a DNS Server needs a DNS. Maybe, but rarely. Root Server A has had the same IP for years now, that’s all a DNS server needs to know to resolve the whole world. And Root Server A is usually hardcoded into the code…

At home neither my OPNsense nor my NethServer uses any Google, Provider or any foreign DNS.
OPNsense is Primary-DNS, NethServer is 2nd DNS. My PI-Hole only uses those two DNS.

Bildschirmfoto 2021-01-23 um 12.33.40

:slight_smile:

Gruss
Andy

How to do that best?

No google DNS in the whole network. I’ll configure the DNS in the VM NS to the OPNSense and the real NS. We’ll see.

Are these (from your NS Screenshot) not Google IPs?

Bildschirmfoto 2021-01-23 um 12.40.10

Screenshot from Browser, this page:

No.

But changing the DNS in the VM leeds to this:

.1 is the OPNSense and .10 is the real NS.

edit:

.10 is working as DNS

DNS:

Setting up your own DNS is actually easy, if you know the ropes.
If you need help in this, I’m not known as a DNS crack for the last 20 years for nothing… :slight_smile:

My 2 cents
Andy

Those DNS needs to be accessible, running - and also have some entries in them…
:slight_smile:

Do they work eg for your PC?

Do you have your (at least the important ones) internal hosts entered in there?
(OPNsense, Proxmox, Neth…)

This are the DNS in the real server:
Bildschirmfoto vom 2021-01-23 12-46-49
working flawless.

I have one (pi-hole) in my home-network. I don’t want to have it in my business.

A PI-Hole is NOT a DNS Server in itself. To use it in a business is possible, but you NEED to know your DNS and AD well!

I do have about 10 clients happy using a PI-Hole, they also know how to temporarily deactivate it, if eg marketing has problems checking up prices…

My 2 cents
Andy

In a company environment, even at home, only using External DNS makes things slower, or even impossible.

Like using AD. Google DNS or your local Provider’s DNS can’t tell you the IP of your AD-Server, or any internal Server or NAS.

Just an example…

My 2 cents
Andy

After changing the DNS to the IP of the real NS:

I don’t get it.

I know. The pi-hole is configured with unbound…

But let’s focus on the question how has a NS running as a VM in proxmox has to be configured to run with hotsync?

In an environment with NethServer, it’s best to deactivate IPv6 on all possible devices.

NethServer does not yet support IPv6 (At all! But will come…). I switched off IPv6 in my OPNsense, Proxmox does not use IPv6, and also my NAS and PCs have IPv6 deactivated.

That could be part of the problem!

Note: Centos underneath CAN do IPv6 - but NOT NethServer.

It’s deactivated - in the whole network, even in every win-client.

Me too…

I need to grab some lunch, will be back in 45 mins - 1 hour…

no prob.

is this o.k.?

coming right from the install…