domain is not accessible from some routers

Discussion in 'Server / Technical Administration Tips and Queries' started by willows, Dec 10, 2012.

  1. willows

    willows New Member

    Hi

    I have this on going issue with one of our domains over the past few months only.
    the domain Willows Consulting - web developers is accessible from a magnet router but not a upc router or eircom router.
    The domain is 10 years old and was moved about 12 months ago so the dns should be propagated by now !

    I am no networking guru and I am getting conflicting messages from the hoster and the network providers.

    The domain is registered with dotster in the states and has been there since inception.
    The hosting was changed 1 year ago.
    The named servers were changed on the domain.

    I have a sneaking suspicion there is some sort of precedence issue on the domain the present hoster is not far enough up the chain.

    Below are the traceroutes from the server where I cannot view my own website from .

    My ip address of my router is 109.255.173.14

    The trace route to www.willows-consulting.com reads

    TraceRoute from Network-Tools.com to 78.137.164.79 [www.willows-consulting.com]
    [TABLE="width: 100"]
    [TR]
    [TD]Hop[/TD]
    [TD](ms)[/TD]
    [TD](ms)[/TD]
    [TD](ms)[/TD]
    [TD][/TD]
    [TD] IP Address[/TD]
    [TD]Host name[/TD]
    [/TR]
    [/TABLE]

    [TABLE="width: 100"]
    [TR]
    [TD]1 [/TD]
    [TD] 1 [/TD]
    [TD] 0 [/TD]
    [TD] 0 [/TD]
    [TD] 8.9.232.73[/TD]
    [TD] xe-5-3-0.edge3.dallas1.level3.net [/TD]
    [/TR]
    [/TABLE]

    [TABLE="width: 100"]
    [TR]
    [TD]2 [/TD]
    [TD] 0 [/TD]
    [TD] 0 [/TD]
    [TD] 0 [/TD]
    [TD] 4.69.145.254[/TD]
    [TD] vlan90.csw4.dallas1.level3.net [/TD]
    [/TR]
    [/TABLE]

    [TABLE="width: 100"]
    [TR]
    [TD]3 [/TD]
    [TD] 0 [/TD]
    [TD] 0 [/TD]
    [TD] 1 [/TD]
    [TD] 4.69.151.170[/TD]
    [TD] ae-93-93.ebr3.dallas1.level3.net [/TD]
    [/TR]
    [/TABLE]

    [TABLE="width: 100"]
    [TR]
    [TD]4 [/TD]
    [TD] 20 [/TD]
    [TD] 21 [/TD]
    [TD] 20 [/TD]
    [TD] 4.69.134.22[/TD]
    [TD] ae-7-7.ebr3.atlanta2.level3.net [/TD]
    [/TR]
    [/TABLE]

    [TABLE="width: 100"]
    [TR]
    [TD]5 [/TD]
    [TD] 34 [/TD]
    [TD] 33 [/TD]
    [TD] 34 [/TD]
    [TD] 4.69.132.86[/TD]
    [TD] ae-2-2.ebr1.washington1.level3.net [/TD]
    [/TR]
    [/TABLE]

    [TABLE="width: 100"]
    [TR]
    [TD]6 [/TD]
    [TD] 33 [/TD]
    [TD] 45 [/TD]
    [TD] 33 [/TD]
    [TD] 4.69.134.134[/TD]
    [TD] ae-71-71.csw2.washington1.level3.net [/TD]
    [/TR]
    [/TABLE]

    [TABLE="width: 100"]
    [TR]
    [TD]7 [/TD]
    [TD] 33 [/TD]
    [TD] 33 [/TD]
    [TD] 33 [/TD]
    [TD] 4.69.134.149[/TD]
    [TD] ae-72-72.ebr2.washington1.level3.net [/TD]
    [/TR]
    [/TABLE]

    [TABLE="width: 100"]
    [TR]
    [TD]8 [/TD]
    [TD] 114 [/TD]
    [TD] 114 [/TD]
    [TD] 114 [/TD]
    [TD] 4.69.137.53[/TD]
    [TD] ae-42-42.ebr2.paris1.level3.net [/TD]
    [/TR]
    [/TABLE]

    [TABLE="width: 100"]
    [TR]
    [TD]9 [/TD]
    [TD] 184 [/TD]
    [TD] 207 [/TD]
    [TD] 212 [/TD]
    [TD] 4.69.148.53[/TD]
    [TD] ae-6-6.car1.dublin3.level3.net [/TD]
    [/TR]
    [/TABLE]

    [TABLE="width: 100"]
    [TR]
    [TD]10 [/TD]
    [TD] 130 [/TD]
    [TD] 130 [/TD]
    [TD] 130 [/TD]
    [TD] 4.69.148.58[/TD]
    [TD] ae-7-7.car2.dublin1.level3.net [/TD]
    [/TR]
    [/TABLE]

    [TABLE="width: 100"]
    [TR]
    [TD]11 [/TD]
    [TD] 131 [/TD]
    [TD] 131 [/TD]
    [TD] 131 [/TD]
    [TD] 213.242.106.78[/TD]
    [TD] - [/TD]
    [/TR]
    [/TABLE]

    [TABLE="width: 100"]
    [TR]
    [TD]12 [/TD]
    [TD] 132 [/TD]
    [TD] 131 [/TD]
    [TD] 131 [/TD]
    [TD] 78.137.164.79[/TD]
    [TD] lh39.dnsireland.com [/TD]
    [/TR]
    [/TABLE]
    Trace complete

    The trace of the ip address 109.255.173.14 to www.willows-consulting.com is

    C:\Users\Willows-Lap3>tracert www.willows-consulting.com
    Unable to resolve target system name www.willows-consulting.com.

    C:\Users\Willows-Lap3>tracert 78.137.164.79

    Tracing route to lh39.dnsireland.com [78.137.164.79]
    over a maximum of 30 hops:

    1 11 ms 9 ms 9 ms 109.255.172.1
    2 9 ms 11 ms 18 ms 109.255.255.254
    3 10 ms 9 ms 10 ms 84.116.238.42
    4 13 ms 9 ms 9 ms to-inex-dub-deg-gw.digiweb.ie [193.242.111.20]
    5 11 ms 10 ms 9 ms lh39.dnsireland.com [78.137.164.79]

    Trace complete.

    This is starting to look like a routing issue with the hoster,
    I have rebooted the local router and reset it to factory settings and this has made no difference. Not that I could ask my clients to do this every time they need to access my website.

    I can access the site from magnet networks, and my iphones tethered connection.


    The trace route to www.willows-consulting.com reads

    TraceRoute from Network-Tools.com to 78.137.164.79 [www.willows-consulting.com]
    [TABLE="width: 100"]
    [TR]
    [TD]Hop[/TD]
    [TD](ms)[/TD]
    [TD](ms)[/TD]
    [TD](ms)[/TD]
    [TD][/TD]
    [TD] IP Address[/TD]
    [TD]Host name[/TD]
    [/TR]
    [/TABLE]

    [TABLE="width: 100"]
    [TR]
    [TD]1 [/TD]
    [TD] 1 [/TD]
    [TD] 0 [/TD]
    [TD] 0 [/TD]
    [TD] 8.9.232.73[/TD]
    [TD] xe-5-3-0.edge3.dallas1.level3.net [/TD]
    [/TR]
    [/TABLE]
    [TABLE="width: 100"]
    [TR]
    [TD]2 [/TD]
    [TD] 0 [/TD]
    [TD] 0 [/TD]
    [TD] 0 [/TD]
    [TD] 4.69.145.254[/TD]
    [TD] vlan90.csw4.dallas1.level3.net [/TD]
    [/TR]
    [/TABLE]
    [TABLE="width: 100"]
    [TR]
    [TD]3 [/TD]
    [TD] 0 [/TD]
    [TD] 0 [/TD]
    [TD] 1 [/TD]
    [TD] 4.69.151.170[/TD]
    [TD] ae-93-93.ebr3.dallas1.level3.net [/TD]
    [/TR]
    [/TABLE]
    [TABLE="width: 100"]
    [TR]
    [TD]4 [/TD]
    [TD] 20 [/TD]
    [TD] 21 [/TD]
    [TD] 20 [/TD]
    [TD] 4.69.134.22[/TD]
    [TD] ae-7-7.ebr3.atlanta2.level3.net [/TD]
    [/TR]
    [/TABLE]
    [TABLE="width: 100"]
    [TR]
    [TD]5 [/TD]
    [TD] 34 [/TD]
    [TD] 33 [/TD]
    [TD] 34 [/TD]
    [TD] 4.69.132.86[/TD]
    [TD] ae-2-2.ebr1.washington1.level3.net [/TD]
    [/TR]
    [/TABLE]
    [TABLE="width: 100"]
    [TR]
    [TD]6 [/TD]
    [TD] 33 [/TD]
    [TD] 45 [/TD]
    [TD] 33 [/TD]
    [TD] 4.69.134.134[/TD]
    [TD] ae-71-71.csw2.washington1.level3.net [/TD]
    [/TR]
    [/TABLE]
    [TABLE="width: 100"]
    [TR]
    [TD]7 [/TD]
    [TD] 33 [/TD]
    [TD] 33 [/TD]
    [TD] 33 [/TD]
    [TD] 4.69.134.149[/TD]
    [TD] ae-72-72.ebr2.washington1.level3.net [/TD]
    [/TR]
    [/TABLE]
    [TABLE="width: 100"]
    [TR]
    [TD]8 [/TD]
    [TD] 114 [/TD]
    [TD] 114 [/TD]
    [TD] 114 [/TD]
    [TD] 4.69.137.53[/TD]
    [TD] ae-42-42.ebr2.paris1.level3.net [/TD]
    [/TR]
    [/TABLE]
    [TABLE="width: 100"]
    [TR]
    [TD]9 [/TD]
    [TD] 184 [/TD]
    [TD] 207 [/TD]
    [TD] 212 [/TD]
    [TD] 4.69.148.53[/TD]
    [TD] ae-6-6.car1.dublin3.level3.net [/TD]
    [/TR]
    [/TABLE]
    [TABLE="width: 100"]
    [TR]
    [TD]10 [/TD]
    [TD] 130 [/TD]
    [TD] 130 [/TD]
    [TD] 130 [/TD]
    [TD] 4.69.148.58[/TD]
    [TD] ae-7-7.car2.dublin1.level3.net [/TD]
    [/TR]
    [/TABLE]
    [TABLE="width: 100"]
    [TR]
    [TD]11 [/TD]
    [TD] 131 [/TD]
    [TD] 131 [/TD]
    [TD] 131 [/TD]
    [TD] 213.242.106.78[/TD]
    [TD] - [/TD]
    [/TR]
    [/TABLE]
    [TABLE="width: 100"]
    [TR]
    [TD]12 [/TD]
    [TD] 132 [/TD]
    [TD] 131 [/TD]
    [TD] 131 [/TD]
    [TD] 78.137.164.79[/TD]
    [TD] lh39.dnsireland.com [/TD]
    [/TR]
    [/TABLE]
    Trace complete

    The trace of the ip address 109.255.173.14 to www.willows-consulting.com is

    C:\Users\Willows-Lap3>tracert www.willows-consulting.com
    Unable to resolve target system name www.willows-consulting.com.


    C:\Users\Willows-Lap3>tracert 78.137.164.79

    Tracing route to lh39.dnsireland.com [78.137.164.79]
    over a maximum of 30 hops:
    1 11 ms 9 ms 9 ms 109.255.172.1
    2 9 ms 11 ms 18 ms 109.255.255.254
    3 10 ms 9 ms 10 ms 84.116.238.42
    4 13 ms 9 ms 9 ms to-inex-dub-deg-gw.digiweb.ie [193.242.111.20]
    5 11 ms 10 ms 9 ms lh39.dnsireland.com [78.137.164.79]
    Trace complete.

    I have rebooted the local router and reset it to factory settings and this has made no difference. Not that I could ask my clients to do this every time they need to access my website.

    So I am asking the good DNS genius's out there to have a look and if they have seen this issue before and solved it to let me know.

    Many thanks for taking the time to read all the details.
     
  2. mneylon

    mneylon Administrator Staff Member

    It sounds like a DNS caching issue.

    Running it through our tool I'm seeing that there are still records on the hosting365 nameservers.. now none of the ISPs should be using those records, but if you could check what their resolvers are seeing then you'd probably be closer to finding a fix.
    I know that Vodafone has had odd issues with their resolvers retaining stale records for several weeks, so other ISPs might suffer from similar issues
     

Share This Page