<html><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:12px"><div id="yui_3_16_0_1_1434024906961_1822241"><span>Hello,</span></div><div><br><span></span></div><div style="" class="" id="yui_3_16_0_1_1434024906961_1817003">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?</div><div style="" class="" id="yui_3_16_0_1_1434024906961_1817187">That is, <br style="" class=""></div><div style="" class="" id="yui_3_16_0_1_1434024906961_1818130">  nslookup google.com.</div><div style="" class="" id="yui_3_16_0_1_1434024906961_1817135"><br style="" class=""><span style="" class="" id="yui_3_16_0_1_1434024906961_1817088"></span></div><div style="" class="" id="yui_3_16_0_1_1434024906961_1817983" dir="ltr"><span style="" class="" id="yui_3_16_0_1_1434024906961_1817088">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.</span><br style="" class=""><span style="" class="" id="yui_3_16_0_1_1434024906961_1817088"></span></div><div style="" class="" id="yui_3_16_0_1_1434024906961_1817982"><span style="" class="" id="yui_3_16_0_1_1434024906961_1817088"><br style="" class=""></span></div><div style="" class="" id="yui_3_16_0_1_1434024906961_1817134"><span style="" class="" id="yui_3_16_0_1_1434024906961_1817088">If the mystery continues, one can turn on nslookup debugging via:<br style="" class=""></span></div><div style="" class="" id="yui_3_16_0_1_1434024906961_1817089"><span style="" class="" id="yui_3_16_0_1_1434024906961_1817088">  set d2</span></div><div style="" class="" id="yui_3_16_0_1_1434024906961_1817933" dir="ltr"><span style="" class="" id="yui_3_16_0_1_1434024906961_1817088">whose additional output may explain what is going on.<br style="" class=""></span></div><div style="" class="" id="yui_3_16_0_1_1434024906961_1817852" dir="ltr"><span style="" class="" id="yui_3_16_0_1_1434024906961_1817088"><br style="" class=""></span></div><div id="yui_3_16_0_1_1434024906961_1822389" dir="ltr">  I hope this helps.  </div><div id="yui_3_16_0_1_1434024906961_1822388" style="" class=""><span style="" class=""><br style="" class=""></span></div><br><div class="qtdSeparateBR"><br><br></div><div style="display: block;" class="yahoo_quoted"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 12px;"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;"> <div dir="ltr"> <font face="Arial" size="2"> On Monday, June 22, 2015 8:40 AM, Fr34k <freaknetboy@yahoo.com> wrote:<br> </font> </div>  <br><br> <div class="y_msg_container"><div id="yiv7950644924"><div><div style="color:#000;background-color:#fff;font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:12px;"><div id="yiv7950644924yui_3_16_0_1_1434024906961_1817003">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.</div><div id="yiv7950644924yui_3_16_0_1_1434024906961_1817187">That is, <br clear="none"></div><div id="yiv7950644924yui_3_16_0_1_1434024906961_1818130">  nslookup google.com.</div><div id="yiv7950644924yui_3_16_0_1_1434024906961_1817135"><br clear="none"><span id="yiv7950644924yui_3_16_0_1_1434024906961_1817088"></span></div><div dir="ltr" id="yiv7950644924yui_3_16_0_1_1434024906961_1817983"><span class="yiv7950644924" id="yiv7950644924yui_3_16_0_1_1434024906961_1817088" style="">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.</span><br clear="none"><span id="yiv7950644924yui_3_16_0_1_1434024906961_1817088"></span></div><div id="yiv7950644924yui_3_16_0_1_1434024906961_1817982"><span id="yiv7950644924yui_3_16_0_1_1434024906961_1817088"><br clear="none"></span></div><div id="yiv7950644924yui_3_16_0_1_1434024906961_1817134"><span id="yiv7950644924yui_3_16_0_1_1434024906961_1817088">If the mystery continues, one can turn on debugging via:<br clear="none"></span></div><div id="yiv7950644924yui_3_16_0_1_1434024906961_1817089"><span id="yiv7950644924yui_3_16_0_1_1434024906961_1817088">  set d2</span></div><div dir="ltr" id="yiv7950644924yui_3_16_0_1_1434024906961_1817933"><span id="yiv7950644924yui_3_16_0_1_1434024906961_1817088">whose additional output may explain what is going on.<br clear="none"></span></div><div dir="ltr" id="yiv7950644924yui_3_16_0_1_1434024906961_1817852"><span id="yiv7950644924yui_3_16_0_1_1434024906961_1817088"></span></div>  <br clear="none"><div class="yiv7950644924qtdSeparateBR" id="yiv7950644924yui_3_16_0_1_1434024906961_1817304"><br clear="none"><br clear="none"></div><div class="yiv7950644924yqt4972862141" id="yiv7950644924yqt08082"><div class="yiv7950644924yahoo_quoted" id="yiv7950644924yui_3_16_0_1_1434024906961_1819313" style="display:block;"> <div id="yiv7950644924yui_3_16_0_1_1434024906961_1819312" style="font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:12px;"> <div id="yiv7950644924yui_3_16_0_1_1434024906961_1819311" style="font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:16px;"> <div dir="ltr"> <font face="Arial" size="2"> On Monday, June 22, 2015 7:36 AM, Niall O'Reilly <niall.oreilly@ucd.ie> wrote:<br clear="none"> </font> </div>  <br clear="none"><br clear="none"> <div class="yiv7950644924y_msg_container" id="yiv7950644924yui_3_16_0_1_1434024906961_1819310">On Mon, 22 Jun 2015 12:07:31 +0100,<br clear="none">Zelalem Fanta Woldesemayat wrote:<br clear="none">> <br clear="none">> Dear all,<br clear="none">> <br clear="none">> I’ve configured BIND 9.9.4. as a cache only server on our DMZ so that<br clear="none">> it can serve as a DNS server for the internal network. Inside the DMZ<br clear="none">> zone the request time out is very fast and the DNS service resolves<br clear="none">> very quickly. But the problem is from the inside network. When I tried<br clear="none">> nslookup it gives the following message. Would you please help me to<br clear="none">> resolve this issue.<br clear="none"><br clear="none">  Perhaps you need to configure named to allow access from the client<br clear="none">  network.  The ISC Knowledge Base has an article which may be useful:<br clear="none">  <a rel="nofollow" shape="rect" target="_blank" href="https://kb.isc.org/article/AA-00269/0/What-has-changed-in-the-behavior-of-allow-recursion-and-allow-query-cache.html">https://kb.isc.org/article/AA-00269/0/What-has-changed-in-the-behavior-of-allow-recursion-and-allow-query-cache.html</a><br clear="none"><br clear="none">  Best regards,<br clear="none">  Niall O'Reilly<div class="yiv7950644924yqt0416960752" id="yiv7950644924yqtfd39238"><br clear="none">  <br clear="none">_______________________________________________<br clear="none">Please visit <a rel="nofollow" shape="rect" target="_blank" href="https://lists.isc.org/mailman/listinfo/bind-users">https://lists.isc.org/mailman/listinfo/bind-users </a>to unsubscribe from this list<br clear="none"><br clear="none">bind-users mailing list<br clear="none"><a rel="nofollow" shape="rect" ymailto="mailto:bind-users@lists.isc.org" target="_blank" href="mailto:bind-users@lists.isc.org">bind-users@lists.isc.org</a><br clear="none"><a rel="nofollow" shape="rect" target="_blank" href="https://lists.isc.org/mailman/listinfo/bind-users">https://lists.isc.org/mailman/listinfo/bind-users</a></div><br clear="none"><br clear="none"></div>  </div> </div>  </div></div></div></div></div><br><br></div>  </div> </div>  </div></div></body></html>