rndc flush usually in /usr/sbin
/usr/sbin/rndc flush (assuming linux, then the client has to have it flushed too) >>> "Nikolay Kondratyev" <[email protected]> 04/29/09 7:15 AM >>> Thanks a lot, I'll try to find out how to clear bind cash. Thanks again, Nikolay. _____ From: Melcon Moraes [mailto:[email protected]] Sent: Wednesday, April 29, 2009 2:32 PM To: Nikolay Kondratyev Cc: Scott Lawrence; [email protected] Subject: Re: [sipX-dev] broken.http://sipxecs.sipfoundry.org/pub/sipXecs/ISO/ When you use +trace, you(the dig utility actually) are searching all the way from root servers until sipxecs.sipfoundry.org. Remember that DNS work like an inverted tree[1]. The root servers know who has the authority on org. domains, which in turn know the authority for sipfoundry.org. and finally the host sipxecs.sipfoundry.org. When you just ask dig to search for the host sipxecs.sipfoundry.org., it will ask your DNS server that will do the whole job, if it has no info about that host or simply answer with the cached info - that was what you get. In your case, your DNS server(172.23.12.222) already had the info about sipxecs.sipfoundry.org. and it will expire in 28395 seconds. ;; ANSWER SECTION: sipxecs.sipfoundry.org <http://sipxecs.sipfoundry.org/> . 28395 IN A 216.142.118.34 If you runs that server you can always flush its cache in order to get the fresh info. - MM [1] http://en.wikipedia.org/wiki/Domain_Name_System On Wed, Apr 29, 2009 at 2:24 AM, Nikolay Kondratyev <[email protected]> wrote: I also can not access http://sipxecs.sipfoundry.org... I'm not sure what is happening, but dig +trace sipxecs.sipfoundry.org shows the new address, while dig sipxecs.sipfoundry.org (without "+trace") shows different (old?) address... [r...@sipx3 yum.repos.d]# dig +trace sipxecs.sipfoundry.org ; <<>> DiG 9.3.4-P1 <<>> +trace sipxecs.sipfoundry.org ;; global options: printcmd . 202693 IN NS A.ROOT-SERVERS.NET. . 202693 IN NS B.ROOT-SERVERS.NET. . 202693 IN NS C.ROOT-SERVERS.NET. . 202693 IN NS D.ROOT-SERVERS.NET. . 202693 IN NS E.ROOT-SERVERS.NET. . 202693 IN NS F.ROOT-SERVERS.NET. . 202693 IN NS G.ROOT-SERVERS.NET. . 202693 IN NS H.ROOT-SERVERS.NET. . 202693 IN NS I.ROOT-SERVERS.NET. . 202693 IN NS J.ROOT-SERVERS.NET. . 202693 IN NS K.ROOT-SERVERS.NET. . 202693 IN NS L.ROOT-SERVERS.NET. . 202693 IN NS M.ROOT-SERVERS.NET. ;; Received 488 bytes from 172.23.12.222#53(172.23.12.222) in 0 ms org. 172800 IN NS D0.ORG.AFILIAS-NST.org. org. 172800 IN NS C0.ORG.AFILIAS-NST.INFO. org. 172800 IN NS B0.ORG.AFILIAS-NST.org. org. 172800 IN NS B2.ORG.AFILIAS-NST.org. org. 172800 IN NS A2.ORG.AFILIAS-NST.INFO. org. 172800 IN NS A0.ORG.AFILIAS-NST.INFO. ;; Received 442 bytes from 198.41.0.4#53(A.ROOT-SERVERS.NET) in 209 ms sipfoundry.org. 86400 IN NS lambda.sipfoundry.org. sipfoundry.org. 86400 IN NS dns.nostrum.com. sipfoundry.org. 86400 IN NS dns.byexample.org. ;; Received 150 bytes from 199.19.57.1#53(D0.ORG.AFILIAS-NST.org) in 64 ms sipxecs.sipfoundry.org. 3600 IN A 67.221.235.27 sipfoundry.org. 3600 IN NS lambda.sipfoundry.org. sipfoundry.org. 3600 IN NS dns.nostrum.com. sipfoundry.org. 3600 IN NS dns.byexample.org. ;; Received 150 bytes from 72.232.205.74#53(lambda.sipfoundry.org) in 169 ms [r...@sipx3 yum.repos.d]# dig sipxecs.sipfoundry.org ; <<>> DiG 9.3.4-P1 <<>> sipxecs.sipfoundry.org ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 8371 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 3, ADDITIONAL: 3 ;; QUESTION SECTION: ;sipxecs.sipfoundry.org. IN A ;; ANSWER SECTION: sipxecs.sipfoundry.org. 28395 IN A 216.142.118.34 ;; AUTHORITY SECTION: sipfoundry.org. 3585 IN NS dns.nostrum.com. sipfoundry.org. 3585 IN NS dns.byexample.org. sipfoundry.org. 3585 IN NS lambda.sipfoundry.org. ;; ADDITIONAL SECTION: dns.nostrum.com. 100151 IN A 72.232.15.10 dns.byexample.org. 362953 IN A 72.36.160.122 lambda.sipfoundry.org. 3585 IN A 72.232.205.74 ;; Query time: 0 msec ;; SERVER: 172.23.12.222#53(172.23.12.222) ;; WHEN: Wed Apr 29 09:18:08 2009 ;; MSG SIZE rcvd: 182 > -----Original Message----- > From: [email protected] [mailto:sipx-dev- > [email protected]] On Behalf Of Scott Lawrence > Sent: Wednesday, April 29, 2009 4:59 AM > To: Tony Graziano > Cc: [email protected] > Subject: Re: [sipX-dev] > broken.http://sipxecs.sipfoundry.org/pub/sipXecs/ISO/ > > On Tue, 2009-04-28 at 20:30 -0400, Tony Graziano wrote: > > The servers were moved recently. It was discovered today the DNS updates > are slowly updating across the Internet. > > > > The proper IP should show: > > > > 67.221.235.27 > > > > http://67.221.235.27/pub/sipXecs/ISO/ > > No - that won't work. This is a name-based virtual host - you must use > the name sipxecs.sipfoundry.org or the path will not work. > > That was, however the correct address, so if you override your local DNS > you should see it. > > If you are not able to resolve the name, send me the output of: > > dig +trace sipxecs.sipfoundry.org > > to help me track down the bad DNS data > > _______________________________________________ > sipx-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
