Don't force bind DNS to IPv6, if it's disabled

[rwjack]

What happened:

What did you expect to happen?:
Portmaster to have a switch not to use IPv6, because it probably can't read my mind, that I'm the one that disabled IPv6.

How did you reproduce it?:
I disabled IPv6 on my Desktop's network interface.

[github-actions]

Greetings and welcome to our community! As this is the first issue you opened here, we wanted to share some useful infos with you:

• 🗣️ Our community on Discord is super helpful and active. We also have an AI-enabled support bot that knows Portmaster well and can give you immediate help.
• 📖 The Wiki answers all common questions and has many important details. If you can't find an answer there, let us know, so we can add anything that's missing.

[github-actions]

Hey @rwjack, thank you for raising this issue with us.

After a first review we noticed that we will require the Debug Info for further investigation. However, you haven't supplied any Debug Info in your report.

Please collect Debug Info from Portmaster while the reported issue is present.

[dhaavi]

You did not provide a lot of info here, but the most probable cause is that you haven't fully disabled IPv6. Please disable IPv6 globally and/or on all network adapters. Then, restart Portmaster.

[rwjack]

I can't believe I forgot to check if IPv6 was enabled before I opened this ticket. Previously I had disabled it using this playbook:

---
- name: Disable ipv6 on Debian hosts
  hosts: all

  tasks:
    - name: Disable ipv6 now
      shell:
        cmd: >
          sysctl -w net.ipv6.conf.all.disable_ipv6=1 &&
          sysctl -w net.ipv6.conf.default.disable_ipv6=1 &&
          sysctl -w net.ipv6.conf.lo.disable_ipv6=1

    - name: Modify /etc/sysctl.conf
      blockinfile:
        path: /etc/sysctl.conf
        block: |
          net.ipv6.conf.all.disable_ipv6=1
          net.ipv6.conf.default.disable_ipv6=1
          net.ipv6.conf.lo.disable_ipv6=1

Although it must have re-enabled itself after an update or something...

Ran the playbook again, restarted portmaster, no warning now.
Guess we can close this one out, thank you.