[Pdns-users] problems resolving 'juniper.net' in 3.1.5?

[Brad Dameron]

Bert,
 
Have another domain that seems to have stopped functioning:
 
credcoservices.com
 
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.
 
**PRODUCTION 1.01 ** ANC(fw/dns):/root>dig @ns2.easydns.com credcoservices.com

; <<>> DiG 9.2.4 <<>> @ns2.easydns.com credcoservices.com
;; global options:  printcmd
;; connection timed out; no servers could be reached
**PRODUCTION 1.01 ** ANC(fw/dns):/root>dig @ns1.easydns.com credcoservices.com

; <<>> DiG 9.2.4 <<>> @ns1.easydns.com credcoservices.com
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 51816
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 4

;; QUESTION SECTION:
;credcoservices.com.        IN    A

;; ANSWER SECTION:
credcoservices.com.    10800    IN    A    66.203.97.50

;; AUTHORITY SECTION:
credcoservices.com.    10800    IN    NS    ns2.easydns.com.
credcoservices.com.    10800    IN    NS    remote1.easydns.com.
credcoservices.com.    10800    IN    NS    remote2.easydns.com.
credcoservices.com.    10800    IN    NS    ns1.easydns.com.

;; ADDITIONAL SECTION:
ns1.easydns.com.    3600    IN    A    66.225.199.10
ns2.easydns.com.    3600    IN    A    72.52.2.1
remote1.easydns.com.    3600    IN    A    209.200.131.4
remote2.easydns.com.    3600    IN    A    66.252.1.10

;; Query time: 50 msec
;; SERVER: 66.225.199.10#53(ns1.easydns.com)
;; WHEN: Sat Apr 19 20:44:34 2008
;; MSG SIZE  rcvd: 204

Hope this helps.
 
Brad Dameron
Clearw're
Senior Systems Engineer

________________________________

From: pdns-users-bounces at mailman.powerdns.com on behalf of bert hubert
Sent: Fri 4/18/2008 8:10 AM
To: pdns-users at mailman.powerdns.com
Subject: [Pdns-users] problems resolving 'juniper.net' in 3.1.5?



Hi everybody,

Over at #powerdns on IRCnet we are currently trying to debug a problem where
heavily loaded PowerDNS 3.1.5 recursors are unable to resolve the
juniper.net domain name.

Could 3.1.5 users please try to resolve www.juniper.net, and if they find
that there is a problem, see if you can get PowerDNS to provide you with a
--trace.

this can be done for example by adding 'trace' to the configuration file,
--trace to the commandline, or by sending signal USR2 to the pdns_recursor
binary.

Be warned that this will generate TREMENDOUS amounts of logfiles.

Thanks!


--
http://www.PowerDNS.com <http://www.powerdns.com/>       Open source, database driven DNS Software
http://netherlabs.nl <http://netherlabs.nl/>               Open and Closed source services
_______________________________________________
Pdns-users mailing list
Pdns-users at mailman.powerdns.com
http://mailman.powerdns.com/mailman/listinfo/pdns-users


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.powerdns.com/pipermail/pdns-users/attachments/20080419/e2c309f3/attachment-0001.html>