I see what you mean, OS/2 dig v9.11.28 doesnt do anything here.
no error messages, just exits after a short wait.
On Mon, 22 May 2023 07:28:11 +0800 (AWS) Ian Manners wrote:
>
> Hi Steven,
>
> <snip>
>
> $dig +nssearch pmoylan.org
> SOA ns1.wiz.net.au. dns.wiz.net.au. 2019030902 10800 3600 604800 300 from
> server 203.30.197.11 in 51 ms.
> SOA ns1.wiz.net.au. dns.wiz.net.au. 2019030902 10800 3600 604800 300 from
> server 43.229.63.26 in 63 ms.
>
> Works ok, at least now, from Western Australia.
> Last few weeks there have been several outages on networks
> in Australia plus peering infrastructure upgrades that normally
> happen late Sundays in Australia.
>
> Cheers
> Ian
>
> > [d:\tmp]dig +nssearch pmoylan.org
> >
> > reports
> >
> > couldn't get address for 'ns1.wiz.net.au': failure
> > couldn't get address for 'ns2.wiz.net.au': failure
> > D:\usr2\bin\dig.exe: couldn't get address for 'ns1.wiz.net.au': no more
> >
> > Do any of you get differing responses? This command returns expected
> > results on OpenSuse and lists the SOA records.
> >
> > [d:\tmp]dig +short pmoylan.org
> >
> > returns nothing which is expected given the issues Peter is working on.
> > However, for bind 9.11.36 and 9.11.37, this command hangs. It can be
> > killed with top's forced kill (Ctrl-F), but not a normal kill (Ctrl-K).
> >
> > Do any of you get differing results.
> >
> > dig.exe from bind 9.12.4 seems work the same as 9.11.28 for these tests.
> >
> > Thanks,
> >
> > Steven
> >
>
>
>
back to list