• DNS_PROBE_FINISHED_NXDOMAIN

    From Rex Libris@king.book@bookworm.com to alt.os.linux.ubuntu on Tue May 25 11:24:58 2021
    From Newsgroup: alt.os.linux.ubuntu

    Using Ubuntu 21.04, Chrome 90.0.4430.212 64 bit
    Get this error only on one site https://www.seniorscard.nsw.gov.au/
    Using wifi, DNS server set to Google 8.8.8.8 & 8.8.4.4.
    Happens in Fierfox as well, in both browsers also in incognito/private
    mode.
    Cleared the cache cahe & cookiess in Chrome, rebooted etc. Error still persists. I could access this site two weeks ago.
    Found this page https://is.gd/wlGtZg but for life of me (inexperienced)
    can't figure out how to follow these instructions
    "Now add below line in the file
    supersede domain-name-servers 8.8.8.8;
    → Save the file and restart the network.
    sudo service network-manager restart"
    (after running sudo nano /etc/dhcp/dhclient.conf)
    And is the best way to resolve the error? Maybe I should be doing
    something else?
    Strange only happening on the above web site (that I know of), and the
    site works ok in my Android phone. All other sites I use seem to
    resolve ok.
    All help gratefully received. As usual!
    --- Synchronet 3.18a-Linux NewsLink 1.113
  • From Henry J Briggs, Esq.@nospam@thankyou.net to alt.os.linux.ubuntu on Wed May 26 08:43:36 2021
    From Newsgroup: alt.os.linux.ubuntu

    On Tue, 25 May 2021 11:24:58 +1000
    Rex Libris <king.book@bookworm.com> wrote:
    Using Ubuntu 21.04, Chrome 90.0.4430.212 64 bit

    Get this error only on one site https://www.seniorscard.nsw.gov.au/

    Using wifi, DNS server set to Google 8.8.8.8 & 8.8.4.4.

    Happens in Fierfox as well, in both browsers also in incognito/private
    mode.

    Cleared the cache cahe & cookiess in Chrome, rebooted etc. Error
    still persists. I could access this site two weeks ago.

    Found this page https://is.gd/wlGtZg but for life of me
    (inexperienced) can't figure out how to follow these instructions

    "Now add below line in the file

    supersede domain-name-servers 8.8.8.8;
    → Save the file and restart the network.

    sudo service network-manager restart"

    (after running sudo nano /etc/dhcp/dhclient.conf)

    And is the best way to resolve the error? Maybe I should be doing
    something else?

    Strange only happening on the above web site (that I know of), and the
    site works ok in my Android phone. All other sites I use seem to
    resolve ok.

    All help gratefully received. As usual!


    Anyone?
    --- Synchronet 3.18a-Linux NewsLink 1.113
  • From Rex Libris@king.book@bookworm.com to alt.os.linux.ubuntu on Wed May 26 08:51:31 2021
    From Newsgroup: alt.os.linux.ubuntu

    On Wed, 26 May 2021 08:43:36 +1000
    "Henry J Briggs, Esq." <nospam@thankyou.net> wrote:

    Anyone?


    BTW just tried the link on Chromebook running same version of Chrome,
    page loaded ok. So can Chrome be ruled out of the equation?

    --- Synchronet 3.18a-Linux NewsLink 1.113
  • From Anssi Saari@as@sci.fi to alt.os.linux.ubuntu on Wed May 26 09:17:30 2021
    From Newsgroup: alt.os.linux.ubuntu

    "Henry J Briggs, Esq." <nospam@thankyou.net> writes:

    Anyone?

    Well, it's easy to answer your specific question. As you're already
    using Google's name servers, changing to Google's name servers is a null operation and is unlikely to help.

    As to what the problem is and how to fix it, I have no idea. That site
    loads for me in Chromium and Firefox and in general
    www.seniorscard.nsw.gov.au resolves to 103.1.195.149 via Google's and
    other name servers.

    Maybe you have DNS over HTTPS enabled in both browsers and that's not
    working?
    --- Synchronet 3.18a-Linux NewsLink 1.113
  • From Rex Libris@king.book@bookworm.com to alt.os.linux.ubuntu on Wed May 26 21:54:47 2021
    From Newsgroup: alt.os.linux.ubuntu

    On Wed, 26 May 2021 09:17:30 +0300
    Anssi Saari <as@sci.fi> wrote:

    Maybe you have DNS over HTTPS enabled in both browsers and that's not working?

    Any ideas where the setting is for that? Can't find it in Chrome.

    --- Synchronet 3.18a-Linux NewsLink 1.113
  • From Anssi Saari@as@sci.fi to alt.os.linux.ubuntu on Wed May 26 15:34:15 2021
    From Newsgroup: alt.os.linux.ubuntu

    Rex Libris <king.book@bookworm.com> writes:

    On Wed, 26 May 2021 09:17:30 +0300
    Anssi Saari <as@sci.fi> wrote:

    Maybe you have DNS over HTTPS enabled in both browsers and that's not
    working?

    Any ideas where the setting is for that? Can't find it in Chrome.

    Apparently it's in the experimental chrome://flags or that's the feeling
    I got. Can't see it in Chromium 90 though. So anyways, not something one
    would enable by accident.
    --- Synchronet 3.18a-Linux NewsLink 1.113
  • From Henry J Briggs, Esq.@nospam@thankyou.net to alt.os.linux.ubuntu on Thu May 27 12:33:16 2021
    From Newsgroup: alt.os.linux.ubuntu

    On Wed, 26 May 2021 15:34:15 +0300
    Anssi Saari <as@sci.fi> wrote:

    Rex Libris <king.book@bookworm.com> writes:

    On Wed, 26 May 2021 09:17:30 +0300
    Anssi Saari <as@sci.fi> wrote:

    Maybe you have DNS over HTTPS enabled in both browsers and that's
    not working?

    Any ideas where the setting is for that? Can't find it in Chrome.

    Apparently it's in the experimental chrome://flags or that's the
    feeling I got. Can't see it in Chromium 90 though. So anyways, not
    something one would enable by accident.

    Weird fix here - removing the VPN solved the issue. Does a VPN have a
    dns cache?

    --- Synchronet 3.18a-Linux NewsLink 1.113
  • From Anssi Saari@as@sci.fi to alt.os.linux.ubuntu on Thu May 27 09:14:11 2021
    From Newsgroup: alt.os.linux.ubuntu

    "Henry J Briggs, Esq." <nospam@thankyou.net> writes:

    Weird fix here - removing the VPN solved the issue. Does a VPN have a
    dns cache?

    Some VPN services provide their own DNS so the problem may have been
    with that.
    --- Synchronet 3.18a-Linux NewsLink 1.113
  • From Henry J Briggs, Esq.@nospam@thankyou.net to alt.os.linux.ubuntu on Thu May 27 18:13:27 2021
    From Newsgroup: alt.os.linux.ubuntu

    On Thu, 27 May 2021 09:14:11 +0300
    Anssi Saari <as@sci.fi> wrote:

    "Henry J Briggs, Esq." <nospam@thankyou.net> writes:

    Weird fix here - removing the VPN solved the issue. Does a VPN
    have a dns cache?

    Some VPN services provide their own DNS so the problem may have been
    with that.



    Even more weird - using wireguard on VPN, would not load; without
    wireguard, but VPN enabled, loads ok.

    Thanks for the help! Have reported to the VPN guys (Mulvad).

    --- Synchronet 3.18a-Linux NewsLink 1.113