So, let's break this down: - NS records for nepustil.net https://trans-trust.verisignlabs.com/?z=nepustil.net
;; AUTHORITY SECTION: nepustil.net. 172800 IN NS ns.nepustil.de. nepustil.net. 172800 IN NS ns.nepustil.eu. nepustil.net. 172800 IN NS ns1.ispeg.eu. - NS records for nepustil.de https://trans-trust.verisignlabs.com/?z=nepustil.de ;; AUTHORITY SECTION: nepustil.de. 86400 IN NS ns.nepustil.com. nepustil.de. 86400 IN NS ns1.ispeg.eu. nepustil.de. 86400 IN NS ns1.nepustil.net. - NS records for nepustil.eu https://trans-trust.verisignlabs.com/?z=nepustil.eu ;; AUTHORITY SECTION: nepustil.eu. 86400 IN NS ns1.nepustil.net. nepustil.eu. 86400 IN NS ns.nepustil.de. - NS records for nepustil.com https://trans-trust.verisignlabs.com/?z=nepustil.com ;; AUTHORITY SECTION: nepustil.com. 172800 IN NS ns.nepustil.de. nepustil.com. 172800 IN NS ns1.nepustil.net. - NS records for ispeg.eu https://trans-trust.verisignlabs.com/?z=ispeg.eu ;; AUTHORITY SECTION: ispeg.eu. 86400 IN NS ns.nepustil.de. ispeg.eu. 86400 IN NS ns.lf.net. ispeg.eu. 86400 IN NS ns1.ispeg.eu. ;; ADDITIONAL SECTION: ns1.ispeg.eu. 86400 IN A 178.132.64.130 ns1.ispeg.eu. 86400 IN AAAA 2a03:2380:2:4::1 - NS records for lf.net https://trans-trust.verisignlabs.com/?z=lf.net ;; AUTHORITY SECTION: lf.net. 172800 IN NS dns1.lf.net. lf.net. 172800 IN NS dns2.lf.net. lf.net. 172800 IN NS dns3.lf.net. ;; ADDITIONAL SECTION: dns1.lf.net. 172800 IN A 212.9.160.10 dns2.lf.net. 172800 IN A 62.50.111.2 dns3.lf.net. 172800 IN A 213.178.170.2 So, what you created here is a maze of NS records that has circular dependencies on each other where only ispeg.eu domain has GLUE records as can provide a break out of the loop. Just compare the transitive trust for lf.net (that's quite simple and straightforward) and the nepustil.* domains where pointing nepustil.* to ns*.nepustil.* makes absolutely no sense as this just creates more loops. For example the resolution of nepustil.net have these paths: nepustil.net -> nepustil.de -> nepustil.net -> ENDLESS LOOP nepustil.net -> nepustil.de -> nepustil.com -> nepustil.de -> ENDLESS LOOP nepustil.net -> nepustil.de -> nepustil.com -> nepustil.net -> ENDLESS LOOP nepustil.net -> nepustil.de -> nepustil.net -> ispeg.eu -> GLUE OK nepustil.net -> nepustil.eu -> nepustil.net -> ENDLESS LOOP nepustil.net -> nepustil.eu -> nepustil.de -> nepustil.com -> nepustil.de -> ENDLESS LOOP nepustil.net -> nepustil.eu -> nepustil.de -> nepustil.com -> nepustil.net -> ENDLESS LOOP nepustil.net -> nepustil.eu -> nepustil.de -> nepustil.net -> ispeg.eu -> GLUE OK nepustil.net -> ispeg.eu -> GLUE OK As you can see, there are 6 paths that can be taken to resolve the nameserver that are completely useless and just adds more work to the resolver prolonging the time and work that it takes to resolve the domain. Ondrej -- Ondřej Surý (He/Him) [email protected] My working hours and your working hours may be different. Please do not feel obligated to reply outside your normal working hours. > On 2. 1. 2026, at 22:44, Kurt Jaeger <[email protected]> wrote: > > Hi! > >> I'll try to add glue records for ispeg.eu... > > It already had correct glue records. > > -- > In the nightmare of the dark W.H. Auden, 1940 > all the dogs of Europe bark > [email protected] +49 171 3101372 > -- > Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from > this list. -- Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list.
