I can’t speak as to why your data isn’t propagating to the rest of your network (as seems to be one issue [@Fraser, perhaps you’d be able to help with debugging that side of a local network?] ), but I can explain what’s going on with the current ‘DNS’ setup.
Your two errors are similar, but distinct.
Essentially a Public Name, is a mutable data saved at the XOR location of the sha3( <public name string>), so when no data is found at that location, you’ll see Requested public name is not found.
The data that should be stored at that location is a map of <service>.<publicName>, such that you can map www.whatever and somethingelse.whatever, and point those to different data on the network.
So Requested service is not found is an error when something-doesnt-exist.whatever, and the something-doesnt-exist entry could not be found.
That’s the ‘current’ implementation. Though we’ve an RFC open that specs out a desired path forward using RDF to clarify the data (as well as describing how public name resolution would work, in general (which is something that’s been missing). You can read that here.
Hope that helps clarify that! (Feedback/thoughts etc are super welcome btw, we’ve a thread dedicated to that.