search

exentriquesolutions / nip.io

http://nip.io
Other
1.39k stars 148 forks source link

Some IP addresses don't work #5

Closed codecat closed 4 years ago

codecat commented 4 years ago

Either this is something I don't entirely understand or it's a bug, but it happens on both xip and nip.

The domain 192-168-168-31.nip.io is not resolving to anything for me:

; <<>> DiG 9.10.6 <<>> 192-168-168-31.nip.io
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 21764
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;192-168-168-31.nip.io.     IN  A

;; Query time: 26 msec
;; SERVER: 192.168.168.1#53(192.168.168.1)
;; WHEN: Wed Jul 29 15:04:07 CEST 2020
;; MSG SIZE  rcvd: 39

But the more traditional 192-168-0-31.nip.io does:

; <<>> DiG 9.10.6 <<>> 192-168-0-31.nip.io
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 47161
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;192-168-0-31.nip.io.       IN  A

;; ANSWER SECTION:
192-168-0-31.nip.io.    86400   IN  A   192.168.0.31

;; Query time: 22 msec
;; SERVER: 192.168.168.1#53(192.168.168.1)
;; WHEN: Wed Jul 29 15:04:11 CEST 2020
;; MSG SIZE  rcvd: 64

Changing the 168 to 167 or 169 makes it resolve again. What is it about this subnet that breaks the DNS resolving?

codecat commented 4 years ago

I'll close this issue as it seems to be something related to the network I'm on. (It works fine on a completely separate network.)

If anyone knows what's causing it I would love to know though!

Seems like switching to a different DNS server (1.1.1.1) also resolves this, so it seems like the DNS of my router is somehow blocking it. Interesting!