Unbound stop working on 127.0.0.1 after 2.5.1 upgrade

juniper

@sashli you have to change GENERAL SETUP---DNS Server Settings with an external server and after reboot pfsense server.

After you can ping 127.0.0.1 and unbound reply to 127.0.0.1 query

but if you change pfsense general setup dns doesn't work anymore.

SashLi

@juniper can confirm removing the 127.0.0.1 AND restarting did the trick . It did not work just to remove the DNS Server from the configuatuion.

Now the dig command return to operate / resolve as normal. Many thanks to all and @juniper

dig @127.0.0.1 apple.com +short
17.253.144.10

SashLi

Just as a summary :

I think this was in pfsense before they introduced the option in the General Setup that the localhost DNS setting will be used as drop down, the locahost was set in the DNS Server as 127.0.0.1
After updates to 2.5.1 things go wrong if you have the 127.0.0.1 in the General Setup , DNS Server Settings set as additional DNS Server to the option of " DNS Resolution Behavior " where you can already set that the locahost should be in use.
If you did the settings wrong here, unbound will not be able to resolve and other effect I saw now on 2.5.0 that sometimes DNS resolve fails without reason

Gertjan

Exact.

The bad news : this is not good.
The good news : it's a non issue, as adding 127.0.0.1 is not needed - it's already there.

I just added the missing ::1 (we all prefer IPv6, right ?) and that doesn't 'break' the localhost.

Now I have this :

and it works.

SteveITS

See if a reboot fixes it like this post.

MikeV7896

After removing 127.0.0.1 from the server list (since it's already covered by the dropdown further down) and rebooting, localhost DNS resolution is working again.

Of interesting note about this though... the Status > DNS Resolver page showed no statistics or data, even though resolution for other hosts on my networks was occurring without issue. But now that I made the above change, all appears to be working.

Gertjan

@virgiliomi said in Unbound stop working on 127.0.0.1 after 2.5.1 upgrade:

the Status > DNS Resolver page showed no statistics or data

Changing the DNS settings restart the Resolver, clearing all stats and cache.
That normal.

garyn

I had this same issue. I didn't find this thread until this morning and adding ::1 did not work for me. However, what I found yesterday that did work was removing 127.0.0.1 and adding my router's local LAN address, in my case 192.168.2.1.

Cool_Corona

@garyn Remove everything in DNS and reboot.

It will work afterwards with no records.

garyn

@cool_corona I'll try it, thanks!