Re: private tld

In message <20130820221524.ga24...@iano.org>, Maria writes: > My company uses a private tld. We are working on fixing that but the fix is > going to take a while, especially if our sol > ution ends up being trying to register it with icann. > > Our resolvers that all internet queries go through

Re: duplicate records

The answer is "none". All versions did duplicate elimination even back in the BIND 4 days. Mark In message <5213d1c3.3090...@chrysler.com>, Kevin Darcy writes: > > Since such behavior would flagrantly violate RFC 2181, Section 5, look > for a version prior to the publication date of that RFC

Re: Bind99 and a slave named server

Perhaps you should check that the master is running a nameserver and that it doesn't have firewalls blocking the DNS (both UDP and TCP). % dig soa covisp.net @75.148.117.92 ; <<>> DiG 9.10.0pre-alpha <<>> soa covisp.net @75.148.117.92 ;; global options: +cmd ;; connection timed out; no servers c

Re: Bind99 and a slave named server

On 20 Aug 2013, at 14:38 , Alan Clegg wrote: > To convert master to slave: [snip] > Bazinga! OK. Not Bazinga. $ grep covisp named.conf zone "covisp.net" { type slave; file "slave/covisp.net"; masters { 75.148.117.92; }; }; $ rndc status version: 9.9.3-P2 CPUs found: 2 worker threads: 2 UDP li

Re: Bind99 and a slave named server

On Aug 20, 2013, at 10:32 PM, LuKreme wrote: > I need the data in text because sometimes, the primary dns is down, and > sometimes it si down long enough to require that I switch the slave to be the > primary, and that means master. I can't do that if I don't have text records. Eh... You can

Re: private tld

DNSSEC sign the private TLD and configure its KSK as a trust anchor on the recursive resolvers. Alternatively, you can configure all your recursive resolvers as slaves for the private zone. Authoritative responses aren't validated on a mixed authoritative/recursive nameserver. Those are the only

Re: Bind99 and a slave named server

