| Question: |
Hello.There was a small problem with the domain britishdragonpharmaceuticals.com.Once it is activated on half of the devices (from different subnets) available, and on the other is a plug that rent is overdue. This is due to DNS updates or something else? |
| Answer: |
please Do a trace to Your domain: start - run - enter cmd - in the black window enter tracert YOUR DOMAIN - after click to highlight - making enter - skopirovat here in the ticket
If You are experiencing zatrudina, view instructional videos http://ded07.net/helphost/tracert.htm |
| Question: |
Send You, two traces of the domain from different subnets.The first leads to the plug, the second directly on the website. |
| Question: |
//The tracing is carried out from the subnet that displays on salescordarone route to britishdragonpharmaceuticals.com [209.99.40.223]with the maximum number of jumps 30: 1 2 ms 2 ms 2 ms 172.20.10.1 2 * * * timed out for the request. 3 383 ms 318 ms 287 ms 10.1.32.93 4 446 ms 328 ms 318 ms 10.241.9.26 5 34 ms 40 ms 36 ms 10.241.9.25 6 * * * timed out for the request. 7 108 ms * 135 ms 185.32.225.229 8 57 ms 59 ms 57 ms 188.254.34.201 9 51 ms 156 ms 68 ms 213.59.211.63 10 3093 ms 1909 ms 1920 ms rostelecom-gw.ip4.gtt.net [77.67.75.254] 11 1288 ms 547 ms 555 ms ae1.stk30.ip4.gtt.net [77.67.75.253] 12 126 ms 96 ms 109 ms be3257.ccr21.sto01.atlas.cogentco.com [130.117.15.137] 13 113 ms 110 ms 125 ms be2396.ccr21.sto03.atlas.cogentco.com [130.117.50.121] 14 136 ms 110 ms 104 ms be2281.ccr41.ham01.atlas.cogentco.com [154.54.63.1] 15 106 ms 100 ms 104 ms be2815.ccr41.ams03.atlas.cogentco.com [154.54.38.205] 16 211 ms 318 ms 645 ms be12194.ccr41.lon13.atlas.cogentco.com [154.54.56.93] 17 219 ms 196 ms 268 ms be2982.ccr21.bos01.atlas.cogentco.com [154.54.1.117] 18 189 ms 177 ms 171 ms be2094.ccr41.jfk02.atlas.cogentco.com [154.54.30.13] 19 221 ms 268 ms 244 ms be2806.ccr41.dca01.atlas.cogentco.com [154.54.40.106] 20 451 ms 400 ms 314 ms be2112.ccr41.atl01.atlas.cogentco.com [154.54.7.158] 21 494 ms 508 ms 830 ms be2687.ccr21.iah01.atlas.cogentco.com [154.54.28.70] 22 324 ms 570 ms 442 ms be2873.rcr11.aus02.atlas.cogentco.com [154.54.2.50] 23 684 ms 246 ms 582 ms te0-0-2-0.nr11.b006628-1.aus02.atlas.cogentco.com [154.24.30.250] 24 301 ms 865 ms 1108 ms 38.122.254.14 25 325 ms 309 ms 321 ms 209-99-40-223.fwd.datafoundry.com [209.99.40.223]Trace zavershena.=======================================================================================================//On this subnet site documentenservice route to britishdragonpharmaceuticals.com [192.185.78.30]with the maximum number of jumps 30: 1 1 ms 1 ms 1 ms infolan.by [192.168.0.1] 2 1 ms <1 MS 1 ms edge.infolan.by [10.25.94.126] 3 25 ms 1 ms 1 ms alpha.infolan.by [192.168.0.201] 4 1 ms 1 ms 1 ms border.infolan.by [10.25.255.5] 5 1 ms 1 ms 1 ms 212.98.162.1 6 1 ms 1 ms 1 ms msq.po2.gate4.bn.by [212.98.160.185] 7 1 ms 1 ms 1 ms 185.32.225.229 8 6 ms 6 ms 6 ms ae2.RT.HWE.LBD.PL.retn.net [87.245.245.97] 9 53 ms 30 ms 30 ms ae3-8.RT.TC2.AMS.NL.retn.net [87.245.234.86] 10 29 ms 29 ms 29 ms er1.ams1.nl.above.net [80.249.208.122] 11 31 ms 30 ms 29 ms ae14.cr1.ams10.nl.zip.zayo.com [64.125.21.77] 12 141 ms 143 ms 141 ms ae27.cs1.ams10.nl.eth.zayo.com [64.125.27.0] 13 146 ms 146 ms 146 ms ae2.cs1.lhr15.uk.eth.zayo.com [64.125.29.17] 14 138 ms 138 ms 138 ms ae5.cs1.dca2.us.eth.zayo.com [64.125.29.131] 15 143 ms 167 ms 143 ms ae3.cs1.iah1.us.eth.zayo.com [64.125.29.49] 16 138 ms 138 ms 137 ms ae27.cr1.iah1.us.zip.zayo.com [64.125.30.239] 17 138 ms 138 ms 138 ms xe-0-0-0.mpr1.iah81.us.zip.zayo.com [64.125.30.213] 18 142 ms 142 ms 143 ms 64.124.202.50.IPYX-120228-001-ZYO.zip.zayo.com [64.124.202.50] 19 145 ms 146 ms 145 ms 146 216.117.50.138 20 ms 307 ms 145 ms 192.185.178.170 21 141 ms 140 ms 140 ms 192.185.78.30 the Trace was completed. |
| Answer: |
you have not updated DNS |
| Question: |
thank you so much! We will wait for the provider pull up the new DNS! |
| Answer: |
ok |
| Question: |
Tell me how long you can go update the DNS?It`s been 2 days and with some providers, the site never became available. |
| Answer: |
Average time to update 12-72 hours and depends on the provider. |
