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

    DNS Not Working with Static WAN IP

    Scheduled Pinned Locked Moved General pfSense Questions
    5 Posts 4 Posters 675 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.
    • M
      Mountbaldy
      last edited by

      Hello!

      So I scoured the web for an answer to this and I can't seem to locate one so I'm posting this question here... I can seem to get my DNS working just fine with using DHCP WAN IP but as soon as I put my static WAN settings back in DNS fails.

      When I change things to static WAN IP, I make sure to change my WAN gateway to the static WAN gateway from the ISP. I have tried leaving this out but it doesn't change anything. I can't seem to figure out what I"m missing. I used static settings for quite some time before and never had any problems.

      Thanks!

      Joe

      1 Reply Last reply Reply Quote 0
      • GertjanG
        Gertjan
        last edited by

        Hi,

        My pfSense has a LAN network 192.168.1.1/24.
        I have an "upstream" router, the one my ISP gave me - I have to use it to handle the VDSL stuff coming in over the POTS network.
        A classic router-after-router setup.

        Normally, I could / can / will / should use DHCP on the WAN : my pfSense is 'seen' by my ISP router as "just another device on his network".
        Btw : I have set my ISP router LAN to 192.168.10.1/24, it's default 192.168.1.1/24 would otherwise severally conflict with my pfSense LAN network.

        So, this works for me out of the box :

        725c9954-e05d-400b-899f-7e3f53f90a8c-image.png

        so I obtain this for my WAN :

        f990e5ce-b033-4be8-9554-c27b1b3a6a07-image.png

        I could go to static on WAN - why not - here we go :

        9083761f-3b96-4bb3-9f86-8f0bfb6354da-image.png

        Important detail : because this is a WAN , I had to "select an existing Gateway from the list or add a new one using the "Add" button." I had to release my DHCP lease first (see second image image - red button) which "frees" the WAN Gateway IP, so I could create a Gateway 192.168.10.1 - and add it to the WAN setup.
        As said : a WAN type interface needs a gateway IP. It's asigned to you by your box locally, or even from a router not at your site, so your ISP has to give it to you upfront.
        The /24 mask is the only correct value - so I set that.

        DNS : the default setup is more the perfect. Nothing had to be changed. The default resolver will work with any kind of connection. As long as there is a connection.

        38928f5b-a9c4-42c8-877e-915c650d33b7-image.png

        Si I post this reply using a static WAN IP.

        No "help me" PM's please. Use the forum, the community will thank you.
        Edit : and where are the logs ??

        1 Reply Last reply Reply Quote 0
        • bingo600B
          bingo600
          last edited by

          @Gertjan

          Why 1480 as MTU , VDSL or ???

          /Bingo

          If you find my answer useful - Please give the post a šŸ‘ - "thumbs up"

          pfSense+ 23.05.1 (ZFS)

          QOTOM-Q355G4 Quad Lan.
          CPUĀ  : Core i5 5250U, Ram : 8GB Kingston DDR3LV 1600
          LANĀ  : 4 x Intel 211, DiskĀ  : 240G SAMSUNG MZ7L3240HCHQ SSD

          GertjanG 1 Reply Last reply Reply Quote 0
          • DerelictD
            Derelict LAYER 8 Netgate
            last edited by

            Is your WAN provisioned by the ISP as DHCP or static? You need to use settings that match how it is provisioned.

            Chattanooga, Tennessee, USA
            A comprehensive network diagram is worth 10,000 words and 15 conference calls.
            DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
            Do Not Chat For Help! NO_WAN_EGRESS(TM)

            1 Reply Last reply Reply Quote 0
            • GertjanG
              Gertjan @bingo600
              last edited by Gertjan

              @bingo600 said in DNS Not Working with Static WAN IP:

              Why 1480 as MTU , VDSL or ???

              Good question.
              That value was needed, way back.
              It goes with my tunnel.he.net IPv6 ISP.

              I have to re experiment with it.

              edit : done.

              ping www.yahoo.com -f -l 1474 -4
              

              and higher = fragmented.

              ping www.yahoo.com -f -l 1472 -4
              

              It's a pass.
              1472 it will be.

              No "help me" PM's please. Use the forum, the community will thank you.
              Edit : and where are the logs ??

              1 Reply Last reply Reply Quote 1
              • First post
                Last post
              Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.