Re: Facebook
Joe Baptista <[email protected]>
| Newsgroups | gmane.network.djbdns |
|---|---|
| Message-ID | <[email protected]> |
On Wed, Mar 10, 2010 at 1:20 PM, Matthew Dempsky <[email protected]>wrote: > On Wed, Mar 10, 2010 at 8:36 AM, Joe Baptista <[email protected]> > wrote: > > The misconfiguration is at facebook.com. > > For anyone interested in details, the issue here is that two of > facebook.com's name servers are in the tfbnw.net zone while all of > tfbnw.net's name servers are in the facebook.com zone. > I double checked. There is no misconfiguration. But your explanation is not correct or is confused. The facebook.com NS are as follows: facebook.com. 172800 IN NS dns04.sf2p.tfbnw.net. facebook.com. 172800 IN NS dns05.sf2p.tfbnw.net. facebook.com. 172800 IN NS ns1.facebook.com. facebook.com. 172800 IN NS ns2.facebook.com. but www.facebook.com is not in the facebook zone. It has it's own set of DNS servers - i.e.: www.facebook.com. 491 IN NS glb01.hkg1.tfbnw.net. www.facebook.com. 491 IN NS glb01.snc1.tfbnw.net. www.facebook.com. 491 IN NS glb01.dfw1.tfbnw.net. www.facebook.com. 491 IN NS glb01.sf2p.tfbnw.net. www.facebook.com. 491 IN NS glb01.lhr1.tfbnw.net. www.facebook.com. 491 IN NS glb01.ash1.tfbnw.net. www.facebook.com. 491 IN NS glb01.ams1.tfbnw.net. > > dnscache always tries to resolve all of a zone's name servers before > attempting to resolve any names within that zone, so this zone > dependency loop results in dnscache spending a lot of extra effort > trying to track down the missing glue records. > > That said, I was able to resolve www.facebook.com using dnscache, just > not on the first attempt. I can imagine it failing repeatedly on a > busy resolver though. > That could be an issue. regards joe