RE: Failover
This is not the DNS job to check at the web service availability. You could make an external script that is testing for the service availibility and change the dns accordingly, like (...) : web1 active ? yes : was it active at last test ? yes : do nothing no : set www to point to web1 in DNS no : was it already inactive ? yes : do nothing no : set www to point to web2 in DNS and with having www/web1/web2 having a low TTL. Philippe From: bind-users-boun...@lists.isc.org [mailto:bind-users-boun...@lists.isc.org] On Behalf Of Mohammed Ejaz Sent: Monday, April 27, 2009 8:11 AM To: bind-users@lists.isc.org Subject: Failover Hi all, Can it be possible through the bind, www records should work as failover, I mean during the primary record unavailable and then it should go for next www only, Pls. note that I don't want let they work as round robin function. 1. Primary www record pointing 1.2.3.4 as long as it is available it should read from the same IP, 2. Secondary www record pointing 4.3.2.1 it should act only incase of primary is down. Ejaz ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
RE: Failover
First of all many thanks for your response, Actually we are in ISP; this solution is for one of our customer in this case we need to give the access of the server to the customer, Ejaz _ From: philippe.simo...@swisscom.com [mailto:philippe.simo...@swisscom.com] Sent: Monday, April 27, 2009 10:00 AM To: me...@cyberia.net.sa; bind-users@lists.isc.org Subject: RE: Failover This is not the DNS job to check at the web service availability. You could make an external script that is testing for the service availibility and change the dns accordingly, like (...) : web1 active ? yes : was it active at last test ? yes : do nothing no : set www to point to web1 in DNS no : was it already inactive ? yes : do nothing no : set www to point to web2 in DNS and with having www/web1/web2 having a low TTL. Philippe _ From: bind-users-boun...@lists.isc.org [mailto:bind-users-boun...@lists.isc.org] On Behalf Of Mohammed Ejaz Sent: Monday, April 27, 2009 8:11 AM To: bind-users@lists.isc.org Subject: Failover Hi all, Can it be possible through the bind, www records should work as failover, I mean during the primary record unavailable and then it should go for next www only, Pls. note that I don't want let they work as round robin function. 1. Primary www record pointing 1.2.3.4 as long as it is available it should read from the same IP, 2. Secondary www record pointing 4.3.2.1 it should act only incase of primary is down. Ejaz ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: Failover
In article , wrote: > This is not the DNS job to check at the web service availability. > You could make an external script that is testing for the service availibil= > ity > and change the dns accordingly, like (...) : > > web1 active ? > yes : was it active at last test ? > yes : do nothing > no : set www to point to web1 in DNS > no : was it already inactive ? > yes : do nothing > no : set www to point to web2 in DNS > > and with having www/web1/web2 having a low TTL. We do something like this for some not-very-critical services. A script (happens to run on a nameserver, but that's coincidental) watchdogs a number of servers and uses (suitably secured) dynamic update to remove non-responsive ones from a low-TTL roundrobin. It knows not to remove the last entry. Sam ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: Failover
The Best - use carp (VRRP) protocol for it or nginx proxy server. Or you can use dynamic update for zone: ping -c 5 your.host || nsupdate ... Mohammed Ejaz wrote: > Hi all, > > > > Can it be possible through the bind, www records should work as > failover, I mean during the primary record unavailable and then it > should go for next www only, Pls. note that I don’t want let they work > as round robin function. > > > > 1. Primary www record pointing 1.2.3.4 as long as it is available it > should read from the same IP, > > > > 2. Secondary www record pointing 4.3.2.1 it should act only incase of > primary is down. > > > > Ejaz > > > > > > > ___ > bind-users mailing list > bind-users@lists.isc.org > https://lists.isc.org/mailman/listinfo/bind-users ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: Failover
On Apr 27 2009, Mohammed Ejaz wrote: Can it be possible through the bind, www records should work as failover, I mean during the primary record unavailable and then it should go for next www only, Pls. note that I don't want let they work as round robin function. 1. Primary www record pointing 1.2.3.4 as long as it is available it should read from the same IP, 2. Secondary www record pointing 4.3.2.1 it should act only incase of primary is down. If only SRV records for http had been standardised, and been implemented in browsers, this would be a straightforward application of them :-( -- Chris Thompson Email: c...@cam.ac.uk ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: bind 9.4 acache crashes
Sotiris Tsimbonis wrote, On 09/04/2009 10:26 AM: On 9/4/2009 10:10 πμ, Sotiris Tsimbonis wrote: On 7/4/2009 12:09 μμ, Sotiris Tsimbonis wrote: On 6/4/2009 9:23 μμ, JINMEI Tatuya / 神明達哉 wrote: At Fri, 03 Apr 2009 18:38:01 +0300, Sotiris Tsimbonis wrote: Anyone else seen crashes like these? FWIW, I've never seen any of these. Solaris 10, Bind 9.4.3b2 And another one (Solaris 9, bind 9.4.3b2) ... The acache related crashes still persist... Any ideas? 27-Apr-2009 18:14:39.092 general: acache.c:393: INSIST(result == 0) failed 27-Apr-2009 18:14:39.092 general: exiting (due to assertion failure) 27-Apr-2009 18:17:09.339 general: sockmgr 25af90: maximum number of FD events (256) received Cheers, Sotiris. ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Signing algorithms for rndc
It seems that even in the most recent versions of BIND, rndc supports only the hmac-md5 algorithm. Given that MD5 is being deprecated all over the place (I am thinking of draft-ietf-dnsext-tsig-md5-deprecated-02 in particular), is this wise? -- Chris Thompson Email: c...@cam.ac.uk ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
How to forward domain totally not using CNAME?
Hello, all. I would like to CNAME like below. example.com. IN CNAMEexample2.com. But I know that this is wrong. then, is there any way or solution to solve this problem? I searched and found that below is a similar solution. * IN CNAMEexample2.com. but in this case, only .example.com works well and example.com doesn't work well. Any comment? Thanks in advance. _ 봄이라 사진 많이 찍으시죠?! 사진 갤러리로 리사이즈와 보정을 한번에! http://mswindowslive.tistory.com/5 ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: How to forward domain totally not using CNAME?
MontyRee wrote: > > Hello, all. > > > I would like to CNAME like below. > > example.com. IN CNAMEexample2.com. > > > But I know that this is wrong. > then, is there any way or solution to solve this problem? > > > I searched and found that below is a similar solution. > > > * IN CNAMEexample2.com. > > but in this case, only .example.com works well > and example.com doesn't work well. > > > Any comment? > > > Thanks in advance. use example.com. IN DNAMEexample2.com. ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
about DNAME question
Hello, all. Thanks for kind answering for DNAME. I have additional questions for DNAME. If I set like below, example.com. IN DNAMEexample2.com IP addreess of example.com is 192.168.1.2 1. if client resolver use bind 8 or below old version. What would be happen? Can recognize DNAME record well? 2. if I query example.com, it returns NXDOMAIN instead of 192.168.1.2. How to solve this problem? Thanks in advance. _ 새로워진 핫메일! 무료 POP3로 타메일, 클라이언트 연동도 자유롭게! http://mail.live.com ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Stupid comp.protocols.dns.bind gateway
What's worse than a mail-to-news gateway that leaving the multipart crap headers in the body but removing the "Content-Type: multipart/alternative" line from the header In article , MontyRee wrote: > CkhlbGxvLCBhbGwuCiAKVGhhbmtzIGZvciBraW5kIGFuc3dlcmluZyBmb3IgRE5BTUUuCkkgaGF2 > ZSBhZGRpdGlvbmFsIHF1ZXN0aW9ucyBmb3IgRE5BTUUuCiAKSWYgSSBzZXQgbGlrZSBiZWxvdywg > CiAKZXhhbXBsZS5jb20uICAgICAgICAgICAgICBJTiBETkFNRSAgICAgICAgZXhhbXBsZTIuY29t > CgpJUCBhZGRyZWVzcyBvZiBleGFtcGxlLmNvbSBpcyAxOTIuMTY4LjEuMiAKIAogCjEuIGlmIGNs > aWVudCByZXNvbHZlciB1c2UgYmluZCA4IG9yIGJlbG93IG9sZCB2ZXJzaW9uLgogICBXaGF0IHdv > dWxkIGJlIGhhcHBlbj8KICAgQ2FuIHJlY29nbml6ZSBETkFNRSByZWNvcmQgd2VsbD8KIAogCjIu > IGlmIEkgcXVlcnkgZXhhbXBsZS5jb20sIGl0IHJldHVybnMgTlhET01BSU4gaW5zdGVhZCBvZiAx > OTIuMTY4LjEuMi4KICAgSG93IHRvIHNvbHZlIHRoaXMgcHJvYmxlbT8KIAogCgpUaGFua3MgaW4g > YWR2YW5jZS4KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f > X19fX19fX19fX19fX19fX18Ku/W3zr/2wfggx9a43sDPISC5q7fhIFBPUDO3ziDFuLjewM8sIMWs > tvPAzL7wxq4gv6y1v7W1IMDawK+307DUIQpodHRwOi8vbWFpbC5saXZlLmNvbQpfX19fX19fX19f > X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpiaW5kLXVzZXJzIG1haWxpbmcg > bGlzdApiaW5kLXVzZXJzQGxpc3RzLmlzYy5vcmcKaHR0cHM6Ly9saXN0cy5pc2Mub3JnL21haWxt > YW4vbGlzdGluZm8vYmluZC11c2Vycw== -- Barry Margolin, bar...@alum.mit.edu Arlington, MA *** PLEASE don't copy me on replies, I'll read them in the group *** ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
approach on parsing the query-log file
Hi all, I'm thinking of writing a quick tool to archive the query-log in a database to allow for easier reports. The obvious question that occurs is; What would be what's the best approach to do this? Running scripts that parses through the query-log would cause locking essentially killing BIND on a heavy loaded server and only parsing archived files wouldn't allow real-time information, also re-parsing the same set of data over and over again until the log has rotated would cause unnecessary I/O load. I'm guessing the best would be to have BIND write directly to a script that dumps the data where-ever it makes sense to. I've used BIND statistics and found it highly useful but then again it doesn't allow me to make breakdowns based on host/query. If anyone has done something like this or having pointers on how this could achieved any information is welcome! Thanks /Jonathan ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
