• dns issues, anyone?

    From august abolins@21:1/5 to All on Thu Jan 19 18:08:00 2023
    Has anyone here ever come across a situation where PING to a
    specific #.#.#.# works, but not to a domain name?

    This problem seems to be reoccuring here every few days. I
    can't understand what would cause the difference.

    I have configured Windows' DNS specifically to 1.1.1.1 and
    8.8.8.8, yet visiting sites and pulling in my mail (POP/SMTP)
    would fail.

    Any similar experiences? Solutions?
    --
    ../|ug

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From JJ@21:1/5 to august abolins on Fri Jan 20 08:13:19 2023
    On Thu, 19 Jan 2023 18:08:00 -0500, august abolins wrote:
    Has anyone here ever come across a situation where PING to a
    specific #.#.#.# works, but not to a domain name?

    This problem seems to be reoccuring here every few days. I
    can't understand what would cause the difference.

    I have configured Windows' DNS specifically to 1.1.1.1 and
    8.8.8.8, yet visiting sites and pulling in my mail (POP/SMTP)
    would fail.

    Any similar experiences? Solutions?

    In most cases, it'd be due to bad network route chosen by the ISP.
    Or the ISP itself.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul in Houston TX@21:1/5 to august abolins on Fri Jan 20 17:52:13 2023
    august abolins wrote:
    Has anyone here ever come across a situation where PING to a
    specific #.#.#.# works, but not to a domain name?

    This problem seems to be reoccuring here every few days. I
    can't understand what would cause the difference.

    I have configured Windows' DNS specifically to 1.1.1.1 and
    8.8.8.8, yet visiting sites and pulling in my mail (POP/SMTP)
    would fail.

    Any similar experiences? Solutions?
    --
    ../|ug

    Good dns info here: https://www.hp.com/us-en/shop/tech-takes/how-to-resolve-dns-issues

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From august abolins@21:1/5 to All on Fri Jan 20 18:24:00 2023
    Hello jj4public!

    ** On Thursday 19.01.23 - 20:13, jj4public wrote to :

    Any similar experiences? Solutions?

    In most cases, it'd be due to bad network route chosen by the ISP.
    Or the ISP itself.

    It's not the network route at the ISP. I have a local Win7 pc
    and other smartphones accessing my router to the 'net, and they
    don't exhibit any problems with websites.

    The only way that I can seem to recover normal operation is if
    I reboot XP.

    --
    ../|ug

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From august abolins@21:1/5 to All on Fri Jan 20 23:20:00 2023
    Hello Paul!

    Good dns info here: https://www.hp.com/us-en/shop/tech-takes/how-to-resolve-dns-issues


    Thx. I'll be trying the following the next time it happens:

    ipconfig /flushdns
    ipconfig /registerdns
    ipconfig /release
    ipconfig /renew
    NETSH winsock reset catalog
    NETSH int ipv4 reset reset.log
    NETSH int ipv6 reset reset.log
    Exit

    I only new of this sequence:

    ipconfig /release *
    ipconfig /flushdns
    ipconfig /renew

    .but /registerdns might be necessary.

    And if that doesn't help, then I'll have to disable the
    services in the "clean reboot" option that the article
    suggests.

    I does seem to be possible that some service simply trips up
    the dns since the pc will function just fine for several days
    between hibernate or standby, but then it would fail.

    --
    ../|ug

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)