0

FRITZ.BOX | NRDs blocked -> fritz.box is an alias for site.my.box

Hey All,

My PC uses NEXTDNS directly for DNS.
So i added some "rewrites" of ip's in the configuration.
( sorry, i was not able to switch language to english, so i do not now if "rewrite" is the corrent field name  )

"fritz.box" -> "192.168.178.1"

To be sure, domain "fritz.box" ( normally resolved by fritz.box itself ) will NOT resolved "outside".

I found today that i'm blocked by NRD.

It seems, that the "rewrite's"  in my profile are not working.
I deleted "*.fritz.box" and added it again - won't help.

Also:
Special rewrites, e.g. "mylittlepc.fritz.box" will not be resolved.
I see it in the logs - blocked by NRD.

So, outging queried "domain" is correct.

What has been changed?

Worked for years  , but now it's broken...

1 reply

null
    • Alexander_Rudolf
    • 3 mths ago
    • Reported - view

    Some update - since now:

    "fritz.box" is blocked by NRDs ( CNAME, resolving to site.my.box ).
    If i disable "NRDs" , "REWRITE" is working again.

    I'm quite sure i tested it prio to open this bug report.
    But now i found "REWRITE" working ( again? ).

    I note:
    "NRDs" are blocking first, since now or earlier, who knows.
    "REWRITE" seems like to be  checked afterwards - if domain is not blocked.

    My setup now:
    I add "fritz.box" to "Allowlist", so NRDs will be ignored.
    After that, REWRITE "fritz.box -> 192.168.178.1" will be done.
    IP is located back to my internal network  and not in the wild ( this suspicious site.my.box ).

    The problem in my configuration was probably latent for a long time.
    Usage problem on my part.

    No bug, usage problem.

    Regards.

Login to reply

Content aside

  • 3 mths agoLast active
  • 1Replies
  • 102Views
  • 1 Following