Re: dig +trace to find all the forwarders?

2010-04-26 Thread Josh Kuo
What is happening is I suspect the DNS resolved IP given by my ISP is actually forwarding recursive queries to yet-another-server(s), and is introducing slow name resolution and timeouts. In any case, I will have to involve the ISP in troubleshooting and (hopefully) fixing the problem. I was hoping

RE: one record to be redirected to a specific IP

2010-04-26 Thread hugo hugoo
What I want to do is redirect a site to a specific IP using DNS (this kind of request comes from the Justice). This specific IP can be an internal website with a warning message for example. So I need to could redirect www.abcd.com for example to a specific IP 1.2.3.4 for example. This red

Re: one record to be redirected to a specific IP

2010-04-26 Thread Sten Carlsen
I wonder if the following could be done: - make the zone for www.abcd.com, which would also redirect the "anything else" part. - delegate the "anything else" back to its original owner. like: www.abcd.com. soa @ IN A1.2.3.4 * NS I am not sure this could work? I am not

Re: one record to be redirected to a specific IP

2010-04-26 Thread Torsten
Am Mon, 26 Apr 2010 11:30:26 +0200 schrieb Sten Carlsen : > I wonder if the following could be done: > > - make the zone for www.abcd.com, which would also redirect the > "anything else" part. > - delegate the "anything else" back to its original owner. > > like: > > www.abcd.com. soa >

Re: one record to be redirected to a specific IP

2010-04-26 Thread Phil Mayers
On 26/04/10 12:44, Torsten wrote: Am Mon, 26 Apr 2010 11:30:26 +0200 schrieb Sten Carlsen: I wonder if the following could be done: - make the zone for www.abcd.com, which would also redirect the "anything else" part. - delegate the "anything else" back to its original owner. like: www.abcd.

Re: dig +trace to find all the forwarders?

2010-04-26 Thread Warren Kumari
On Apr 26, 2010, at 3:10 AM, Josh Kuo wrote: What is happening is I suspect the DNS resolved IP given by my ISP is actually forwarding recursive queries to yet-another-server(s), and is introducing slow name resolution and timeouts. Well, if you are just trying to figure out if the nameserver

RE: dig +trace to find all the forwarders?

2010-04-26 Thread Lightner, Jeff
? That link only shows the IP you came from and does a reverse lookup on it. It doesn't seem to say anything about the nameserver. -Original Message- From: bind-users-bounces+jlightner=water@lists.isc.org [mailto:bind-users-bounces+jlightner=water@lists.isc.org] On Behalf Of Warr

Re: Caching DNS server (bind9.4.2) CPU usage is so so so high.

2010-04-26 Thread Dave Sparro
On 4/25/2010 10:23 PM, Trần Trọng Tấn wrote: Hi, I have a caching-only dns server which get ~3k queries per second. Here is specs: |Xeon dual-core2,8GHz 4GB of RAM Centos 5x 32bit(kernel2.6.18-164.15.1.el5PAE) bind9.4.2 | rndc status: recursive clients: 666/4900/5000 Bind always uses

Re: dig +trace to find all the forwarders?

2010-04-26 Thread Warren Kumari
On Apr 26, 2010, at 10:41 AM, Lightner, Jeff wrote: ? That link only shows the IP you came from and does a reverse lookup on it. It doesn't seem to say anything about the nameserver. Does it? Are you sure? If so, I sent the wrong link -- the machine I was testing from is also a nameser

RE: dig +trace to find all the forwarders?

2010-04-26 Thread Lightner, Jeff
I'm sure that's all it displayed when I went to it from my Windows desktop's browser. -Original Message- From: Warren Kumari [mailto:war...@kumari.net] Sent: Monday, April 26, 2010 2:20 PM To: Lightner, Jeff Cc: Josh Kuo; bind-us...@isc.org Subject: Re: dig +trace to find all the forwarde

Re: dig +trace to find all the forwarders?

2010-04-26 Thread Warren Kumari
On Apr 26, 2010, at 2:54 PM, Lightner, Jeff wrote: I'm sure that's all it displayed when I went to it from my Windows desktop's browser. Uuuummm Are you maybe behind the same NAT that your recursive resolver is behind and so your IP == your resolvers IP? Or is your Windows desktop al

RE: dig +trace to find all the forwarders?

2010-04-26 Thread Lightner, Jeff
I'm certainly behind a NAT and the IP reported is the NATed IP. Maybe I missed the point in the site. Is it to report the name server your IP exist on (the one it returned the reverse lookup for) or is it intended to run only from a name server? If the latter I don't see the point of the site.

Re: dig +trace to find all the forwarders?

2010-04-26 Thread Kevin Darcy
On 4/25/2010 12:01 AM, Josh Kuo wrote: You need administrative access to see the overides to the normal resolution process. Just so I understand this completely, by administrative access you mean I need to be able to log in to each of the resolvers (not administrative access on m

Re: dig +trace to find all the forwarders?

2010-04-26 Thread Warren Kumari
On Apr 26, 2010, at 4:00 PM, Lightner, Jeff wrote: I'm certainly behind a NAT and the IP reported is the NATed IP. And is the recursive resolver that you are using ALSO behind the same NATed IP?! Maybe I missed the point in the site. Is it to report the name server your IP exist on

Re: dig +trace to find all the forwarders?

2010-04-26 Thread Barry Margolin
In article , Warren Kumari wrote: > On Apr 26, 2010, at 3:10 AM, Josh Kuo wrote: > > > What is happening is I suspect the DNS resolved IP given by my ISP is > > actually forwarding recursive queries to yet-another-server(s), and is > > introducing slow name resolution and timeouts. > > Well, i