Use local DNS resolver instead of quad9 that wasn't working very well
This commit is contained in:
parent
65ca536b3b
commit
fe3e529cf6
4 changed files with 6 additions and 4 deletions
|
@ -5,6 +5,7 @@
|
|||
address = "192.168.1.254";
|
||||
interface = "eno1";
|
||||
};
|
||||
networking.nameservers = [ "192.168.1.254" ];
|
||||
|
||||
deuxfleurs.site_name = "neptune";
|
||||
}
|
||||
|
|
|
@ -5,6 +5,7 @@
|
|||
address = "192.168.1.254";
|
||||
interface = "eno1";
|
||||
};
|
||||
networking.nameservers = [ "192.168.1.254" ];
|
||||
|
||||
deuxfleurs.site_name = "neptune";
|
||||
|
||||
|
|
|
@ -23,10 +23,6 @@
|
|||
# Per-interface useDHCP will be mandatory in the future, so this generated config
|
||||
# replicates the default behaviour.
|
||||
networking.useDHCP = false;
|
||||
# networking.wireless.enable = true; # Enables wireless support via wpa_supplicant.
|
||||
|
||||
# Networking configuration (static IPs for each node is defined in node/*.nix)
|
||||
networking.nameservers = [ "9.9.9.9" ];
|
||||
|
||||
# Set your time zone.
|
||||
time.timeZone = "Europe/Paris";
|
||||
|
|
|
@ -8,3 +8,7 @@
|
|||
192.168.1.22 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIHXyY9yZdq/VYpg3K1plBzFvim41tWlu+Dmov3BNSm39
|
||||
192.168.1.21 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAILYIRbHPU1w1xWRpm2+u3QsXOKfMjv1EXrpYbHT+epds
|
||||
192.168.1.23 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAICNRilSqrgqdZlLdhN2eOY5ZMbzqpeqAdIf6QuChhXU+
|
||||
10.42.2.2 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIORTjNdFaDbhto8kuMPB3hYkfnzdnceZVIELApUe5PPL
|
||||
10.42.2.22 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIHXyY9yZdq/VYpg3K1plBzFvim41tWlu+Dmov3BNSm39
|
||||
10.42.2.21 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAILYIRbHPU1w1xWRpm2+u3QsXOKfMjv1EXrpYbHT+epds
|
||||
10.42.2.23 ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAICNRilSqrgqdZlLdhN2eOY5ZMbzqpeqAdIf6QuChhXU+
|
||||
|
|
Loading…
Reference in a new issue