1. Forum
  2. Newsgroups
  3. comp.os.linux.networking

  • DNS issues in private network

    From Kyonshi@gmkeros@gmail.com to comp.os.linux.networking on Fri Apr 12 15:05:00 2024
    From Newsgroup: comp.os.linux.networking

    I have a rather new, minimal installation of Rocky Linux 9 (so
    effectively RHEL 9) and have a pihole running on another machine in my
    private network. I have changed the nameservers on the Rocky Linux
    machine to resolve via the pihole DNS on the local network.
    All of a sudden the DNS stops resolving.

    ; <<>> DiG 9.16.23-RH <<>> google.com
    ;; global options: +cmd
    ;; connection timed out; no servers could be reached

    Network connection still is there, only DNS resolution is affected. I
    can ping the other machine. The pihole is running and it is resolving
    for other machines, it just doesn't seem to work on this particular
    machine.

    Anyone got an idea what the issue might be?

    --- Synchronet 3.20a-Linux NewsLink 1.114
  • From Marco Moock@mm+usenet-es@dorfdsl.de to comp.os.linux.networking on Sat Apr 13 21:00:17 2024
    From Newsgroup: comp.os.linux.networking

    On 12.04.2024 um 15:05 Uhr Kyonshi wrote:

    Anyone got an idea what the issue might be?

    Rund resolvectl and post the output here.
    --
    kind regards
    Marco

    Send spam to 1712927100muell@cartoonies.org

    --- Synchronet 3.20a-Linux NewsLink 1.114
  • From Carlos E.R.@robin_listas@es.invalid to comp.os.linux.networking on Sat Apr 13 22:32:45 2024
    From Newsgroup: comp.os.linux.networking

    On 2024-04-12 15:05, Kyonshi wrote:
    I have a rather new, minimal installation of Rocky Linux 9 (so
    effectively RHEL 9) and have a pihole running on another machine in my private network. I have changed the nameservers on the Rocky Linux
    machine to resolve via the pihole DNS on the local network.
    All of a sudden the DNS stops resolving.

    ; <<>> DiG 9.16.23-RH <<>> google.com
    ;; global options: +cmd
    ;; connection timed out; no servers could be reached

    Network connection still is there, only DNS resolution is affected. I
    can ping the other machine. The pihole is running and it is resolving
    for other machines, it just doesn't seem to work on this particular
    machine.

    Anyone got an idea what the issue might be?

    Start with:

    host -v google.com pi.hole.ip.address
    --
    Cheers, Carlos.

    --- Synchronet 3.20a-Linux NewsLink 1.114
  • From Kyonshi@gmkeros@gmail.com to comp.os.linux.networking on Wed Apr 24 13:28:31 2024
    From Newsgroup: comp.os.linux.networking

    On 4/13/2024 10:32 PM, Carlos E.R. wrote:
    On 2024-04-12 15:05, Kyonshi wrote:
    I have a rather new, minimal installation of Rocky Linux 9 (so
    effectively RHEL 9) and have a pihole running on another machine in my
    private network. I have changed the nameservers on the Rocky Linux
    machine to resolve via the pihole DNS on the local network.
    All of a sudden the DNS stops resolving.

    ; <<>> DiG 9.16.23-RH <<>> google.com
    ;; global options: +cmd
    ;; connection timed out; no servers could be reached

    Network connection still is there, only DNS resolution is affected. I
    can ping the other machine. The pihole is running and it is resolving
    for other machines, it just doesn't seem to work on this particular
    machine.

    Anyone got an idea what the issue might be?

    Start with:

    host -v google.com pi.hole.ip.address



    I had to install Rocky Linux 8 for other reasons and that solved this issue
    --
    microblog: https://dice.camp/@kyonshi
    macroblog: https://gmkeros.wordpress.com
    pictures: https://portfolio.pixelfed.de/kyonshi
    --- Synchronet 3.20a-Linux NewsLink 1.114