Help to identify Microsoft DNS version

2012-01-09 Thread babu dheen
Dear All,    Can anyone help me how to find bind & microsoft DNS software version using dig or nslookup command remotely?   Regards Babu___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing

Is bind support conditionally resolution?

2012-01-09 Thread Drunkard Zhang
I am designing a big deploy system, which will implement via DNS. The demond is misc, one of them is conditionally resolve, which means that if one CDN node near unavailable, or latency increased significantly, no matter why, I want bind to give another second best result, which located in distant

Re: NAPTR Catch-all

2012-01-09 Thread Doug
Hi, Okay, *. works perfectly, however, I need to limit the queries to specific numbers. As an example 0.0.1.0.9.6.4.1.2.7.2.domain1.com 3.8.6.2.7.4.7.2.8.7.2.domain2.net 8.1.5.1.0.5.3.7.8.7.2.domain3 As per above, the number portion [0-9].[0-9]... will need to be specific, while the domain port

Re: NAPTR Catch-all

2012-01-09 Thread Doug
Hi, Okay, *. works perfectly, however, I need to limit the queries to specific numbers. As an example 0.0.1.0.9.6.4.1.2.7.2.domain1.com 3.8.6.2.7.4.7.2.8.7.2.domain2.net 8.1.5.1.0.5.3.7.8.7.2.domain3 As per above, the number portion [0-9].[0-9]... will need to be specific, while the domain port

Re: NAPTR Catch-all

2012-01-09 Thread Florian Weimer
> I did try the following: > > 7.7.7.5.2.1.4.4.9.9.8.1.2.* The "*" wildcard must be the first label. ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https

Re: NAPTR Catch-all

2012-01-09 Thread Doug
Hi, I did try the following: 7.7.7.5.2.1.4.4.9.9.8.1.2.* Which sadly did not work. Below is an example of queries that I would typically need to process. In all examples, the number will be the same, its just the domain portion that will change based on the environment: 7.7.7.5.2.1.4.4.9.9.8.1

Bind to INADDR_ANY

2012-01-09 Thread Bostjan Skufca
Hi everyone, is binding to all interfaces at once already supported in bind9? I know named binds to each at-the-moment-available IP address but in HA environment with virtual interfaces a "rndc reload" is necessary for named to pick up a new interface, which leaves a bit of a window of unavailable

Re: Exercising RFC 5011 rollovers

2012-01-09 Thread Evan Hunt
On Mon, Jan 09, 2012 at 09:40:51PM +, Chris Thompson wrote: > | If the resolver ever sees the DNSKEY RRSet without the new key but > | validly signed, it stops the acceptance process for that key and > | resets the acceptance timer. > > What BIND does is to retain the entry for the new key in

BIND 9.9.0rc1 is now available

2012-01-09 Thread Michael McNally
Introduction BIND 9.9.0rc1 is the first release candidate for BIND 9.9. This document summarizes changes from BIND 9.8 to BIND 9.9. Please see the CHANGES file in the source code release for a complete list of all changes. Download The latest versions of BIND

certain records not being returned from cache?

2012-01-09 Thread Ian Veach
Greetings and thanks for any help - I'm running into what seems like a strange problem. On our bind (9.7.3-P3-RedHat-9.7.3-2.el6_1.P3.3, but patched to latest), we seem to be having some domains [we aren't auth for] that aren't returning expected information from cache (although thousand of other

Re: RFC 6303 vs. BIND: NS ... has no address records (A or AAAA)

2012-01-09 Thread Doug Barton
On 01/09/2012 14:13, Irwin Tillman wrote: > RFC 6303 says that a recursive nameserver should locally serve > a number of DNS zones. Section 3 provides this generic empty > zone for this purpose, in master file format: > > @ 10800 IN SOA @ nobody.invalid. 1 3600 1200 604800 10800 > @ 10800 IN NS

RFC 6303 vs. BIND: NS ... has no address records (A or AAAA)

2012-01-09 Thread Irwin Tillman
RFC 6303 says that a recursive nameserver should locally serve a number of DNS zones. Section 3 provides this generic empty zone for this purpose, in master file format: @ 10800 IN SOA @ nobody.invalid. 1 3600 1200 604800 10800 @ 10800 IN NS @ The RFC notes: "The NS RR is needed as some UPDAT

Re: Exercising RFC 5011 rollovers

2012-01-09 Thread Chris Thompson
Back in November, I started a thread about testing BIND's managed-keys code for tracking trust anchor rollovers. Since then I have been doing some experiments which, as pointed out then, can take quite some time due to the 30-day "hold-down" times specified in RFC 5011. Recently I thought I had d

Re: NAPTR Catch-all

2012-01-09 Thread Florian Weimer
> 7.7.7.5.2.1.4.4.9.9.8.1.2.INNAPTR10010"u" "E2U+sip" > "!(^.*$)!sip:2799820784000132" .; Testing This isn't a wildcard, so it will not match as a wildcard. Can you provide a few example RRs which you want to synthesize using wildcards? It's not clear (to me at least)

Re: forwarding "@" to a different domain?

2012-01-09 Thread enigmedia (onl)
On Mon, 9 Jan 2012 15:11:19 + "Lightner, Jeff" wrote Just as a follow on to that prior thread. I was able to setup the CNAME for www and * at the Registrar without A records as indicated. Unfortunately the * at registrar equated to "*." Meaning for example ftp.mydomain.com would wor

RE: forwarding "@" to a different domain?

2012-01-09 Thread Lightner, Jeff
Just as a follow on to that prior thread. I was able to setup the CNAME for www and * at the Registrar without A records as indicated. Unfortunately the * at registrar equated to "*." Meaning for example ftp.mydomain.com would work with that CNAME but the domain itself, mydomain.com, would not

NAPTR Catch-all

2012-01-09 Thread Doug
Hi Everyone. I've been trying to get a solution working where by I need to supply a response based on a NAPTR query. The problem is, the domain section of the NAPTR needs to be "dynamic", as this could be different per query. I based my config on the following url, and all works well for A record

Re: ddns and views

2012-01-09 Thread Phil Mayers
On 01/09/2012 07:42 AM, Psychobyte wrote: Sorry, I didn't mean rndc I meant DDNS updates. in particular using the Perl Net::DNS module. DDNS works the same way as every other DNS packet with views; the "view" "match" statement determines which view you are talking to. The match statement ca