Level 3 DNS servers in USA not routing to oook?

Collapse
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • Ghen
    Apprentice
    • Jun 2007
    • 70
    #1

    Level 3 DNS servers in USA not routing to oook?

    I've been switching between OpenDNS, Comcast, and Level3 DNS servers for different reasons. I've found though, that Level 3 servers (4.2.2.1 , 4.2.2.2) just won't rout to angband.oook.cz at all. So to get here I have to change my DNS server to comcast or OpenDNS and it lets me through.

    I can't just skip DNS either by using the hosts file because angband.oook.cz translates to http://195.250.144.108/ which goes to the main website and won't link here by IP.

    Anyone noticed Level 3 not routing to .cz or other domains? Any other issues like that with oook.cz?
    Tags: None
    • konijn_
      Hellband maintainer
      • Jul 2007
      • 367
      #2
      Works fine from NY,NY

      Go east coast !
      * Are you ready for something else ? Hellband 0.8.8 is out! *

        Comment

        • PowerDiver
          Prophet
          • Mar 2008
          • 2820
          #3
          Originally posted by Ghen
          Anyone noticed Level 3 not routing to .cz or other domains? Any other issues like that with oook.cz?
          Yesterday, I could never connect the first time. A second attempt usually got through. I have no idea how much was DNS vs server problems. Seems back to normal today.

            Comment

            • zaimoni
              Knight
              • Apr 2007
              • 590
              #4
              Originally posted by Ghen
              I've been switching between OpenDNS, Comcast, and Level3 DNS servers for different reasons. I've found though, that Level 3 servers (4.2.2.1 , 4.2.2.2) just won't rout to angband.oook.cz at all. So to get here I have to change my DNS server to comcast or OpenDNS and it lets me through.
              It's not just Level 3. I have to use OpenDNS to reliably get to any website in the EU.
              Zaiband: end the "I shouldn't have survived that" experience. V3.0.6 fork on Hg.
              Zaiband 3.0.10 ETA Mar. 7 2011 (Yes, schedule slipped. Latest testing indicates not enough assert() calls to allow release.)
              Z.C++: pre-alpha C/C++ compiler system (usable preprocessor). Also on Hg. Z.C++ 0.0.10 ETA December 31 2011

                Comment

                • Ghen
                  Apprentice
                  • Jun 2007
                  • 70
                  #5
                  Originally posted by PowerDiver
                  Yesterday, I could never connect the first time. A second attempt usually got through. I have no idea how much was DNS vs server problems. Seems back to normal today.

                  Mine is frighteningly consistent. If I change DNS and then flush the cache or reboot the computer then it just won't work so yours was probably just one time

                    Comment

                    • pav
                      Administrator
                      • Apr 2007
                      • 793
                      #6
                      Originally posted by PowerDiver
                      Yesterday, I could never connect the first time. A second attempt usually got through. I have no idea how much was DNS vs server problems. Seems back to normal today.
                      Any chance your browser is sending AAAA query first, and the recursor is choking on these? Second try would be sending regular A query, which would work ...

                      Just a thought.
                      See the elves and everything! http://angband.oook.cz

                        Comment

                        • sandtrap
                          Scout
                          • Nov 2008
                          • 26
                          #7
                          Saint Louis MO USA AT&T okay

                          never had a problem

                            Comment

                            • PowerDiver
                              Prophet
                              • Mar 2008
                              • 2820
                              #8
                              Originally posted by pav
                              Any chance your browser is sending AAAA query first, and the recursor is choking on these? Second try would be sending regular A query, which would work ...

                              Just a thought.
                              I have no clue what you are talking about. It's a pretty old firefox if that matters, and it was just for a couple of days.

                                Comment

                                Previous template Next
                                Working...
                                😀
                                😂
                                🥰
                                😘
                                🤢
                                😎
                                😞
                                😡
                                👍
                                👎
                                ☕