Google DNS tries to resolv Standard Gateway (Router Address)

[shog...@googlemail.com]

Why does Google DNS start a lookup of the Standard Gateway address?

I can not access my router because of this behaviour when using Google DNS.

There is no problem when the ISP DNS is used. In this case the browser opens the router when I enter the Standard Gateway Adress.

[Alex Dupuy]

Hi Shogimoto,

You wrote:

Why does Google DNS start a lookup of the Standard Gateway address?

I can not access my router because of this behaviour when using Google DNS.

There is no problem when the ISP DNS is used. In this case the browser opens the router when I enter the Standard Gateway Address.

Your browser is not recognizing the "Standard Gateway address" (I assume you mean 192.168.1.1 or similar) as an address and is instead trying to resolve it as a domain name. If you query Google Public DNS with an IPv4 address as the domain name, it properly returns NXDOMAIN (and in fact it must do so to provide an answer which can be validated with DNSSEC:

$ dig +noall +authority +dnssec +comment 192.168.1.1 @8.8.8.8

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 42787

;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 4, ADDITIONAL: 1

;; OPT PSEUDOSECTION:

; EDNS: version: 0, flags: do; udp: 512

;; AUTHORITY SECTION:

.                       4546    IN      SOA     a.root-servers.net. nstld.verisign-grs.com. 2017070701 1800 900 604800 86400

.                       4546    IN      RRSIG   SOA 8 0 86400 20170720170000 20170707160000 15768 . GYb0myKeVihadm1ODfwIjFjJt+xyTB0e46bt+/hTWiI9RvlhY1OlN7fB QgMtMrVnQ9oQcVnZ6UWSfbDzsGKDs2LQjogjjYJuWrxnbTwp8Nfdvoa9 N/IOo31F2NIEqOrip4cIijJmagzP3b/aoWKqMksXMSUZKbEAjHKlbyyc AtfPJxVYTf9NmxT0BGvSkYDy/bU6Oxk1z0GkG3dKtjrEUFhOgdfrpeha tv9jFAs9GU196F+3nS0vz0uGj3kpEQ8pysvOwnrAQpEFF8G+BYZPrCwr 7G/i1yBKawr2pH2nKSiWEmSaqhxhN/q/Eg3AbyylSs40BeCdXUG9CYqx i/wPPQ==

.                       4546    IN      NSEC    aaa. NS SOA RRSIG NSEC DNSKEY

.                       4546    IN      RRSIG   NSEC 8 0 86400 20170720170000 20170707160000 15768 . Ccy0EZfrYbuUlhhnVoei0PcwinueGAI73RViA/I5R2vea2eGZQpNW1qh QMKKEW0qDOdlOEks2uBB3X+G0+CALxjnRtJLhMt6oydwhmuZS9EBZcB3 SrBgDFoUrbjsGpCZkDGXNa1rJUqEbE4AvAYQYWQgGkvTLGRzkddUUMXQ HrqyCNU/t1hJ5JFhyCoK1kMQkOdzPHtiRzba67KyrJRjh6SuOjEqjpNC nSs8cwMxSRSr0EZ96R+BdyGaKCTguFmo9XPs802FcmcYy/wytg0ULQYw a6Z0XdmC3Y9hoFEvJ5mjQGyCt+wZCy/gffxDi+H4cy3SOrEKrVcJZBCE CM9NKw==

Some resolvers will return an A record when an IPv4 address is looked up as a domain, the only public resolvers that I could find which do this are the Level 3 resolvers (4.2.2.1), but it may be supported for compatibility reasons by some resolver software including firmware on WiFi or cable routers and other low-end devices. However, it is better not to enable this feature as you will incur additional traffic and latency for no reason (since you already have the address).

$ dig +noall +comment 192.168.1.1 @208.67.220.220 # OpenDNS

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 24219

;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

$ dig +noall +comment 192.168.1.1 @8.8.8.8 # Google

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 8934

;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

$ dig +noall +answer +comment 192.168.1.1 @4.2.2.1 # Level3

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6199

;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; ANSWER SECTION:

192.168.1.1.            86400   IN      A       192.168.1.1

$ dig +noall +answer +comment 192.168.1.1 # My Apple Airport router

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 24556

;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; ANSWER SECTION:

192.168.1.1.            655360  IN      A       192.168.1.1