NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Reverse lookup not working ?
Hi. My model is AX1800 (not sure why it isn't in the list). I do not succed to use the local internal resolver on my Netgear (DHCP activated). The local names that I've set up in the admin interfa...
Make sure that your reverse DNS record matches the host name of your server. Make sure that a regular DNS lookup for the domain you have designated as the reverse DNS record entry returns the IP address in question. For example: If 70.32. 86.172 has a reverse DNS record of example.com.
Cooper152 wrote:
Make sure that your reverse DNS record matches the host name of your server. Make sure that a regular DNS lookup for the domain you have designated as the reverse DNS record entry returns the IP address in question. For example: If 70.32. 86.172 has a reverse DNS record of example.com.
- Make sure that your reverse DNS record matches the host name of your server.
- Make sure that a regular DNS lookup for the domain you have designated as the reverse DNS record entry returns the IP address in question. For example: If 70.32. 86.172 has a reverse DNS record of example.com.
Sorry i am still learning all this network stuff.
I was thinking the router would do this job for me.
My goal is to simply identify my devices on Adguard Home without static adress for all my devices. Is it possible to achieve that?
I have a question similar to the OP. I have setup two separate DNS servers on my private network 192.168.0.0/24. When I send reverse lookups directly to each server they work fine, e.g. `dig -x 192.168.0.1 @192.168.0.4` returns all expected PTR records with NOERROR. However when I drop the DNS server argument (e.g. @192.168.0.4) and the request is sent to the router (a Netgear Nighthawk AX120 BTW), I get an empty PTR record and the dreaded NXDOMAIN status. Foward lookups (either sent directly to each server or the router) also work fine.
Any clues, advice, or suggestions?
(Actually, now that I'm writing this, it occurred to me that at least one server is using port 953 in addition to port 53 used on the other server. That probably has something to do with it.)