Dig -x +trace?

Andrew Latham lathama at gmail.com
Thu Sep 29 22:25:12 UTC 2022


Mike

1. You can set the server with @ so in your case `dig @1.1.1.1 -x 208.x.x.x
+trace`
2. Test with an IP that you know should work `$ dig +short @8.8.4.4 -x
8.8.8.8` answers `dns.google.` for example
3. Confirm your RIR or provider has working NS set for the range. Query
directly the NS you think should be working.
4. `+[no]trace This option toggles tracing of the delegation path from the
root name servers for the name being looked up.`
5. It sounds like your dig is answering correctly.
`

On Thu, Sep 29, 2022 at 3:51 PM Mike Hodson <mystica at gmail.com> wrote:

> I'm attempting to figure out how/why my reverse DNS delegation is broken.
> I've already deleted systemd-resolved's temporary resolv.conf and added in
> an immutable single line
> nameserver 1.1.1.1
> resolv.conf.
>
> I can dig +trace forward hostnames fine.
> I cannot dig -x an ip +trace.
> All I get is the root-servers instead of any sort of reverse looking up
> happening at all.
> What am I doing wrong?
>
> Thanks,
>
> Mike
>
> $ dig -x 208.x.x.x +trace
>
> ; <<>> DiG 9.18.1-1ubuntu1.1-Ubuntu <<>> -x 208.x.x.x +trace
> ;; global options: +cmd
> .                       509855  IN      NS      a.root-servers.net.
> .                       509855  IN      NS      b.root-servers.net.
> .                       509855  IN      NS      c.root-servers.net.
> .                       509855  IN      NS      d.root-servers.net.
> .                       509855  IN      NS      e.root-servers.net.
> .                       509855  IN      NS      f.root-servers.net.
> .                       509855  IN      NS      g.root-servers.net.
> .                       509855  IN      NS      h.root-servers.net.
> .                       509855  IN      NS      i.root-servers.net.
> .                       509855  IN      NS      j.root-servers.net.
> .                       509855  IN      NS      k.root-servers.net.
> .                       509855  IN      NS      l.root-servers.net.
> .                       509855  IN      NS      m.root-servers.net.
> .                       509855  IN      RRSIG   NS 8 0 518400
> 20221012170000 20220929160000 20826 .
> FkcsBmNz2oK02ARhYfNSfxbnEL93RITDteQtHQoPn8zHZg9B6BRXqkH9
> +UpAEViDraX+4l8YJiUvYzrHh9twpQry0vv7xgDLoDdU9kRqokG5DEoq
> Ueqph6qleC6Vylga4f1MzW
> N+Dh9zK9/eCSp6WxwgbnW53a9GMDbI5KWZ
> WkcWw3IPHVvVwDZfWhrKJtKZ3hafsGgmigm9F01Xk17prOAS6jBbvYjT
> jCUyTl3UZJ+bAKS4tkpFdjp78raxBKBQPN6TzdLjtxYQrhriZZ3Gjdcg
> dT+WQkLGYuyeakm2JqVe9vXGMGn0XkZEGMYnh7iW80N1XHyBMfhzGO+s 61zvWA==
> ;; Received 1097 bytes from 1.1.1.1#53(1.1.1.1) in 12 ms
>
>
> --
> Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
> from this list
>
> ISC funds the development of this software with paid support
> subscriptions. Contact us at https://www.isc.org/contact/ for more
> information.
>
>
> bind-users mailing list
> bind-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users
>


-- 
- Andrew "lathama" Latham -
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20220929/0554a183/attachment-0001.htm>


More information about the bind-users mailing list