No. Those are the nameservers for your domain.
If you can resolve contribs.org to 207.182.33.10 then you don't have a DNS problem.
If you can tracert to 207.182.33.10 from one network but not another one then you have a routing problem.
As posted above, you need to get Telstra on the phone and get them to do tracerts and see that there is a problem. They need to sort it out at a level that you are really remote from.
I recommend that you look for a proxy server that lets you connect to Contribs and then start using your static IP - presumably you need the IP for webmail and stuff, and contribs for news and updates.
If you can persuade telstra to give you a different static IP then go for it.
I manage a site in Melbourne on 61.9.145.xxx and one in Sydney on 144.131.132.xxx that can both get to contribs.org. (I don't think it can be your hardware - but I'm using NetComm routers in bridge mode with PPPoE)
++++ Sydney to Contribs +++
C:\Documents and Settings\pbai-admin>tracert contribs.org
Tracing route to contribs.org [207.182.33.10]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 10.130.254.250
2 18 ms 32 ms 49 ms 61.9.192.253
3 18 ms 52 ms 19 ms 61.9.192.145
4 19 ms 52 ms 23 ms 61.9.193.6
5 19 ms 33 ms 49 ms gigabitethernet3-6.pic2.sydney.telstra.net [139.130.0.37]
6 18 ms 58 ms 17 ms gigabitethernet3-16.pic1.sydney.telstra.net [203.50.12.121]
7 19 ms 19 ms 20 ms gigabitethernet11-1.ken-core4.sydney.telstra.net [203.50.12.117]
8 19 ms 19 ms 19 ms 10GigabitEthernet3-0.pad-core4.Sydney.telstra.net [203.50.6.86]
9 18 ms 19 ms 19 ms 10gigabitethernet2-2.syd-core01.sydney.net.reach.com [203.50.13.38]
10 171 ms 165 ms 168 ms i-6-2.wil-core02.net.reach.com [202.84.249.69]
11 165 ms 166 ms 168 ms i-6-2.wil04.net.reach.com [202.84.251.186]
12 167 ms 169 ms 168 ms lap-brdr-01.inet.qwest.net [205.171.4.53]
13 170 ms 167 ms 169 ms bur-core-03.inet.qwest.net [205.171.213.105]
14 180 ms 178 ms 201 ms tmp-core-01.inet.qwest.net [205.171.8.2]
15 198 ms 200 ms 199 ms phv-edge-01.inet.qwest.net [205.171.129.86]
16 206 ms 211 ms 205 ms 65.121.93.134
17 206 ms 207 ms 207 ms t2-0.tucson-enss1.t3.login.com [204.17.35.106]
18 205 ms 213 ms 204 ms core-gw.opus1.com [207.182.35.58]
19 213 ms 221 ms 209 ms dsl-gw3.opus1.com [204.27.149.14]
20 215 ms 262 ms 232 ms coleman-rstrat-t1.opus1.net [207.182.63.246]
21 234 ms 220 ms 220 ms
www.contribs.org.33.182.207.in-addr.arpa [207.182.33.10]
Trace complete.
+++Sydney to 61.9.128.250 +++
C:\Documents and Settings\pbai-admin>tracert 61.9.128.250
Tracing route to 61.9.128.250 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 10.130.254.250
2 18 ms 53 ms 19 ms 61.9.192.253
3 25 ms 52 ms 19 ms 61.9.192.145
4 24 ms 48 ms 32 ms 61.9.193.6
5 22 ms 52 ms 19 ms gigabitethernet3-1.pit2.sydney.telstra.net [139.130.94.97]
6 20 ms 53 ms 19 ms gigabitethernet3-16.pic1.sydney.telstra.net [203.50.12.121]
7 20 ms 49 ms 20 ms gigabitethernet11-1.ken-core4.sydney.telstra.net [203.50.12.117]
8 18 ms 66 ms 19 ms 10gigabitethernet12-0.chw-core2.sydney.telstra.net [203.50.6.42]
9 35 ms 49 ms 32 ms Pos9-0.exi-core1.Melbourne.telstra.net [203.50.6.38]
10 36 ms 69 ms 33 ms GigabitEthernet2-7.exi1.Melbourne.telstra.net [203.50.77.14]
11 33 ms 52 ms 32 ms broadb1.lnk.telstra.net [139.130.94.126]
12 33 ms 35 ms 46 ms 61.9.129.4
13 34 ms 50 ms 36 ms 61.9.128.250
Trace complete.
+++ Melbourne to contribs.org +++
C:\Documents and Settings\pbai-admin>tracert contribs.org
Tracing route to contribs.org [207.182.33.10]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 10.120.254.250
2 21 ms 48 ms 45 ms 61.9.128.251
3 18 ms 49 ms 19 ms adelaide-atm.vic.bigpond.net.au [61.9.128.145]
4 18 ms 50 ms 19 ms 61.9.129.6
5 17 ms 49 ms 20 ms gigabitethernet2-10.exi2.melbourne.telstra.net [139.130.0.5]
6 20 ms 49 ms 20 ms gigabitethernet2-9.exi1.melbourne.telstra.net [203.50.77.33]
7 19 ms 48 ms 16 ms gigabitethernet2-2.exi-core1.melbourne.telstra.net [203.50.77.13]
8 34 ms 49 ms 32 ms pos15-0.chw-core2.sydney.telstra.net [203.50.6.37]
9 34 ms 48 ms 33 ms 10gigabitethernet1-0.oxf-core1.sydney.telstra.net [203.50.6.2]
10 34 ms 35 ms 53 ms 10gigabitethernet6-0.syd-core04.sydney.net.reach.com [203.50.13.34]
11 35 ms 56 ms 46 ms i-5-0.syd-core02.net.reach.com [202.84.144.249]
12 186 ms 183 ms 181 ms i-0-0.wil-core02.net.reach.com [202.84.144.101]
13 196 ms 190 ms 184 ms i-6-2.wil04.net.reach.com [202.84.251.186]
14 182 ms 183 ms 183 ms lap-brdr-01.inet.qwest.net [205.171.4.53]
15 185 ms 182 ms 186 ms bur-core-03.inet.qwest.net [205.171.213.105]
16 195 ms 195 ms 195 ms tmp-core-01.inet.qwest.net [205.171.8.2]
17 217 ms 215 ms 214 ms phv-edge-01.inet.qwest.net [205.171.129.86]
18 223 ms 220 ms 221 ms 65.121.93.134
19 221 ms 222 ms 220 ms t2-0.tucson-enss1.t3.login.com [204.17.35.106]
20 221 ms 222 ms 220 ms core-gw.opus1.com [207.182.35.58]
21 226 ms 227 ms 234 ms dsl-gw3.opus1.com [204.27.149.14]
22 238 ms 231 ms 266 ms coleman-rstrat-t1.opus1.net [207.182.63.246]
23 236 ms 231 ms 231 ms gpl.contribs.org [207.182.33.10]
Trace complete.
+++ Melbourne to 61.9.128.250 +++
C:\Documents and Settings\pbai-admin>tracert 61.9.128.250
Tracing route to 61.9.128.250 over a maximum of 30 hops
1 1 ms <1 ms <1 ms 10.120.254.250
2 17 ms 49 ms 19 ms 61.9.128.251
3 18 ms 34 ms 34 ms 61.9.128.250
Trace complete.
Actually, looking at this last short trace, it occurs to me that you possibly should be going out via 61.9.128.251 not 61.9.128.250 - which again is down to Telstra.
I know they're a nightmare to deal with - I came over there for a few weeks in February/early March to configure two sites to connect back to the UK and had a horrible time getting static IP addresses configured - not with the technical stuff, but with their administration. In fact, I think they have still to switch the billing for the Sydney IP from my personal credit card onto the main phone bill ... its only been 8 weeks .....
HTH
David
47 Replies
9728 Views