NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

nnagreg's avatar
nnagreg
Apprentice
Mar 22, 2022
Solved

DNS Hijacking R8000P- presenting errors, requires fresh frequently

For the past several months,  I've noticed the when using my router as the DNS server,  it appears to act odd, "Site cannot be reached" ,  "DNS address could not be found. Diagnosing the problem" esp...
  • nnagreg's avatar
    nnagreg
    Apr 18, 2022

    UPDATE 4/18/2022

     

    Work Around  (Solved)

     

    Enabled - IPV6 Auto  (set to 6to4 Tunnel)

     

    Hi All,

    By enabling IPv6,  the problem went away.

     

    Hope this helps!!

     

    Greg

     

     

nnagreg's avatar
nnagreg
Apprentice
Apr 18, 2022

******** UPDATE *************

4/18/2022

Any thoughts?  Problem still exists

 

 

New Firmware applied:   V1.4.3.88_1.3.50

Did a Factory reset and completely re-built the router configuration using the WEB interface.

 

Problem still exists using windows 11 device :  

Seeing 'DNS_PROBE' errors,

Still requires F5 refresh to continue to website during first request  

AND now the router does not supply my manual DNS entries to the clients.

 

Detail below

----------------

Advanced Internet Setup:

Get Dynamically from ISP
Use Static IP Address
IP Address 192.168.88.8
IP Subnet Mask 255.255.255.0
Gateway IP Address 192.168.88.253

 

IP Address192.168.88.8
Subnet Mask255.255.255.0
Default Gateway192.168.88.253
DNS Server8.8.8.8


Domain Name Server (DNS) Address
X Use These DNS Servers
Primary DNS 8.8.8.8
Secondary DNS  blank

 

 

Client DHCP info:

IP =  192.168.99.10  (Client IP)

Netmark 255.255.255.0

Gateway:  192.168.99.3

DNS Server = 192.168.99.3 (Its the internal Router IP)

 

NSLOOKUP  (new Domain names are returned immediately)

> server
Server: UnKnown
*** UnKnown can't find server: Non-existent domain

 

 

 

FURRYe38's avatar
FURRYe38
Guru
Apr 18, 2022

Seems like the router is getting a private IP address (192.168.88.#) instead of a public address, ##.##.###.###.

Looking at the modem seems like it doe not have a built in router however wondering if the ISP has it configured differently. 

Can you check with the ISP to see if they have the modem configured differently and see if the modem can pass thru a public IP address? 

 

  • nnagreg's avatar
    nnagreg
    Apprentice
    Apr 18, 2022

    Yes, this DHCP behavior is odd with the current version of the firmware.

    With my ISP, I've elected to not accept the DNS entries from the provider (Midco.net)


    Good news is that I was able to resolve the problem with DNS multiple requests,  see my posted down below.   However,  my DHCP clients still point to the router as the DNS server,  odd.

     

    Thanks for the help!