[PATCH] REGTESTS: Don't try to use real nameservers for testcases

[Christian Ruppert]

Another one, also fixing issues in restriced / sandboxed test 
environments.

--
Regards,
Christian RuppertFrom 7af426f661d2789fe3020ef87280407a1446dd88 Mon Sep 17 00:00:00 2001
From: Christian Ruppert <id...@qasl.de>
Date: Mon, 11 May 2026 19:48:23 +0200
Subject: [PATCH] REGTESTS: Don't try to use real nameservers for testcases
The test doesn't need a real nameserver and in a isolated, restricted
test environment it might not be able to reach one at all, like with a
network sandbox. So lets just use 127.0.0.1:53. Even if there is none,
that's not a problem for this particular test.

Signed-off-by: Christian Ruppert <id...@qasl.de>
---
 reg-tests/server/cli_set_fqdn.vtc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/reg-tests/server/cli_set_fqdn.vtc b/reg-tests/server/cli_set_fqdn.vtc
index 72695769f..fae53fff0 100644
--- a/reg-tests/server/cli_set_fqdn.vtc
+++ b/reg-tests/server/cli_set_fqdn.vtc
@@ -42,7 +42,7 @@ haproxy h2 -conf {
         timeout server  "${HAPROXY_TEST_TIMEOUT-5s}"
 
     resolvers systemdns
-        parse-resolv-conf
+        nameserver dns1 127.0.0.1:53
 
     frontend myfrontend
         bind "fd@${my_fe}"
-- 
2.53.0