In article ,
Jun Xiang X Tee wrote:
> (1) Does "dig" get its UDP packets from "named" server? Or "lwresd" server?
> Or others?
If you use the @server argument, it gets it from that server. Otherwise,
it gets it from a server in your resolver configuration
(/etc/resolv.conf on Unix).
>
Jun Xiang X Tee wrote:
>
> For the past two weeks, I have searched through many articles online
> and asked many people on how to do this, but I am still confused on
> where "dig" gets the UDP packets from.
It sounds like you should start off with a good DNS textbook, such as
http://www.zytrax.
Sorry, but isn't this almost exactly the same question which you asked
in: https://lists.isc.org/pipermail/bind-users/2016-June/097012.html
("Append a Hard-coded Text Tuple into Additional Section of "dig"
Feature") ? And "Query "resolver" and "lwresd" via "dig"" ?
Perhaps if you explained what yo
(1) Does "dig" get its UDP packets from "named" server?
Yes.
tcpdump -n -i lo0 port domain
$ dig www.allpowerlabs.com
20:36:28.073280 IP 127.0.0.1.10588 > 127.0.0.1.53: 18890+ A?
www.allpowerlabs.com. (38)
20:36:28.210557 IP 127.0.0.1.53 > 127.0.0.1.10588: 18890 1/3/3 A 75.119.212.1
On Wed, 2016-06-22 at 01:06 +, Jun Xiang X Tee wrote:
> I am working on hacking UDP packets returned to "dig" client. I
> wish to include some extra information about the "digged" domain
> (e.g., facebook.com) at Additional Section of "dig" reply in TXT
> format. The ideal result is to be abl
Dear all,
I am working on hacking UDP packets returned to "dig" client. I wish to
include some extra information about the "digged" domain (e.g., facebook.com)
at Additional Section of "dig" reply in TXT format. The ideal result is to be
able to see the hacked UDP packets having the extra in
6 matches
Mail list logo
