PTR records are just as pointless as A records...
in a secured DNS heirarchy, this is less of an issue
We are not quite there yet, are we?
since you have to spoof the entire delegation chain.
so either trust the DNS (both forward and reverse)
or not. For
Adam Jacob Muller wrote:
Not possible with most modern IRCD's since they check forward and
reverse dns.
So for example if your address is:
1.2.3.4
and that resolves to:
1-2-3-4.dsl.verizon.net
the ircd make sure that:
1-2-3-4.dsl.verizon.net
resolves back to
1.2.3.4
it's a simple
http://www.albany.edu/~ja6447/hacked_bots8.txt
Isn't it a good idea to collect the IP addresses rather than the ptr
name? For instance, if I were an evil person in control of the ptr
record of my own IP, I could easily make the name something like
1-2-3-4.dsl.verizon.net, and if you didn't
On Fri, Feb 11, 2005 at 03:45:52PM +, Ketil Froyn wrote:
http://www.albany.edu/~ja6447/hacked_bots8.txt
Isn't it a good idea to collect the IP addresses rather than the ptr
name? For instance, if I were an evil person in control of the ptr
record of my own IP, I could easily make
Not possible with most modern IRCD's since they check forward and
reverse dns.
So for example if your address is:
1.2.3.4
and that resolves to:
1-2-3-4.dsl.verizon.net
the ircd make sure that:
1-2-3-4.dsl.verizon.net
resolves back to
1.2.3.4
it's a simple and elegant solution that basically
