Woof! Okay, this time the ip addr switch again for me, one moment it was:
$ dig sipxecs.sipfoundry.org ; <<>> DiG 9.5.1-P2-RedHat-9.5.1-2.P2.fc10 <<>> sipxecs.sipfoundry.org ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 28455 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;sipxecs.sipfoundry.org. IN A ;; ANSWER SECTION: sipxecs.sipfoundry.org. 300 IN A 67.221.235.27 ;; Query time: 303 msec ;; SERVER: 192.168.1.106#53(192.168.1.106) ;; WHEN: Fri Apr 24 13:50:09 2009 ;; MSG SIZE rcvd: 56 And 5 minutes later (after the 300 second TTL timed out) it was: $ dig sipxecs.sipfoundry.org ; <<>> DiG 9.5.1-P2-RedHat-9.5.1-2.P2.fc10 <<>> sipxecs.sipfoundry.org ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 18868 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;sipxecs.sipfoundry.org. IN A ;; ANSWER SECTION: sipxecs.sipfoundry.org. 86388 IN A 216.142.118.34 I went to check OpenDNS.org's cache (http://www.opendns.com/support/cache/) and it showed different addresses in different geographical places. New York and London had the old address, Palo Alto, DC, Chicago, and Seattle had the correct one. Note the TTL on the "wrong" address is 24 hours, so I guess it's a good thing I'm going away for the weekend! It could be something wrong with OpenDNS... --Woof! _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
