OK, who can explain this?
I used to redirect parts.mbz.org to buymbparts.org by pointing to its IP address (74.208.144.39). Three days ago I changed parts.mbz.org so that has an A record of 199.166.24.53
The nameservers for mbz.org are:
# tinydns-get ns mbz.org
2 mbz.org:
228 bytes, 1+5+0+5 records, response, authoritative, noerror
query: 2 mbz.org
answer: mbz.org 172800 NS mejac.palo-alto.ca.us
answer: mbz.org 172800 NS ns.ndc.vrx.net
answer: mbz.org 172800 NS ns1.quasar.net
answer: mbz.org 172800 NS ns1.vrx.net
answer: mbz.org 172800 NS rd.vrx.net
additional: mejac.palo-alto.ca.us 2146 A 192.147.236.1
additional: ns.ndc.vrx.net 172800 A 199.166.26.200
additional: ns1.quasar.net 48415 A 199.166.31.3
additional: ns1.vrx.net 172800 A 199.166.24.1
additional: rd.vrx.net 172800 A 199.166.26.51
root@ndc.vrx.net Fri Nov 13 13:21:41 /service/tinydns/root
# tinydns-get soa mbz.org
6 mbz.org:
278 bytes, 1+1+5+5 records, response, authoritative, noerror
query: 6 mbz.org
answer: mbz.org 172800 SOA ns1.vrx.net use_the_phone.vrx.net 2009131100 14400 3600 1728000 172800
authority: mbz.org 172800 NS mejac.palo-alto.ca.us
authority: mbz.org 172800 NS ns.ndc.vrx.net
authority: mbz.org 172800 NS ns1.quasar.net
authority: mbz.org 172800 NS ns1.vrx.net
authority: mbz.org 172800 NS rd.vrx.net
additional: mejac.palo-alto.ca.us 2146 A 192.147.236.1
additional: ns.ndc.vrx.net 172800 A 199.166.26.200
additional: ns1.quasar.net 48415 A 199.166.31.3
additional: ns1.vrx.net 172800 A 199.166.24.1
additional: rd.vrx.net 172800 A 199.166.26.51
root@ndc.vrx.net Fri Nov 13 13:21:55 /service/tinydns/root
From any of those servers, if I query the server from my XP laptop on Bell's wifi at Starbucks I consistantly get the wrong address, even though I'm querying the authoritatove servers directly:
C:\>host parts.mbz.org ns.ndc.vrx.net
Using domain server:
Name: ns.ndc.vrx.net
Address: 199.166.26.200#53
parts.mbz.org has address 74.208.144.39
C:\>host parts.mbz.org ns1.vrx.net
Using domain server:
Name: ns1.vrx.net
Address: 199.166.24.1#53
parts.mbz.org has address 74.208.144.39
C:\>host parts.mbz.org mejac.palo-alto.ca.us
Using domain server:
Name: mejac.palo-alto.ca.us
Address: 192.147.236.1#53
parts.mbz.org has address 74.208.144.39
Yes if I query those nameservers from anywhere other than my laptop on Bells wifi I get different numbers from the same servers apparantly:
@mejac Fri Nov 13 11:35:23 ~
% host parts.mbz.org mejac.palo-alto.ca.us
Using domain server:
Name: mejac.palo-alto.ca.us
Addresses: 192.147.236.1
parts.mbz.org has address 199.166.24.53
@ndc.vrx.net Fri Nov 13 13:58:48 /service/tinydns/root
# host parts.mbz.org ns.ndc.vrx.net
Using domain server:
Name: ns.ndc.vrx.net
Address: 199.166.26.200#53
parts.mbz.org has address 199.166.24.53
@ns1.vrx.net Fri Nov 13 14:39:16 /service/tinydns/root
# host parts.mbz.org ns1.vrx.net
Using domain server:
Name: ns1.vrx.net
Address: 199.166.24.1#53
parts.mbz.org has address 199.166.24.53
Bell is caching DNS records, ignoring TTLs by intercepting DNS requests? Really?
Reboot XP laptop.
C:\>host parts.mbz.org
parts.mbz.org has address 199.166.24.53
Finally. correct.
(Use web browser to look at parts.mbz.org - get the wrong page.)
C:\>host parts.mbz.org
parts.mbz.org has address 74.208.144.39
Wrong! Lovely!
