Dig -x +trace?
Mike Hodson
mystica at gmail.com
Mon Oct 3 19:17:55 UTC 2022
>
> https://defuse.ca/b/GuqI6Lct This is a working reverse dns delegated to
> us. Notice that It took HOW MANY times of me hitting "up-enter" to properly
> get it to show something: TWENTY FOUR.
>
Ok no, more like 12... I didnt realize when pasting the pastebin copied the
entire text into an edit box at the bottom.
But still. 12 tries to get different results and finally get the 1 result I
expect is utterly crap.
On Mon, Oct 3, 2022 at 1:11 PM Mike Hodson <mystica at gmail.com> wrote:
> On Thu, Sep 29, 2022 at 4:57 PM Mark Andrews <marka at isc.org> wrote:
>
>>
>>
>> Hiding the actual address you are wanting the reverse lookups for.
>> Really you have an incredible resource here of knowledgeable people with
>> millennia of experience between them who would have looked at every
>> delegation and then would have told you what they saw that was wrong.
>>
>
> Privacy must be uncommon to you. I was asking why dig was returning 'not
> the entire tree of delegations' when I ran trace. But since you seem to
> think showing the actual IP will give me a different answer than, after
> finally executing dig about 20 times, I come to the conclusion that
> "globalcrossing/l3/lumen actually owns the delegation, not us, and I cant
> do anything without contacting them"
>
>
>> Not installing maintenance releases when they are released. dig +trace
>> is a little fragile in 9.18.1 following the change to libuv. Upgrade to a
>> current release.
>>
> I would expect every stupid distro by now to have a working and usable
> copy of 'dig' available. How the hell did ubuntu even ship something so
> useless that it cant even give me the same results more than once at a time?
>
> https://defuse.ca/b/GuqI6Lct This is a working reverse dns delegated to
> us. Notice that It took HOW MANY times of me hitting "up-enter" to properly
> get it to show something: TWENTY FOUR.
>
> How the hell did this ship?!
>
> I expect the same results every time I run the program, not 24 tries
> later, I get the results I expect.
>
> Now, for the delegation I was wondering about; it ONLY took THREE tries to
> get dig to return these results:
>
> mike at mike-pc:~$ dig -x 208.51.60.0 SOA +trace
>
> ; <<>> DiG 9.18.1-1ubuntu1.1-Ubuntu <<>> -x 208.51.60.0 SOA +trace
> ;; global options: +cmd
> . 511356 IN NS a.root-servers.net.
> . 511356 IN NS b.root-servers.net.
> . 511356 IN NS c.root-servers.net.
> . 511356 IN NS d.root-servers.net.
> . 511356 IN NS e.root-servers.net.
> . 511356 IN NS f.root-servers.net.
> . 511356 IN NS g.root-servers.net.
> . 511356 IN NS h.root-servers.net.
> . 511356 IN NS i.root-servers.net.
> . 511356 IN NS j.root-servers.net.
> . 511356 IN NS k.root-servers.net.
> . 511356 IN NS l.root-servers.net.
> . 511356 IN NS m.root-servers.net.
> . 511356 IN RRSIG NS 8 0 518400
> 20221016050000 20221003040000 18733 .
> YIXaa/EBSQVICUNPRhTRK21PwpQy6pk6zgrYeokFCUG6pPKmfn+7gOiq
> k12OWXOTYRguXIWv0YauJlYZlRJFOucvxIWI2hE8oeppc5bCDBXUwZ2V
> 6GDOEYnCkk/8Bh7QgaAGpBYeNbuPj2TD1bDX1dHKOZ/PIOoXeSxAOuAi
> xkZzEi4/zXqDWmeDA7CVq74qNvVgfkVg0NXDxqFtmJH/cXwvdGsWbeaZ
> gu95le0xD12RbYGoxfzM06DT4YLJMPJ4evH26D2xnUolBqZ9tbqjAxcv
> AdnAllbVw5AcuaYQMCqn3qy/x+M4rJKmExFughKCvnZWXxTlGcZDRDt1 0VFw0g==
> ;; Received 1097 bytes from 1.1.1.1#53(1.1.1.1) in 20 ms
>
> in-addr.arpa. 172800 IN NS a.in-addr-servers.arpa.
> in-addr.arpa. 172800 IN NS b.in-addr-servers.arpa.
> in-addr.arpa. 172800 IN NS c.in-addr-servers.arpa.
> in-addr.arpa. 172800 IN NS d.in-addr-servers.arpa.
> in-addr.arpa. 172800 IN NS e.in-addr-servers.arpa.
> in-addr.arpa. 172800 IN NS f.in-addr-servers.arpa.
> in-addr.arpa. 86400 IN DS 47054 8 2
> 5CAFCCEC201D1933B4C9F6A9C8F51E51F3B39979058AC21B8DF1B1F2 81CBC6F2
> in-addr.arpa. 86400 IN DS 53696 8 2
> 13E5501C56B20394DA921B51412D48B7089C5EB6957A7C58553C4D4D 424F04DF
> in-addr.arpa. 86400 IN DS 63982 8 2
> AAF4FB5D213EF25AE44679032EBE3514C487D7ABD99D7F5FEC3383D0 30733C73
> in-addr.arpa. 86400 IN RRSIG DS 8 2 86400
> 20221016120000 20221003110000 44050 arpa.
> S3xrgFdS8QeUYgzkEYDAq7muSgCVtNAcHotpSZC/CqBQIm1hwlTBQ+mn
> Wi/Hhi/rgwIjwLRxsN/MfGlnU9uAOFwinly14co58FbqCEa5Q1t+/Lx0
> d2qSCKoQ2POl3gsy3PXYybFqBVz/2RyOuQKQwBsis2UL9mliA00iOuDy
> Cw5zFLSK4X7GeAIGVbBoz6pHK6YfZV/3zctBG/0ooEsAPM8R02SC9JHY
> 8YxqF/VqqxRceq5YYFENMK0yVslB57N07F1eQ1kQfXtf0+BCZVvt1SpC
> m4Z6EjT87RDIzHid8h2xmfKJARQbRUxBHcNW9UteICtURVdiW0UtF73T gs1K5A==
> ;; Received 893 bytes from 199.9.14.201#53(b.root-servers.net) in 44 ms
>
> 208.in-addr.arpa. 86400 IN NS r.arin.net.
> 208.in-addr.arpa. 86400 IN NS u.arin.net.
> 208.in-addr.arpa. 86400 IN NS x.arin.net.
> 208.in-addr.arpa. 86400 IN NS y.arin.net.
> 208.in-addr.arpa. 86400 IN NS z.arin.net.
> 208.in-addr.arpa. 86400 IN NS arin.authdns.ripe.net.
> 208.in-addr.arpa. 86400 IN DS 42649 8 2
> 25E577B46EDA1A702037D78813C161270156706E30C28102832BAF9A A81B5A3E
> 208.in-addr.arpa. 86400 IN RRSIG DS 8 3 86400
> 20221022031953 20221001032504 19590 in-addr.arpa.
> UlXNiU7lLRbvyiaBN+VLa+SZtqxefKTQMqcgirVEXyx3cW9UowrsVOZx
> 3OyEB1HvrGZP9TeL6Bs/9jYrgAI94sOD3vK/cxRvH41A4XHxSFeZtJry
> ys3P6g9ZJ5rQrEo//l/nCsJf87y7DMl6YpteFjPYRFOJWXbhC9t0EpwF GM0=
> ;; Received 393 bytes from 193.0.9.1#53(f.in-addr-servers.arpa) in 120 ms
>
> 51.208.in-addr.arpa. 86400 IN NS name.phx.gblx.net.
> 51.208.in-addr.arpa. 86400 IN NS name.snv.gblx.net.
> 51.208.in-addr.arpa. 86400 IN NS name.roc.gblx.net.
> 51.208.in-addr.arpa. 86400 IN NS name.jfk1.gblx.net.
> 51.208.in-addr.arpa. 10800 IN NSEC 0.52.208.in-addr.arpa. NS
> RRSIG NSEC
> 51.208.in-addr.arpa. 10800 IN RRSIG NSEC 8 4 10800
> 20221017163242 20221003153242 35871 208.in-addr.arpa.
> enZnvkPe0CVbuCUoO6bJuFevbDYCMwwBAPNvWhukmpFZBT3NV5RDTKW5
> JSdCpYNguApCKhagjOfDflIjmcYt5nn6mLcdCAkvgtWBOXvCFi7mi5H0
> WEUTIKRpMHBcRwCK/Qc8vqH2o0mkkJMv4izGNsAguOvbNiL5PluWgZP8 vKc=
> ;; Received 444 bytes from 199.212.0.63#53(z.arin.net) in 92 ms
>
> 60.51.208.in-addr.arpa. 43200 IN NS ns1.trustats.com.
> 60.51.208.in-addr.arpa. 43200 IN NS ns2.trustats.com.
> ;; Received 129 bytes from 67.17.215.134#53(name.snv.gblx.net) in 24 ms
>
>
>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20221003/80b36d52/attachment-0001.htm>
More information about the bind-users
mailing list