windows client request timed out

2015-06-22 Thread Zelalem Fanta Woldesemayat 
Dear all,
I've configured BIND 9.9.4. as a cache only server on our DMZ so that it can 
serve as a DNS server for the internal network. Inside the DMZ zone the request 
time out is very fast and the DNS service resolves very quickly. But the 
problem is from the inside network. When I tried nslookup it gives the 
following message. Would you please help me to resolve this issue.

> google.com
Server:  [172.16.2.11]
Address:  172.16.2.11

DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
Non-authoritative answer:
Name:google.com
Addresses:  2a00:1450:400c:c0b::8a
  64.233.184.139
  64.233.184.102
  64.233.184.101
  64.233.184.138
  64.233.184.100
  64.233.184.113

Best Regards,

[VC-39_EmailSignature_3]

Zelalem Fanta | Systems Administrator

Plot #30, May Avenue, Juba, South Sudan
Mob: +211 95 950 2224 -  Tel: +211 95 960 2224
zfa...@vivacell.com | 
www.vivacell.com

___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe 
from this list

bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users

Re: windows client request timed out

2015-06-22 Thread Niall O'Reilly 
On Mon, 22 Jun 2015 12:07:31 +0100,
Zelalem Fanta Woldesemayat wrote:
> 
> Dear all,
> 
> I’ve configured BIND 9.9.4. as a cache only server on our DMZ so that
> it can serve as a DNS server for the internal network. Inside the DMZ
> zone the request time out is very fast and the DNS service resolves
> very quickly. But the problem is from the inside network. When I tried
> nslookup it gives the following message. Would you please help me to
> resolve this issue.

  Perhaps you need to configure named to allow access from the client
  network.  The ISC Knowledge Base has an article which may be useful:
  
https://kb.isc.org/article/AA-00269/0/What-has-changed-in-the-behavior-of-allow-recursion-and-allow-query-cache.html

  Best regards,
  Niall O'Reilly
  
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe 
from this list

bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users

Re: windows client request timed out

2015-06-22 Thread Fr34k 
Hello,
How about putting a dot at the end of the query hostname so that Windows 
doesn't add whatever the domain name suffix/es the Windows client may be 
configured with?That is, 
  nslookup google.com.
It may be the case that the windows client is adding whatever domain name 
suffix/es it is configured with (e.g., google.com.vivacell.com) and perhaps 
those queries are timing out until it finally tries google.com.

If the mystery continues, one can turn on nslookup debugging via:
  set d2whose additional output may explain what is going on.

 I hope this helps. 



 On Monday, June 22, 2015 8:40 AM, Fr34k  wrote:
   

 Put a dot at the end of the lookup so that Windows doesn't added whatever the 
domain name suffix/es it may be configured with.That is, 
  nslookup google.com.
I suspect the windows client is adding whatever the domain name suffix/es are 
(e.g., google.com.vivacell.com) and perhaps those are timing out until it 
finally tries google.com.

If the mystery continues, one can turn on debugging via:
  set d2whose additional output may explain what is going on.
 


 On Monday, June 22, 2015 7:36 AM, Niall O'Reilly  
wrote:
   

 On Mon, 22 Jun 2015 12:07:31 +0100,
Zelalem Fanta Woldesemayat wrote:
> 
> Dear all,
> 
> I’ve configured BIND 9.9.4. as a cache only server on our DMZ so that
> it can serve as a DNS server for the internal network. Inside the DMZ
> zone the request time out is very fast and the DNS service resolves
> very quickly. But the problem is from the inside network. When I tried
> nslookup it gives the following message. Would you please help me to
> resolve this issue.

  Perhaps you need to configure named to allow access from the client
  network.  The ISC Knowledge Base has an article which may be useful:
  
https://kb.isc.org/article/AA-00269/0/What-has-changed-in-the-behavior-of-allow-recursion-and-allow-query-cache.html

  Best regards,
  Niall O'Reilly
  
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe 
from this list

bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users

   

  ___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe 
from this list

bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users

Re: windows client request timed out

2015-06-22 Thread Fr34k 
Put a dot at the end of the query hostname so that Windows doesn't add whatever 
the domain name suffix/es the Windows client may be configured with.That is, 
  nslookup google.com.
It may be the case that the windows client is adding whatever domain name 
suffix/es it has been configured with (e.g., google.com.vivacell.com) and 
perhaps those queries are timing out until it finally tries google.com as the 
FQDN.

If a mystery remains, one can turn on nslookup debugging via:
  set d2whose additional output may explain what is going on.  That is, enter 
nslookup, then enter set d2, then enter a query such as google.com
Nslookup

|   |
|   |   |   |   |   |
| NslookupNslookup is a useful tool for troubleshooting DNS problems, such as 
host name resolution.  |
|  |
| View on technet.microsoft.com | Preview by Yahoo |
|  |
|   |


 I hope this helps.


 On Monday, June 22, 2015 7:36 AM, Niall O'Reilly  
wrote:
   

 On Mon, 22 Jun 2015 12:07:31 +0100,
Zelalem Fanta Woldesemayat wrote:
> 
> Dear all,
> 
> I’ve configured BIND 9.9.4. as a cache only server on our DMZ so that
> it can serve as a DNS server for the internal network. Inside the DMZ
> zone the request time out is very fast and the DNS service resolves
> very quickly. But the problem is from the inside network. When I tried
> nslookup it gives the following message. Would you please help me to
> resolve this issue.

  Perhaps you need to configure named to allow access from the client
  network.  The ISC Knowledge Base has an article which may be useful:
  
https://kb.isc.org/article/AA-00269/0/What-has-changed-in-the-behavior-of-allow-recursion-and-allow-query-cache.html

  Best regards,
  Niall O'Reilly
  
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe 
from this list

bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users

  ___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe 
from this list

bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users