fix(dns): use parse-resolv-conf (#5)

Co-authored-by: Robert Schönthal <[email protected]>

Author: digitalkaoz

.github/workflows/test.yaml

@@ -187,18 +187,6 @@ jobs:
           -e SERVER_COUNT=foo \
           "${{ env.IMAGE_NAME }}"
 
-      - name: Run Docker Image with Invalid DNS Resolver
-        timeout-minutes: 1
-        id: test-validation-dns-resolver
-        continue-on-error: true
-        run: |
-          ! docker run \
-          -e STRATEGY=PERCENTAGE \
-          -e OLD_DOMAIN=haproxy.com:443 -e NEW_DOMAIN=apache.org:443 \
-          -e COOKIE_PERCENTAGE_NAME=my_app \
-          -e DNS_RESOLVER=foo \
-          "${{ env.IMAGE_NAME }}"
-
       - name: Check for failures
         if: always()
         env:

README.md

@@ -41,10 +41,6 @@ how much traffic should be routed to the old application
 ### PERCENTAGE_NEW
 how much traffic should be routed to the new application
 
-### DNS_RESOLVER (optional, default=1.1.1.1)
-The DNS resolver to use for resolving the domain names to IP addresses.
-If you want to reroute internal traffic you might want to change that.
-
 ### SERVER_COUNT (optional, default=5)
 as we are using DNS Resolver we try to create a server for each IP address we get back from the DNS query. 
 This is the maximum amount of servers we will create. 

haproxy.cfg

@@ -11,7 +11,6 @@ global
   presetenv PERCENTAGE_NEW "0"
   presetenv PERCENTAGE_OLD "100"
   presetenv SERVER_COUNT "5"
-  presetenv DNS_RESOLVER "1.1.1.1:53"
 
   # we source them from the environment here to actually typecheck them
   set-var proc.percentage_new int("${PERCENTAGE_NEW}")
@@ -81,5 +80,5 @@ backend cookie_strategy
   server-template default_new "$SERVER_COUNT" "$NEW_DOMAIN"
 
 resolvers dns
-  nameserver default "$DNS_RESOLVER"
+  parse-resolv-conf
   accepted_payload_size 8192