0

Rewrite to local address

Hi!

This a today problem, the rewrites rules to local address not resolve, are blocked.

I use a web server in local network with several webs (in subdomains).

  • web1.rafa.local
  • web2.rafa.local
  • ....

and in nextdns >> setings >> rewrites a rule:

  • *.rafa.local >> 127.0.01

And allways was working without problems... but today do not resolve. If I ping to thats address i get a response from "blockpage.nextdns.io [217.146.1.31]".

I use YogaDNS (free edition) and its send de ask to:

  • [06.07 08:44:56] web-2022.rafa.local - process : server=NextDNS (NextDNS), rule=Default

I disable "DNS Rebinding Protection" (before was active, but this is not the problem)...

What can i do? Any idea?

Thanks in advance

p.d. i have a lot of subdomains and several "nextdns configs" (computer, brewsers, etc.) (host file alternative is no easy to configure). :-(

5 replies

null
    • rafa
    • 1 yr ago
    • Reported - view

    I resolve with host file. :-?

    if anybody has a idea? welcome! ;-)

    • badung
    • 1 yr ago
    • Reported - view

    I have the same problem since today.

    I am connected to my companies VPN and the local Domain Names *.mycompany.local can't be resolved any more. It worked for years until today.

    I had to disable NextDNS to be able to work.

    • NextDNs
    • 1 yr ago
    • Reported - view

    Can you please show the result of:

    dig CHAOS web-2022.rafa.local

    (you may need to install dig first on your windows)

    • badung
    • 1 yr ago
    • Reported - view

    Today it is working again for me 🤔

    • rafa
    • 1 yr ago
    • Reported - view

    Hi. Today is working.

    I try that command in Linux and says "Got bad packet: bad label type"... but is working.

    If i put "dig @45.90.28.64 subdomain.rafa.local" >>>> (45.90.28.64 is a NextDNS server IP what I use) 

    ; <<>> DiG 9.16.27-Debian <<>> @45.90.28.64 subdomain.rafa.local
; (1 server found)
;; global options: +cmd
;; Got answer:
;; WARNING: .local is reserved for Multicast DNS
;; You are currently testing what happens when an mDNS query is leaked to DNS
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61676
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;subdomain.rafa.local.    IN      A
;; ANSWER SECTION:
subdomain.rafa.local. 300 IN      A       127.0.0.1
;; Query time: 42 msec
;; SERVER: 45.90.28.64#53(45.90.28.64)
;; WHEN: Wed Jun 08 09:03:02 CEST 2022
;; MSG SIZE  rcvd: 60

    "subdomain.rafa.local" is not real

    Now, is working perfect!

    Thanks!

Login to reply

Content aside

  • 1 yr agoLast active
  • 5Replies
  • 823Views
  • 4 Following