Recreational / Hobbyist UAS pilot reported flying the UAS although the flight control software displayed a No-Fly Zone warning.

Narrative

I was conducting a routine UAS operation over my own property--an area where I have flown numerous times previously--when I encountered unusual notifications during the airspace-authorization process.Using a LAANC-connected application to request flight authorization; I received a message I had not seen before. To be cautious; I reduced my planned flight area twice to ensure adequate distance from the nearest airport. On the third submission; the system granted authorization.When starting takeoff; the flight-control software displayed a 'No-Fly Zone' warning indicating flight restrictions in effect for the location. Believing this to be a software error (because I had just received LAANC approval -- and the requisite indicator had turned 'green' indicating the approval window was now in effect ); I chose to proceed with the mission. The UAS remained within visual line of sight for the entire flight; operated at or below 140 ft AGL; and no manned aircraft were observed.Approximately two hours after the flight; I received a phone call from a local Air National Guard unit asking if I had been operating a drone. I confirmed the flight and explained what I was doing. The conversation was professional; and no further action was taken. Looking back; I relied too heavily on my past experience at this property and didn't take into account the fact that airspace restrictions can change at any time. Furthermore; given the amount of errors I have experienced with drone software; I have grown overly dismissive of their warnings. This flight was a wake up call. I will change my approach and in the future; if there is any doubt; I will call the tower at the airport to verify there are no special airspace restrictions in place before I fly.