Hi Scott Hi Scott
-bash-3.2$ dig sipxecs.sipfoundry.org ; <<>> DiG 9.3.4-P1 <<>> sipxecs.sipfoundry.org ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 15357 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 3, ADDITIONAL: 3 ;; QUESTION SECTION: ;sipxecs.sipfoundry.org. IN A ;; ANSWER SECTION: sipxecs.sipfoundry.org. 680 IN A 67.221.235.27 ;; AUTHORITY SECTION: sipfoundry.org. 25873 IN NS dns.nostrum.com. sipfoundry.org. 25873 IN NS lambda.sipfoundry.org. sipfoundry.org. 25873 IN NS dns.byexample.org. ;; ADDITIONAL SECTION: dns.nostrum.com. 162677 IN A 72.232.15.10 lambda.sipfoundry.org. 680 IN A 72.232.205.74 dns.byexample.org. 205571 IN A 72.36.160.122 ;; Query time: 4 msec ;; SERVER: 69.38.187.19#53(69.38.187.19) ;; WHEN: Wed Apr 29 09:41:42 2009 ;; MSG SIZE rcvd: 182 -bash-3.2$ -bash-3.2$ dig sipxecs.sipfoundry.org ; <<>> DiG 9.3.4-P1 <<>> sipxecs.sipfoundry.org ;; global options: printcmd ;; Got answer: -bash: -bash-3.2$: command not found ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 15357 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 3, ADDITIONAL: 3 -bash-3.2$ -bash-3.2$ ; <<>> DiG 9.3.4-P1 <<>> sipxecs.sipfoundry.org -bash: syntax error near unexpected token `;' -bash-3.2$ ;; global options: printcmd -bash: syntax error near unexpected token `;;' -bash-3.2$ ;; Got answer: -bash: syntax error near unexpected token `;;' -bash-3.2$ ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 15357 -bash: syntax error near unexpected token `;;' -bash-3.2$ ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 3, ADDITIONAL: 3 -bash: syntax error near unexpected token `;;' -bash-3.2$ -bash-3.2$ ;; QUESTION SECTION: -bash: syntax error near unexpected token `;;' -bash-3.2$ ;sipxecs.sipfoundry.org. IN A -bash: syntax error near unexpected token `;' -bash-3.2$ -bash-3.2$ ;; ANSWER SECTION: -bash: syntax error near unexpected token `;;' -bash-3.2$ sipxecs.sipfoundry.org. 680 IN A 67.221.235.27 -bash: sipxecs.sipfoundry.org.: command not found -bash-3.2$ -bash-3.2$ ;; AUTHORITY SECTION: -bash: syntax error near unexpected token `;;' -bash-3.2$ sipfoundry.org. 25873 IN NS dns.nostrum.com. -bash: sipfoundry.org.: command not found -bash-3.2$ sipfoundry.org. 25873 IN NS lambda.sipfoundry.org. -bash: sipfoundry.org.: command not found -bash-3.2$ sipfoundry.org. 25873 IN NS dns.byexample.org. -bash: sipfoundry.org.: command not found -bash-3.2$ -bash-3.2$ ;; ADDITIONAL SECTION: -bash: syntax error near unexpected token `;;' -bash-3.2$ dns.nostrum.com. 162677 IN A 72.232.15.10 -bash: dns.nostrum.com.: command not found -bash-3.2$ lambda.sipfoundry.org. 680 IN A 72.232.205.74 -bash: lambda.sipfoundry.org.: command not found -bash-3.2$ dns.byexample.org. 205571 IN A 72.36.160.122 -bash: dns.byexample.org.: command not found -bash-3.2$ -bash-3.2$ ;; Query time: 4 msec -bash: syntax error near unexpected token `;;' -bash-3.2$ ;; SERVER: 69.38.187.19#53(69.38.187.19) -bash: syntax error near unexpected token `;;' -bash-3.2$ ;; WHEN: Wed Apr 29 09:41:42 2009 -bash: syntax error near unexpected token `;;' -bash-3.2$ ;; MSG SIZE rcvd: 182 -bash: syntax error near unexpected token `;;' ----- Original Message ----- From: "Scott Lawrence" <[email protected]> To: "Tony Graziano" <[email protected]> Cc: <[email protected]>; <[email protected]> Sent: Tuesday, April 28, 2009 7:59 PM 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 > > ----- Original Message ----- From: "Scott Lawrence" <[email protected]> To: "Tony Graziano" <[email protected]> Cc: <[email protected]>; <[email protected]> Sent: Tuesday, April 28, 2009 7:59 PM 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
