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

Re: 2.3.3 Release Testing DNS

2.3.3 Development Snapshots
4
4
1.4k
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
    mafiosa
    last edited by Feb 11, 2017, 5:10 PM

    I m facing a problem.I upgraded from 2.3.2 just now to 2.3.3rc but in general settings tab i m not allowed to add my gateway as DNS server unlike before.My isp uses its gateway to provide dns service as well.Kindly enable that option like before.
    error.png
    error.png_thumb

    1 Reply Last reply Reply Quote 0
    • D
      Derelict LAYER 8 Netgate
      last edited by Feb 11, 2017, 9:48 PM

      Why would you want to assign a gateway to itself (or anything else on a local subnet)? Seems if that used to work it shouldn't have. pfSense will already have an interface/connected route in that case.

      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
      • J
        jimp Rebel Alliance Developer Netgate
        last edited by Feb 12, 2017, 12:06 AM

        If that is your gateway it can't take a new route since that is directly connected. It would also be considered directly connected if it had some other route. In other words, you're trying to set a route when it can't be set – either it's already there or it's not necessary. So there is no bug there. Just set the gateway to "none" and it'll follow the system routing table and do the right thing.

        If that is your only gateway you don't need to set a gateway on any of the DNS entries anyhow. That's only useful for Multi-WAN when using DNS Resolver in forwarding mode or the DNS Forwarder

        Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

        Need help fast? Netgate Global Support!

        Do not Chat/PM for help!

        1 Reply Last reply Reply Quote 0
        • P
          phil.davis
          last edited by Feb 12, 2017, 4:23 AM

          As a side-issue on that screen shot, do a ctrl-F5 (or whatever key-combination it is on your OS/browser) to force a reload of all the JavaScript and CSS. That will make the "*Hostname" "*Domain" go away and turn into Hostname Domain

          After an upgrade, everyone should do a browser refresh - because old JavaScript and CSS can get cached for a while in the browser.

          Jim has raised an issue to find a suitable way to make that happen automagically in future:
          https://redmine.pfsense.org/issues/7251

          As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
          If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

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