Do you mind checking these URL's?

Discussion in 'Non Technical' started by tHeSmUrF, Dec 6, 2006.

  1. tHeSmUrF

    tHeSmUrF tHeSmUrF

    Hi,

    I'm having a few problems with four domain names. They seem to work ok except with Telstra and Internode customers....but of course they said nothing is wrong, go talk to the hosting company....who also say nothing is wrong.

    I really don't think it is the hosting companies problem as the domains work fine when using other providers (e.g. my work network).

    Can you try clicking the four below domains and letting me know if they work or don't work, and who your ISP is? The first three should bring up just a black page with a message about this being the future site of chalkagency.

    http://www.chalkagency.com.au
    http://www.chalkagency.com
    http://www.chalkagency.net.au

    As a test I'm pointing this next one to a different hosting account and also using different Name Servers to the above. This one should take you to a fresh joolma page:
    http://www.chalkagency.net

    Thank you for doing this, I just need to prove it is or isn't an ISP related issue and didn't know where else to ask.

    Cheers
    Mark
     
  2. Zeo

    Zeo Active Member

    I am with Internode. The first 3 were ok the last one didnt get through. Have you tried pinging the sites?
     
  3. tHeSmUrF

    tHeSmUrF tHeSmUrF

    Can't resolve DNS, so can't ping or tracert

    Hi Zeo, yep I can't ping them from any of my Internode connected machines (have three machines on two seperate Internode accounts..seperate phone lines etc). Can't resolve the DNS, so pings don't work. Also can't resolve on a MAC (spit, spit, spit) connect via a Bigpond account.

    They said the TTL was set a little high on the domain details and so may not have been getting updated DNS details. I waiting until the TTL was reached (last Friday) and the domains started working fine for me. Until I noticed on Sunday they had stopped again. It's really pissing me off as everyone is blaming everyone else....of course.

    Using the tools at dnsstuff.com seem to show everything working again (except the second NS sometimes times out).

    Thank you for trying, kinda disappointed it worked for you :)

    Cheers
    Mark

     
  4. red32

    red32 You talkin' to me?

    All four worked for me, Mark. I'm with Telstra (Bigpond.net.au) cable
     
  5. tHeSmUrF

    tHeSmUrF tHeSmUrF

    Thank you for testing this.

    Still seems to be something dodgy with the DNS resolution.

    Cheers
    Mark

     
  6. Zeo

    Zeo Active Member

    Just went back again and the same as before. Sorry.:zlove:
     
  7. Marklar

    Marklar gruntled

    The first three worked fine, the last said the page was offline.
    I'm on Optus.
     
  8. Gazza

    Gazza Active Member

    First three worked for me, the last one had not loaded up after 5 mins. Im with Kooee using dial up....
     
  9. CurnZ

    CurnZ zero rwkw

    All links worked for me. Sounds like DNS issue on the ISPs end I would say. Cache time to high? For those interested you can read up on how DNS works here: http://en.wikipedia.org/wiki/DNS

    nslookup:

    Code:
    > www.chalkagency.com.au
    Server:  dnscache01.westnet.com.au
    Address:  203.21.20.20
    
    Non-authoritative answer:
    Name:    www.chalkagency.com.au
    Address:  75.126.27.171
    
    > www.chalkagency.com
    Server:  dnscache01.westnet.com.au
    Address:  203.21.20.20
    
    Non-authoritative answer:
    Name:    www.chalkagency.com
    Address:  75.126.27.171
    
    > www.chalkagency.net.au
    Server:  dnscache01.westnet.com.au
    Address:  203.21.20.20
    
    Non-authoritative answer:
    Name:    www.chalkagency.net.au
    Address:  75.126.27.171
    
    > www.chalkagency.net
    Server:  dnscache01.westnet.com.au
    Address:  203.21.20.20
    
    *** dnscache01.westnet.com.au can't find www.chalkagency.net: Server failed
    > server dnscache02.westnet.com.au
    Default Server:  dnscache02.westnet.com.au
    Address:  203.10.1.9
    
    > www.chalkagency.net
    Server:  dnscache02.westnet.com.au
    Address:  203.10.1.9
    
    Non-authoritative answer:
    Name:    www.chalkagency.net
    Address:  208.101.48.244
     
    Last edited: Dec 7, 2006
  10. black baz

    black baz black 'n blue Bazemy

    first three fine with me .. 4th, "server not found" ...

    i'm with iinet.net.au as an isp and using firefox as a browser ....
     
  11. Fast_Z

    Fast_Z New Member

    Its called DNS Propagation

    In real simple terms, DNS Propagation can sometimes take several days depending on when different ISP's have their Domain Name Server set to refresh, typically a company like Telstra in an attempt to save costs sets the DNS refresh to a longer period and thus why people who use Telstra getting different results to those smarter people who do not.
     
  12. CHILI

    CHILI Indestructable Target

    Hi Mark,
    All four behave exactly as described by you. I am using Telstra ADSL Broadband and Mozilla Firefox 2.0 browser.

     
  13. TAzZie

    TAzZie Mumbler

    Dial-up from DoDo Works all 4

    Dodo Dial up works on all 4 from my Work here
    and they all work from My works main Intranet.
     
  14. black baz

    black baz black 'n blue Bazemy

    correction by black baz .... all 4 now work for me .. it

    turns out that my ISP was in the process of falling into a screaming heap just as i was checking that url last night .. just back up this am and all is well ..:(





     
  15. Egg

    Egg ....

    All worked for me with...

    ...internode.
     
  16. tHeSmUrF

    tHeSmUrF tHeSmUrF

    Yeap TTL was set incorrectly

    and so new settings weren't getting updated. Also turned out to be incorrect entries in the two name servers at the host (were giving out different details for the same domains).

    Thanks for your help
    Cheers
    Mark

     
  17. tHeSmUrF

    tHeSmUrF tHeSmUrF

    Yep thanks, I know what DNS propagation is.

    It turned out to be multiple issues. TTL was set to high and so new settings weren't getting updated. Also turned out to be incorrect entries in the two name servers at the host (were giving out different details for the same domains). They have now fixed that and all seem good :)

    Thanks for your help
    Cheers
    Mark


     
  18. tHeSmUrF

    tHeSmUrF tHeSmUrF

    Thanks Chili, all looks to be working now.

    Was mostly a problem with NS details at the host company.

    Cheers
    Mark

     
  19. tHeSmUrF

    tHeSmUrF tHeSmUrF

    Thanks for that Egg. Turned out to be a host and registration problem.

    Thanks for your help.

    Cheers
    Mark

     
  20. ltd

    ltd Linux Ninja

    First three work, the last one does not. (iiNet)

     

Share This Page