Netgate SG-1000 microFirewall

Author Topic: Re: 2.3.3 Release Testing DNS  (Read 734 times)

0 Members and 1 Guest are viewing this topic.

Offline mafiosa

  • Jr. Member
  • **
  • Posts: 66
  • Karma: +1/-0
    • View Profile
Re: 2.3.3 Release Testing DNS
« on: February 11, 2017, 11:10:07 am »
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.

Offline Derelict

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 9980
  • Karma: +1126/-311
    • View Profile
Re: Re: 2.3.3 Release Testing DNS
« Reply #1 on: February 11, 2017, 03:48:28 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.
Las Vegas, Nevada, USA
Use this diagram to describe your issue.
The pfSense Book is now available for just $24.70!

Offline jimp

  • Administrator
  • Hero Member
  • *****
  • Posts: 21619
  • Karma: +1484/-26
    • View Profile
Re: Re: 2.3.3 Release Testing DNS
« Reply #2 on: February 11, 2017, 06:06:51 pm »
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
Need help fast? Commercial Support!

Co-Author of pfSense: The Definitive Guide. - Check the Doc Wiki for FAQs.

Do not PM for help!

Offline phil.davis

  • Hero Member
  • *****
  • Posts: 4618
  • Karma: +552/-3
    • View Profile
    • International Nepal Fellowship
Re: 2.3.3 Release Testing DNS
« Reply #3 on: February 11, 2017, 10:23:03 pm »
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:
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