Server not found

[ColinTaylor]

And you say these nslookup commands work from this same PC if you use the Ethernet connection instead of WiFi? Can you try that again now please?

EDIT: What country are you in?

 

[Ramz]

And you say these nslookup commands work from this same PC if you use the Ethernet connection instead of WiFi? Can you try that again now please?

EDIT: What country are you in?

Yes via ethernet works when i bypass my asus router works on both laptops her work address.

 

[ColinTaylor]

Yes via ethernet works when i bypass my asus router works on both laptops her work address.

Sorry, can you explain what you mean by this? "works when i bypass my asus router"

You never said you were bypassing the router. We thought you were connecting the PC's Ethernet port to the Asus router's LAN port.

 

[Ramz]

Sorry, can you explain what you mean by this? "works when i bypass my asus router"

You never said you were bypassing the router. We thought you were connecting the PC's Ethernet port to the Asus router's LAN port.

Sorry we both use WIFI to try and access her work via asus router which has DNS server quad9 and cloudfare installed. But when we connect via Ethernet via modem which is bridged to asus router it works hope that makes sense, So something is up with the Asus router.

 

[peepsnet]

with the NSLOOKUP not working at all it would seem something on the router is redirecting all port 53 requests to the router.

I dont know if there are any settings that force all port 53 traffic back to the router

 

[ColinTaylor]

Sorry we both use WIFI to try and access her work via asus router which has DNS server quad9 and cloudfare installed. But when we connect via Ethernet via modem which is bridged to asus router it works hope that makes sense, So something is up with the Asus router.

<sigh> So you experience the same problem when you connect to the router (not modem) over Ethernet.

Check the DNS Filtering page again and make absolutely sure it isn't enabled.

 

[Ramz]

<sigh> So you experience the same problem when you connect to the router over Ethernet.

Check the DNS Filtering page again and make absolutely sure it isn't enabled.

Sorry where do i find that? in ASUS User interface

 

[ColinTaylor]

Sorry where do i find that? in ASUS User interface

The same place it was when you checked it before and said it wasn't enabled. Under the LAN tab.

 

[Ramz]

The same place it was when you checked it before and said it wasn't enabled. Under the LAN tab.

Thanks for all your help by he way.

 

[Ramz]

The same place it was when you checked it before and said it wasn't enabled. Under the LAN tab.

Found it. Thanks.

 

[ColinTaylor]

Found it. Thanks.

And...

 

[Ramz]

And...

just rebooted router and same result. So there is something wrong with router like I said when i run wire from my providers modem it works, And when I disconnect our phones from Wifi they work so its my router or I have Quad9 and cloudfare set up wrong in router.

 

[john9527]

Did you see my question...post #19?

 

[ColinTaylor]

As per the question in post #19:

"If you have DoT enabled (DNS Privacy) try disabling it."

 

[Ramz]

Did you see my question...post #19?

I did and nothing.

 

[Ramz]

As per the question in post #19:

"If you have DoT enabled (DNS Privacy) try disabling it."

Same error .

 

[Ramz]

As per the question in post #19:

"If you have DoT enabled (DNS Privacy) try disabling it."

I got this now
nslookup starmetrolandmedia.my.salesforce.com 9.9.9.9
Server: dns9.quad9.net
Address: 9.9.9.9

Non-authoritative answer:
Name: na110-ia2.ia2.r.my.salesforce.com
Addresses: 13.110.33.205
13.110.34.205
13.110.34.77
Aliases: starmetrolandmedia.my.salesforce.com
na110.my.salesforce.com
na110-ia2.my.salesforce.com

 

[john9527]

much better.....should work now.

let me guess.....you are running the 384.16-beta? (other part of my question )

 

[Ramz]

no

much better.....should work now.

let me guess.....you are running the 384.16-beta? (other part of my question )[/QUOTE

No running 384,15

 

[ColinTaylor]

Same error .

I got this now

So what changed between these two statements?