fix: force using our nameservers
Some checks failed
Build_Deploy / build (push) Successful in 2m1s
Build_Deploy / linter (push) Successful in 5m12s
Build_Deploy / deploy_dns (push) Successful in 2m47s
Build_Deploy / deploy_active (active-core) (push) Successful in 17m10s
Build_Deploy / deploy_active (active) (push) Successful in 3m35s
Build_Deploy / deploy_active (active-ext) (push) Failing after 3m20s
Some checks failed
Build_Deploy / build (push) Successful in 2m1s
Build_Deploy / linter (push) Successful in 5m12s
Build_Deploy / deploy_dns (push) Successful in 2m47s
Build_Deploy / deploy_active (active-core) (push) Successful in 17m10s
Build_Deploy / deploy_active (active) (push) Successful in 3m35s
Build_Deploy / deploy_active (active-ext) (push) Failing after 3m20s
This commit is contained in:
parent
8a8a1a3c7f
commit
a2000ec6da
1 changed files with 2 additions and 0 deletions
|
@ -104,6 +104,8 @@ in {
|
|||
# every sever needs to be accessable over ssh for admin use at least
|
||||
firewall.allowedTCPPorts = [22];
|
||||
|
||||
resolvconf.useLocalResolver = false;
|
||||
resolvconf.extraConfig = "name_servers='193.1.99.120 193.1.99.109'";
|
||||
# explisitly stating this is good
|
||||
defaultGateway = {
|
||||
address = "193.1.99.65";
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue