TypicallyI connect to my router by its IP address of 192.168.1.1. However, I am also able to connect to it at the URL
router.asus.com. My computer does not have a connection to the Internet. How does this work?
As you're likely using DHCP, it'll automatically assign your machines to use its own DNS. You could test this by changing to a manually assigned DNS server (8.8.8.8 for example), flush your DNS and then try the same URL.
Since that page isn't served over HTTPS, it's entirely possible for the router to simply intercept the HTTP request and answer it without talking it any external server. Asus routers have been known to redirect pages under some circumstances. Note that if the redirection occurs even without an Internet connection (i.e. with no external DNS), it must be caused by your router's DNS; there's no reason both couldn't be going on, though.
My Netgear home router, for instance, can block domains and keywords (serving a "blocked by Netgear firewall" page) even if I'm not using its DNS. I made sure that it's not intercepting the DNS requests; the name gets resolved correctly, but going to the page in a web browser results in the "blocked" page.
I was using the Asus router with my previous dns provider, and the
router.asus.com was resolving to the correct IP of the router, when I switched to nextdns, it does not work anymore.. it might seems obvious since the entry probably does not exist on the nextdns servers, but what get's me confused is that it did not existed in my previous dns provider as well
1. Run "ipconfig /all" to see what DNS-servers the client use. What does DNS-server say?
2. Run "nslookup
router.asus.com" to see what servers answers to the query. Is your router listed?
3. Surf to
test.nextdns.io and in a browser to see connectivity information.
4. Does it work on other clients? (Phone, Tablet etc.)
Easy fix is go to settings > rewrites. Add
router.asus.com and for the target put in your Asus's router ip address. I use opnsense and use unbound dns on my router for lots of local services. In the cli client I have a few customizations the ones I had to do that to let my router handle resolution for local domains was forwader
mydomain.com=
10.0.1.1:5352 (this is your router's IP) The port 5352 is what I changed my unbound service to answer on. So basically nextdns cli sends the majority of my name requests to the nextdns service, but then I sitll can get my local name resolution I need. I use a different IP for my web services inside than outside.
Before operating an ASUS router , a user has to register the product in an ASUS account. Without registering your product in an ASUS account, you cannot operate the router in a network. After you log in to the ASUS account, a user becomes eligible to receive various product promotions from ASUS. Go to the official website of ASUS and register your product there before performing the
router.asus.com setup process.
Actual Behaviour:
Everything works great until turning off DHCP on router and turning on DHCP on pihole. Network still functions but ipscan of router shows no ports open. Router is still functioning. Trying to connect via ip using a browser gives "[IP] refused to connect"
I have smashed the search function and have found similar issues but none have helped.
tracert shows a single hop to router when using both
router.asus.com and IP.
Commonly, a router configures a static IP for itself, so it would never request a DHCP lease.
Without DHCP registration through Pi-hole's DHCP server, Pi-hole also remains unaware of any names your router may use for itself.
Thanks @Bucking_Horn but as I mentioned in my first post this has already been done. My DHCP also starts a number after the router so i know its not assigning that IP anywhere else. Even if I had not set it up in the Local DNS Records, access to my router using the static IP should work right?
So after all that it seems there may be something wrong with the Asus AC68U. After a few reboots during setup my router closes port 80 used for the httpd and refuses to reopen it. I cant figure out why. Managed to get my router setup correct without it closing so for the time being its all up and running! It took a dozen attempts but PiHole was nothing to do with it.
3a8082e126