<HTML dir=ltr><HEAD><TITLE>[Pdns-users] problems resolving 'juniper.net' in 3.1.5?</TITLE>
<META http-equiv=Content-Type content="text/html; charset=unicode">
<META content="MSHTML 6.00.6000.16640" name=GENERATOR></HEAD>
<BODY>
<DIV id=idOWAReplyText55293 dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2>Bert,</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>Have another domain that seems to have stopped functioning:</FONT></DIV>
<DIV dir=ltr> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>credcoservices.com</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>It appears to not attempt to recurse to the other dns server. Which is ns1.easydns.com. And thus just fails. I did a dig and you can see that ns2.easydns.com fails and thus the recursor fails never trying ns1.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>**PRODUCTION 1.01 ** ANC(fw/dns):/root>dig @ns2.easydns.com credcoservices.com<BR><BR>; <<>> DiG 9.2.4 <<>> @ns2.easydns.com credcoservices.com<BR>;; global options: printcmd<BR>;; connection timed out; no servers could be reached<BR>**PRODUCTION 1.01 ** ANC(fw/dns):/root>dig @ns1.easydns.com credcoservices.com<BR><BR>; <<>> DiG 9.2.4 <<>> @ns1.easydns.com credcoservices.com<BR>;; global options: printcmd<BR>;; Got answer:<BR>;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 51816<BR>;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 4<BR><BR>;; QUESTION SECTION:<BR>;credcoservices.com. IN A<BR><BR>;; ANSWER SECTION:<BR>credcoservices.com. 10800 IN A 66.203.97.50<BR><BR>;; AUTHORITY SECTION:<BR>credcoservices.com. 10800 IN NS ns2.easydns.com.<BR>credcoservices.com. 10800 IN NS remote1.easydns.com.<BR>credcoservices.com. 10800 IN NS remote2.easydns.com.<BR>credcoservices.com. 10800 IN NS ns1.easydns.com.<BR><BR>;; ADDITIONAL SECTION:<BR>ns1.easydns.com. 3600 IN A 66.225.199.10<BR>ns2.easydns.com. 3600 IN A 72.52.2.1<BR>remote1.easydns.com. 3600 IN A 209.200.131.4<BR>remote2.easydns.com. 3600 IN A 66.252.1.10<BR><BR>;; Query time: 50 msec<BR>;; SERVER: 66.225.199.10#53(ns1.easydns.com)<BR>;; WHEN: Sat Apr 19 20:44:34 2008<BR>;; MSG SIZE rcvd: 204<BR></FONT></DIV><FONT face=Arial size=2></FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2>Hope this helps.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>Brad Dameron</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2>Clearw're</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2>Senior Systems Engineer</FONT></DIV>
<DIV dir=ltr><BR>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> pdns-users-bounces@mailman.powerdns.com on behalf of bert hubert<BR><B>Sent:</B> Fri 4/18/2008 8:10 AM<BR><B>To:</B> pdns-users@mailman.powerdns.com<BR><B>Subject:</B> [Pdns-users] problems resolving 'juniper.net' in 3.1.5?<BR></FONT><BR></DIV>
<DIV>
<P><FONT size=2>Hi everybody,<BR><BR>Over at #powerdns on IRCnet we are currently trying to debug a problem where<BR>heavily loaded PowerDNS 3.1.5 recursors are unable to resolve the<BR>juniper.net domain name.<BR><BR>Could 3.1.5 users please try to resolve www.juniper.net, and if they find<BR>that there is a problem, see if you can get PowerDNS to provide you with a<BR>--trace.<BR><BR>this can be done for example by adding 'trace' to the configuration file,<BR>--trace to the commandline, or by sending signal USR2 to the pdns_recursor<BR>binary.<BR><BR>Be warned that this will generate TREMENDOUS amounts of logfiles.<BR><BR>Thanks!<BR><BR><BR>--<BR><A href="http://www.powerdns.com/">http://www.PowerDNS.com</A> Open source, database driven DNS Software<BR><A href="http://netherlabs.nl/">http://netherlabs.nl</A> Open and Closed source services<BR>_______________________________________________<BR>Pdns-users mailing list<BR>Pdns-users@mailman.powerdns.com<BR><A href="http://mailman.powerdns.com/mailman/listinfo/pdns-users">http://mailman.powerdns.com/mailman/listinfo/pdns-users</A><BR></FONT></P></DIV></BODY></HTML>