In article ,
Matus UHLAR - fantomas wrote:
> On 21.09.09 19:26, Shi Jin wrote:
> > I've confirmed that the problem is firewall related. I've replaced my
> > current Untangle firewall with a simplest Linux NAT iptables firewall and
> > everything works perfectly, without any complains.
>
> I'd s
On 21.09.09 19:26, Shi Jin wrote:
> I've confirmed that the problem is firewall related. I've replaced my
> current Untangle firewall with a simplest Linux NAT iptables firewall and
> everything works perfectly, without any complains.
I'd say it was bad configuration, not necessarily a bad firewal
Thank you all.
I've confirmed that the problem is firewall related. I've replaced my current
Untangle firewall with a simplest Linux NAT iptables firewall and everything
works perfectly, without any complains.
Thank you very much for your kind help/suggestions.
Shi
1) Confirm whether you need to forward at all. If you don't need to,
then remove the forwarders entries and that should take care of the
errors in your log.
2) If you *must* use forwarders, look at the part of the config that you
didn't show us, and determine whether there is something there (e.
In message <865284.37771...@web36203.mail.mud.yahoo.com>, Shi Jin writes:
>
> > "host unreachable" is one of the clearer error messages, so
> > you need
> > to do some digging. From the box that you've set up bind9
> > on you'll
> > need to use dig to query the ISP's name servers. If that
> > wor
> "host unreachable" is one of the clearer error messages, so
> you need
> to do some digging. From the box that you've set up bind9
> on you'll
> need to use dig to query the ISP's name servers. If that
> works, then
> you'll have to use tcpdump on that box to find out what
> named is doing.
>
>
for each DNS query, the syslog shows entries of
>
> dhcp-dns named[18638]: host unreachable resolving 'google.com/A/IN':
> 216.171.238.66#53
> Where the IP 216.171.238.66 is the ISP provided DNS server.
"host unreachable" is one of the clearer error messages, so yo
> Try
> dig @216.171.238.66 hp.com
> to see if the .66 host answers to your queries. Maybe you
> got a wrong IP
> there? Try the same for .67, the other DNS.
>
Thank you very much. I tried what you suggested and it seems that these two
servers work perfectly. In fact, I can simply set my DNS t
On Montag 21 September 2009 Shi Jin wrote:
> However, it looks to me like the ISP provided DNS server
> (216.171.238.66) was not able to resolve any of the names and all the
> resolving is done at the top level servers. Is my understanding
> correct?
Try
dig @216.171.238.66 hp.com
to see if the .6
dhcp-dns named[18638]: host unreachable resolving 'google.com/A/IN':
216.171.238.66#53
Where the IP 216.171.238.66 is the ISP provided DNS server.
My named.conf.options looks like
forwarders {
216.171.238.66;
216.171.238.67;
};
listen-on-v6 { n
On Tue, May 5, 2009 at 5:41 PM, Jeremy C. Reed wrote:
> On Tue, 5 May 2009, alexus wrote:
>
>> i just deployed new bind-9.6.0-p1
>>
>> and I'm getting a lot of these:
>>
>> May 5 20:18:41 dd named[21037]: host unreachable resolving
>> '128.23
On Tue, 5 May 2009, alexus wrote:
> i just deployed new bind-9.6.0-p1
>
> and I'm getting a lot of these:
>
> May 5 20:18:41 dd named[21037]: host unreachable resolving
> '128.235.241.88.zen.spamhaus.org/TXT/IN': 2001:7b8:3:1f:0:2:53:1#53
If you have IPv6
i just deployed new bind-9.6.0-p1
and I'm getting a lot of these:
May 5 20:18:41 dd named[21037]: host unreachable resolving
'128.235.241.88.zen.spamhaus.org/TXT/IN': 2001:7b8:3:1f:0:2:53:1#53
___
bind-users mailing list
bind-user
13 matches
Mail list logo
