[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Fixed!: nslookup can't resolve hostnames

Hi Mihira

Thanx for your emails. The problem was the following:

My ip address is dynamic, and one my rules on iptables had the last ip
address, not the new. This rule was created by ipmasq even I removed this
later, this rule was saved by iptables-save. So when this rules was readed
by iptables-restore applied to INPUT and OUTPUT chain.

Thanx for your time.

Best regards.


Original Message:
From: Mihira Fernando mihiratheace@gmail.com
Date: Mon, 17 Jul 2006 11:34:34 +0700
To: debian-firewall@lists.debian.org, debian-firewall@lists.debian.org
Subject: Re: weird: nslookup can't resolve hostnames

mario@cancun.net wrote:
> Hi,
> The ip address as DNS nameservers are obtained via DHCP from my ISP, these
> name servers are the same I've specified staticaly for each of my internal
> boxes. I use the same rules for iptables to set the firewall, but
> 'nslookup' still sending the same problem, with firewall rules up or not.

is the name server reported by nslookup and the actual name server 
assigned by your ISP the same ? it is possible that the ISP has assigned 
a different NS but nslookup is still looking for an outdated one.

Also, how are the DNS set in dansguardian and Squid ?

Random Quotes From Megas XLR
Coop: You see? The mysteries of the Universe are revealed when you break 
Jamie: When in doubt, blow up a planet.
Kiva: It's an 80 foot robot, if we can't see it, absolutely it's not here.
Glorft Technician: Unnecessary use of force in capturing the Earthers 
has been approved.

To UNSUBSCRIBE, email to debian-firewall-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact

mail2web - Check your email from the web at
http://mail2web.com/ .

Reply to: