Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Firewalls
[Top] [All Lists]

RE: DNS Manipulation via IPTables or other means?

Subject: RE: DNS Manipulation via IPTables or other means?
Date: Thu, 23 Nov 2006 12:13:21 -0000
  
honestly , I have worked with iptables in really complex 
environments for many years, i never have heard of 
manipulating dns records on the fly, I don't even think you 
can do this with string matching since string matching lets 
you check for a string, not manipulate it.

I really wonder why views aren't scalable, maybe there is 
another solution, I always draw my stuff out on paper (yes 
REAL paper :)) and visualize it that way, then find easier 
solution by looking at the picture. Views in Bind are meant 
for this kind of thing , different access control from 
different ips give you different results. Would you mind 
sharing some more info? maybe the amount of views you are 
handling etc. Maybe someone comes up with a more streamlined idea?

Consider this example, your company wants to provide access to a 
partner company over an IPSec VPN connection.  The servers at both 
companies are on the same 192.168.1.0/24 network.  Your company 
wants to also forward DNS requests to your partner company's DNS 
server for lookups involving their internal DNS domain.

There are several points worth noting about this setup:

i) NAT will have to be used to prevent the two internal networks 
colliding

ii) your partner company's DNS server will be returning addresses on 
your own network, not on the remote NAT'ed network.

ii) you might not be able to request views on your partner company's
DNS server

iii) it is not a scalable and maintainable solution to provide spoofed
zones for your partner company's DNS zones.

An ideal solution (as provided by the PIX) is to manipulate the DNS
responses from your partner company's DNS server.

I've never even bothered trying to set-up a deployment, with these 
issues, with IPTables --- any pointers as to how to do this with IPTables 
would be greatly appreciated.


Paul

<Prev in Thread] Current Thread [Next in Thread>