On Aug 20, 2013, at 7:35 PM, LuKreme wrote: >> zone example.com { >> type master;// I own this. >> file "files/example.com"; // Here's where I read them from >> }; >> >> it will become: >> >> zone example.com { >> type slave; // Now

Re: private tld

On Aug 20, 2013, at 6:15 PM, Maria wrote: > My company uses a private tld. We are working on fixing that but the fix is > going to take a while, especially if our solution ends up being trying to > register it with icann. > > Our resolvers that all internet queries go through have a forward z

Re: d root server

Have you read the source code for these versions of BIND and examined the set of HINTS that are internal to the code inside BIND? These are loaded before any external HINTS file is loaded up. Lyle On 08/20/13 16:37, rohan.he...@cwjamaica.com wrote: Lyle, Version 9.8.4-P1 is also affected. A

private tld

My company uses a private tld. We are working on fixing that but the fix is going to take a while, especially if our solution ends up being trying to register it with icann. Our resolvers that all internet queries go through have a forward zone statement for that tld to some internal name serve

Re: d root server

Lyle, Version 9.8.4-P1 is also affected. And the hints file was downloaded during setup. Also note that even a freshly downloaded copy has the old address. Note IP 199.7.91.13 in the following dig output. dig +tcp @a.root-servers.net . ns ; <<>> DiG 9.8.4-P1 <<>> +tcp @a.root-servers.net . ns

bind-users Digest, Vol 1603, Issue 5

Je suis absent jusqu'au 23 Août 2013 inclus. En cas d'urgence, vous pouvez contacter RASOAMANANA Ranto (Mob: +261320701232, e-mail: ranto.rasoaman...@orange.com). Confidentiality: This email is intended for the above-na

Re: d root server

Your bind code is old and has the old info in it. D root changed it's ip address. Bind has a built-in hints file, in case you don't setup one and it probably has the old ip address for the D root. http://blog.icann.org/2012/12/d-root/ Lyle Giese LCR Computer Services, Inc. On 08/20/13 15:44

Re: d root server

Edward, Agreed. My concern though is why the following show up in my logs when the IP is already in the root hint file. checkhints: d.root-servers.net/A (199.7.91.13) missing from hints Regards, Rohan On Tue, 20 Aug 2013 14:40:09 -0400 Edward DeLargy wrote: >Rohan, > Normally you s

Re: Bind99 and a slave named server

On Aug 20, 2013, at 2:36 PM, LuKreme wrote: > > On 18 Aug 2013, at 19:20 , Noel Butler wrote: > >> As has been said already, there is really very little to it, and unless you >> sent it to Alan off-list, you still have _NOT_ provided the error logs >> after being asked by more than one pe

Re: duplicate records

Since such behavior would flagrantly violate RFC 2181, Section 5, look for a version prior to the publication date of that RFC (July 1997). - Kevin On 8/20/2013 3:14 PM, Nidal Shater wrote: we know that BIND eleminate duplicate records, which version of BIND that doesn't do

bind-users Digest, Vol 1603, Issue 4

Je suis absent jusqu'au 23 Août 2013 inclus. En cas d'urgence, vous pouvez contacter RASOAMANANA Ranto (Mob: +261320701232, e-mail: ranto.rasoaman...@orange.com). Confidentiality: This email is intended for the above-na

Re: rrset-order code

On Aug 20, 2013, at 3:13 PM, Nidal Shater wrote: > we know in bind that we use rrset-order{ order random;}//where is the piece > of code that implement the random function in BIND9 > so i can edit it to reach my goal> Even if you force BIND to return an RRSET in a given order (look for the cod

duplicate records

we know that BIND eleminate duplicate records, which version of BIND that doesn't do that ? NIDAL ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mail

rrset-order code

HI I'm working on a DNS project, which is weighted load balancing DNS which depends on weight of a serveres that have the page we want to lookup to order the returned list of the IP. My question is: we know in bind that we use rrset-order{ order random;}//where is the piece of code that implemen

Re: Bind99 and a slave named server

On 18 Aug 2013, at 19:20 , Noel Butler wrote: > As has been said already, there is really very little to it, and unless you > sent it to Alan off-list, you still have _NOT_ provided the error logs > after being asked by more than one person. Thanks, I thought I was clear. I am *not* gettin

Re: d root server

Thanks Edward, I didn't think I needed to edit the downloaded root hint file. In fact the d.root-server.net server is assigned the IP address in the dig output below. I do not know where 128.8.10.90 comes from. dig d.root-servers.net ; <<>> DiG 9.7.2-P3 <<>> d.root-servers.net ;; global optio

d root server

Hello, Why do I still get the following in my logs even after downloading the latest version root hint file. checkhints: d.root-servers.net/A (128.8.10.90) extra record in hints checkhints: d.root-servers.net/A (199.7.91.13) missing from hints Regards, Rohan ___

bind-users Digest, Vol 1603, Issue 3

Je suis absent jusqu'au 23 Août 2013 inclus. En cas d'urgence, vous pouvez contacter RASOAMANANA Ranto (Mob: +261320701232, e-mail: ranto.rasoaman...@orange.com). Confidentiality: This email is intended for the above-na

Re: BIND 9.8.1-P1: 'make test' fails

On 20 Aug 2013, at 15:08, Chris Buxton wrote: > There is a mailing list for Net::DNS. > > List-Subscribe: , > > > That said, there was a discussion last December about what ha

Re: BIND 9.8.1-P1: 'make test' fails

On Aug 20, 2013, at 5:11 AM, Niall O'Reilly wrote: > On 22 Nov 2011, at 11:24, Niall O'Reilly wrote: > >> Since quite a few years, I habitually run 'make test' after building BIND >> from sources. I'me seiing a failure with 9.8.1-P1, and wonder whether >> anyone else is also. > > [B

Re: nxdomain not caching for configured reverse lookup

The use of 7.7.7.7 and 9.9.9.9 was used for testing purpose. This test is to cover the scenario, if I have a reverse lookup which is not configured on 10.212.24.11, i was expecting it to return NXDOMAIN and have it cached. This is not the ideal scenario of usage, but to check the condition, if i

Re: nxdomain not caching for configured reverse lookup

On 20.08.13 15:42, sumsum 2000 wrote: zone "7.7.7.7.in-addr.arpa" IN { type forward; forwarders {10.212.24.11;}; forward only; }; On 20.08.13 21:19, Mark An

Re: BIND 9.8.1-P1: 'make test' fails

On 22 Nov 2011, at 11:24, Niall O'Reilly wrote: > Since quite a few years, I habitually run 'make test' after building BIND > from sources. I'me seiing a failure with 9.8.1-P1, and wonder whether > anyone else is also. [By way of putting this to bed, at last ...] Updating

bind-users Digest, Vol 1603, Issue 2

Je suis absent jusqu'au 23 Août 2013 inclus. En cas d'urgence, vous pouvez contacter RASOAMANANA Ranto (Mob: +261320701232, e-mail: ranto.rasoaman...@orange.com). Confidentiality: This email is intended for the above-na

Re: nxdomain not caching for configured reverse lookup

The forward zone is not for a zone cut in the DNS tree. As a result the SOA record is above the "zone" and the SOA record gets ignored. In practice almost all forwarded zones match a actual zone so the returned SOA record is accepted. -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117,

Re: nxdomain not caching for configured reverse lookup

[root@FF15763 var]# dig -x 7.7.7.7 ; <<>> DiG 9.8.2rc1-RedHat-9.8.2-16.mlos2 <<>> -x 7.7.7.7 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 62698 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;7.7.7.7.in-add

bind-users Digest, Vol 1603, Issue 1

Je suis absent jusqu'au 23 Août 2013 inclus. En cas d'urgence, vous pouvez contacter RASOAMANANA Ranto (Mob: +261320701232, e-mail: ranto.rasoaman...@orange.com). Confidentiality: This email is intended for the above-na

Re: nxdomain not caching for configured reverse lookup

On 20.08.13 15:42, sumsum 2000 wrote: zone "7.7.7.7.in-addr.arpa" IN { type forward; forwarders {10.212.24.11;}; forward only; }; and when i do dig -x 7.7

nxdomain not caching for configured reverse lookup

Hi, I have the following zone configuration for forwarding DNS query view "default" IN { max-cache-ttl 604800; max-ncache-ttl 10800; zone "." IN { type forward;