IDNetters Forums

Technical News & Discussion => Networking & Routers => 2-Wire 2700 => Topic started by: kinmel on Apr 12, 2008, 12:19:28

Title: DNS poisoning
Post by: kinmel on Apr 12, 2008, 12:19:28
It appears that BT have taken down all the URLs used for provisioning the 2wire routers and if so then DNS poisoning is no longer necessary on any of them.

I cannot ping or tracert to any of the following:-

cwmp.cms.smehomehubrms.bt.com

gateway.cms.smehomehubrms.bt.com

pbthdm.bt.motive.com

pbthdm2.bt.motive.com


Can anyone reach them?



Title: Re: DNS poisoning
Post by: Sebby on Apr 12, 2008, 12:27:44
I can ping the *.motive.com addresses, but not the *.bt.com ones.
Title: Re: DNS poisoning
Post by: Rik on Apr 12, 2008, 12:28:23
I can get to the last two:

tracert pbthdm.bt.motive.com

Tracing route to pbthdm.bt.motive.com [66.193.112.93]
over a maximum of 30 hops:

  1    <1 ms     1 ms    <1 ms  home [192.168.1.254]
  2    25 ms    23 ms    23 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
  3    25 ms    23 ms    23 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
  4    45 ms    23 ms    23 ms  y-s-2.lon1.arbinet.net [213.232.64.76]
  5     *       38 ms    37 ms  ae-31-55.ebr1.London1.Level3.net [4.68.116.158]
  6    26 ms    39 ms    33 ms  ae-1-100.ebr2.London1.Level3.net [4.69.132.118]
  7   101 ms    94 ms   104 ms  ae-44.ebr1.NewYork1.Level3.net [4.69.137.78]
  8    95 ms   104 ms    94 ms  ae-2.ebr1.Newark1.Level3.net [4.69.132.98]
  9    95 ms    96 ms    94 ms  ae-14-51.car4.Newark1.Level3.net [4.68.99.8]
10    95 ms    94 ms    96 ms  ex1-tg2-0.eqnwnj.sbcglobal.net [151.164.89.249]
11   133 ms   133 ms   134 ms  151.164.241.200
12   136 ms   135 ms   135 ms  ded3-g1-3-0.austtx.sbcglobal.net [151.164.191.195]
13   247 ms   234 ms   236 ms  Motive-Communications-1144536.cust-rtr.swbell.net [67.64.75.106]
14   134 ms   135 ms   135 ms  67.67.200.14
15   144 ms   137 ms   141 ms  pbthdm.bt.motive.com [66.193.112.93]

Trace complete.

tracert pbthdm2.bt.motive.com

Tracing route to pbthdm2.bt.motive.com [64.186.176.39]
over a maximum of 30 hops:

  1    <1 ms     1 ms    <1 ms  home [192.168.1.254]
  2    94 ms    25 ms    25 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
  3    30 ms    27 ms    27 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
  4    26 ms    27 ms    23 ms  y-s-2.lon1.arbinet.net [213.232.64.76]
  5    25 ms    31 ms    37 ms  ae-32-54.ebr2.London1.Level3.net [4.68.116.126]
  6   103 ms   106 ms   108 ms  ae-43.ebr1.NewYork1.Level3.net [4.69.137.74]
  7   107 ms    94 ms   104 ms  ae-2.ebr1.Newark1.Level3.net [4.69.132.98]
  8    94 ms    94 ms    94 ms  ae-14-53.car4.Newark1.Level3.net [4.68.99.72]
  9    96 ms    94 ms    94 ms  ex1-tg2-0.eqnwnj.sbcglobal.net [151.164.89.249]
10   137 ms   133 ms   135 ms  151.164.241.200
11   139 ms   135 ms   137 ms  ded3-g1-3-0.austtx.sbcglobal.net [151.164.191.195]
12   135 ms   135 ms   135 ms  Motive-Communications-1144536.cust-rtr.swbell.net [67.64.75.106]
13   139 ms   137 ms   137 ms  67.67.200.3
14   135 ms   137 ms   137 ms  pbthdm2.bt.motive.com [64.186.176.39]

Trace complete.

Title: Re: DNS poisoning
Post by: kinmel on Apr 12, 2008, 12:34:18
Thanks

I can't get to them, I wonder which bit I have broken now ?

Back to the drawing board........................
Title: Re: DNS poisoning
Post by: Rik on Apr 12, 2008, 12:37:22
Try unplugging the RJ11 connector from the router, Alan. That usually cures most problems for me. ;)
Title: Re: DNS poisoning
Post by: kinmel on Apr 12, 2008, 12:39:23
 ;D