Hi, I see the FCFS page has a new zone key now. I still got the gnunet.org and pin zone in my config. I believe this is from an old(?) configuration and the old pin zone is discontinued? Can you confirm?
``` ❯ gnunet-config -s gns .gnunet.org = 000G0047M3HN599H57MPXZK4VB59SWK4M9NRD68E1JQFY3RWAHDMKAPN30 .pin = 000G001MF6DVMZZ4Y8XRZQDXM1PB3D3VGEK29ZHXBA57EPSNW1QBPKT8J0 INTERCEPT_DNS = NO MAX_PARALLEL_BACKGROUND_QUERIES = 1000 UNIX_MATCH_GID = YES UNIX_MATCH_UID = NO UNIXPATH = $GNUNET_RUNTIME_DIR/gnunet-service-gns.sock BINARY = gnunet-service-gns HOSTNAME = localhost IMMEDIATE_START = YES START_ON_DEMAND = YES ``` Best, Martin On Sunday, January 14th, 2024 at 3:54 PM, Schanzenbach, Martin <schan...@gnunet.org> wrote: > Hi, > > "gnunet.org" is not configured by default through any start zone > https://www.rfc-editor.org/rfc/rfc9498.html#name-start-zones > > You can look at all suffix-to-zone mappings on your system using > > $ gnunet-config -s gns > > What is configured is our current registrar, as "gnunet.gns.alt". > Basically, zones registered at https://fcfs.gnunet.org are reachable > with that suffix. > You can try registering your own zone and try it. > You can also try resolving names of other user's zones (if you know any). > > We currently do not publish the gnunet.org IP addresses in GNS I think. > The unit tests locally configures gnunet.org. > > I hope that helps. > > BR > Martin > > > On 14.01.24 08:35, marty1885 wrote: > > > Hi, > > > > I found that I can't resolve gnunet.org via GNS.The following command > > simply do not finish. I'm resolving gnunet.org in my unit test to make sure > > my GNS resolving works. Is the node hosting that domain down? Or something > > happened? Or it got upgraded to an incomparable version with the official > > 0.20? > > > > `❯ gnunet-gns -u gnunet.org <hangs, no result>` > > > > I am peer CCXHBE49GRQVFAVFQ3BXVXPHHD63NG6ZNY31R0F59KVDZQA42PTG. And I do > > see I'm connected to other nodes. I don't think network connection is the > > issue. > > > > Martin
