Hi Brian, They do work if you specify +noedns
Frank > On 8 May 2019, at 10:46, Brian Candler <b.cand...@pobox.com> wrote: > > On 08/05/2019 09:07, Brian Candler wrote: >> From here (UK), that domain looks a bit broken - see the FORMERR response >> from the authoritative servers. I have tried from two different networks >> and get the same response. > > The nameserver A records for this domain are also toast. The glue records > have these IPs for ns1/ns2.netclient.no: > > $ dig +norec @x.nic.no. ns1.netclient.no. a > ... > ;; ADDITIONAL SECTION: > ns1.netclient.no. 7200 IN A 213.179.58.78 > ns2.netclient.no. 7200 IN A 89.105.33.114 > ns2.netclient.no. 7200 IN A 213.162.232.67 > ... > > But trying to get authoritative answers I get FORMERR from all of these. > > $ for a in 213.179.58.78 89.105.33.114 213.162.232.67; do for h in > ns1.netclient.no. ns2.netclient.no.; do dig +norec "@$a" "$h" a; done; done | > grep status: > ;; ->>HEADER<<- opcode: QUERY, status: FORMERR, id: 29160 > ;; ->>HEADER<<- opcode: QUERY, status: FORMERR, id: 36959 > ;; ->>HEADER<<- opcode: QUERY, status: FORMERR, id: 37955 > ;; ->>HEADER<<- opcode: QUERY, status: FORMERR, id: 24754 > ;; ->>HEADER<<- opcode: QUERY, status: FORMERR, id: 65007 > > ;; ->>HEADER<<- opcode: QUERY, status: FORMERR, id: 1677 > > I can't see how this domain ever resolves unless you already have the answer > in your cache. Even the best-known resolvers have problems with it: > > $ dig @8.8.8.8 ns2.netclient.no > > ; <<>> DiG 9.10.6 <<>> @8.8.8.8 ns2.netclient.no > ; (1 server found) > ;; global options: +cmd > ;; connection timed out; no servers could be reached > > However, on a retry, it *did* resolve somehow. > > Regards, > > Brian. > > _______________________________________________ > Pdns-users mailing list > Pdns-users@mailman.powerdns.com > https://mailman.powerdns.com/mailman/listinfo/pdns-users _______________________________________________ Pdns-users mailing list Pdns-users@mailman.powerdns.com https://mailman.powerdns.com/mailman/listinfo/pdns-users
