Results 1 to 5 of 5
  1. #1
    Join Date
    Feb 2004
    Location
    Bay Area, CA
    Posts
    521

    Help testing Cogent DNS on a Cogent line

    I am having a strange DNS issue on a Cogent circuit using Cogent DNS servers at 66.28.0.45 and 66.28.0.61. What is happening is that some domain requests will timeout the first try. Then subsequent tries will be quick with no timeouts.

    I am having a very hard time getting through to Cogent that there might be an issue somewhere and I was wondering if anyone on a Cogent line using the same Cogent DNS servers could also do a test for me to and see if you can reproduce any timeouts.

    How I am testing:
    - Open nslookup (in linux use: nslookup -timeout=2, windows defaults to 2 seconds)
    - Picking a random domain name (favorite cereal.com, movie title.com, brand name.com, random word.com)
    - Repeating test for same domain if timeout occurs to see the next query resolve instantly

    Here is an example of what Is happening for me:
    Code:
    [eger@womp ~]# nslookup -timeout=2
    > superman.com
    ;; connection timed out; no servers could be reached
    > superman.com
    Server:         66.28.0.45
    Address:        66.28.0.45#53
    
    Non-authoritative answer:
    Name:   superman.com
    Address: 64.12.47.7
    > napaautoparts.com
    ;; connection timed out; no servers could be reached
    > napaautoparts.com
    Server:         66.28.0.45
    Address:        66.28.0.45#53
    
    Non-authoritative answer:
    Name:   napaautoparts.com
    Address: 208.254.241.70
    >
    I picked 2 random domains (that were likely not cached at the name server) and they both timeout the first try. Anyone else able to replicate this?

  2. #2
    I'm not on Cogent, but I got the same results you did (timeout on first try, then ok after that)

  3. #3
    Join Date
    Feb 2003
    Location
    North Hollywood, CA
    Posts
    2,548
    Overloaded DNS servers maybe? no idea really.

    I use 4.2.2.2 or 4.2.2.1
    Remote Hands and Your Local Tech for the Los Angeles area.

    (310) 573-8050 - LinkedIn

  4. #4
    Join Date
    Feb 2004
    Location
    Bay Area, CA
    Posts
    521
    Quote Originally Posted by Jeremy
    Overloaded DNS servers maybe? no idea really.

    I use 4.2.2.2 or 4.2.2.1
    Strange thing is, I also tested 4.2.2.1 and 4.2.2.2 using Cogent and same problem happens. Get random timeouts on domains the first try.

  5. #5
    Join Date
    Feb 2003
    Location
    North Hollywood, CA
    Posts
    2,548
    hmm i dont have a problem against 4.2.2.2 / .1

    Testing against cogent i get timeouts, network problem ??
    Remote Hands and Your Local Tech for the Los Angeles area.

    (310) 573-8050 - LinkedIn

  6. Newsletters

    Subscribe Now & Get The WHT Quick Start Guide!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •