• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login
Netgate Discussion Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login

Potential DNS Rebind attack detected

Scheduled Pinned Locked Moved General pfSense Questions
3 Posts 3 Posters 618 Views
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • T
    thebonden
    last edited by Feb 13, 2022, 8:06 PM

    Potential DNS Rebind attack detected, see http://en.wikipedia.org/wiki/DNS_rebinding
    Try accessing the router by IP address instead of by hostname.

    hi I bought a domain today
    and I have made a record that points to my ipadress Wan porten on Pfsens but now I get this message where do I get rid of it
    the plan is that i will make a sub domain for pfsen's web interface
    and one for VPN

    pf.mydomane.dk
    vpn.mydomane.dk

    where do i set up DNS I use one.com

    i also want to make ddns on it

    S 1 Reply Last reply Feb 13, 2022, 9:17 PM Reply Quote 0
    • S
      SteveITS Galactic Empire @thebonden
      last edited by Feb 13, 2022, 9:17 PM

      @thebonden First, I recommend not exposing your router web GUI to the Internet. When we do this for clients, we allow the connection only from our office IP.

      You can go to the System/Advanced/Admin Access page and either 1) check "Disable DNS Rebinding Checks" or 2) enter the hostname and/or IP in the "Alternate Hostnames" field.

      Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
      When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
      Upvote 👍 helpful posts!

      1 Reply Last reply Reply Quote 1
      • S
        stephenw10 Netgate Administrator
        last edited by Feb 14, 2022, 1:26 AM

        If the firewall is actually configured with that FQDN it won't throw that warning.

        1 Reply Last reply Reply Quote 0
        3 out of 3
        • First post
          3/3
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
          This community forum collects and processes your personal information.
          consent.not_received