Reverse DNS Dig returning PTR results only with trace option

2009-11-10 Thread Raj Adhikari
Hi Guys, I have a 63.254.134.224/28 delegated from ns1.cyzap.net to ns1.moneytreesystems.com. The dig with trace only shows the PTR record. Surprisingly, it starts acting normal after I do the dig on ns1.cyzap.net. See the dig output below. Here is the output: Simple dig to 63.254.234.228. $ dig

Re: Reverse DNS Dig returning PTR results only with trace option

2009-11-10 Thread Chris Hills
On 10/11/09 18:25, Raj Adhikari wrote: Now I can do a dig for an hour or so. But again I run into same problem. It wont return PTR record unless I explicitly do dig on ns1.cyzap.net. Also, the last did showing ns1.cyzap.net as Authority NS for this IP. But trace showing ns1.moneytreesystems.com

Re: Reverse DNS Dig returning PTR results only with trace option

2009-11-10 Thread Kevin Darcy
It's worse than that. Sometimes RD doesn't even get copied into the response header. I suspect there's a load-balancer in front here, and at least one bad, non-BIND nameserver behind it, spewing out nasty stuff like horizontal delegations... Either that, or some middlebox is munging the

Re: Reverse DNS Dig returning PTR results only with trace option

2009-11-10 Thread Raj Adhikari
Thanks Chris for the reply. Actually, let me put my question the other way. How can one delegate the classless subnet to other DNS? Actually, one of our ISP could not delegate classless subnet to our server ns1.cyzap.net. I am trying to help them in delegating the classless subnet to us. So this

Re: Reverse DNS Dig returning PTR results only with trace option

2009-11-10 Thread Mark Andrews
In message 4af9a220.9070...@cyzap.com, Raj Adhikari writes: Hi Guys, I have a 63.254.134.224/28 delegated from ns1.cyzap.net to ns1.moneytreesystems.com. The dig with trace only shows the PTR record. Surprisingly, it starts acting normal after I do the dig on ns1.cyzap.net. See the dig

Re: Reverse DNS Dig returning PTR results only with trace option

2009-11-10 Thread Kevin Darcy
Raj Adhikari wrote: Thanks Chris for the reply. Actually, let me put my question the other way. How can one delegate the classless subnet to other DNS? Actually, one of our ISP could not delegate classless subnet to our server ns1.cyzap.net. I am trying to help them in delegating the classless

Re: bind configuration help

2009-11-10 Thread Laurent CARON
On 10/11/2009 23:07, Błażej Ślusarek wrote: Hello, Hi I'd like to ask for help in setting up my DNS server. When I start the server, everything is fine, but only for some time. After the some time passes, my external domain name cannot be resolved from anywhere on the Internet. When I

Re: Reverse DNS Dig returning PTR results only with trace option

2009-11-10 Thread Kevin Darcy
Raj Adhikari wrote: Yes, they both are non-BIND servers, actually using Windows DNS servers. I have delegated *each*in-addr*arpa*name* from cyzap to monetreeysystems. Nope. $ dig -x 63.254.134.228 soa @ns1.moneytreesystems.com ; DiG 9.3.5-P2 -x 63.254.134.228 soa

Re: bind configuration help

2009-11-10 Thread Błażej Ślusarek
Sorry, but could You specify more accurately what is bad ? This is my first bind configuration, so probably I've made some mistakes, but I'd like to do it the right way in the end.:) On Tue, Nov 10, 2009 at 11:19 PM, Laurent CARON lca...@lncsa.com wrote: On 10/11/2009 23:07, Błażej Ślusarek

Re: Reverse DNS Dig returning PTR results only with trace option

2009-11-10 Thread Mark Andrews
In message 4af9dfba.6040...@cyzap.com, Raj Adhikari writes: Thanks Chris for the reply. Actually, let me put my question the other way. How can one delegate the classless subnet to other DNS? Actually, one of our ISP could not delegate classless subnet to our server ns1.cyzap.net. I am

Re: Reverse DNS Dig returning PTR results only with trace option

2009-11-10 Thread Raj Adhikari
Kevin Wrote: {QUOTE} There is no BIND way versus Windows way. For a range smaller than /24 you either need to host all the records in the /24 zone, delegate each entry individually (as /32 zones), or use CNAMEs. This is determined by the protocol, regardless of whether you're using Microsoft DNS,