Aces High Bulletin Board
General Forums => Aces High General Discussion => Topic started by: hblair on August 05, 2002, 01:32:00 PM
-
I can't view the board using DNS, gotta do this..
http://216.91.192.19/forums/index.php?s=
-
Looks like thier DNS servers are not responding to anyone.. Or there is a cache poison somewhere out there.... If you do a lookup off them direct it works... Otherwise you de SERVERFAIL.. I'd say hey need to have a talk with the ISP ASAP...
See-ya
mdbaker
-
Its not necessarily HTC's DNS that has to have the problem... I thought that most IPS providers had their own DNS that should look up HTC. Not sure how that process goes... if they just attatch an IP addy or if it actually querries the IP addy first... I guess that's where skuzzy needs to chime in.
Hey Skuzzy? You reading this? If so... GET BACK TO WORK! ;)
AKDejaVu
-
Houston, we have a problem.
Thanks for posting this in BW, HB.
ATC
(http://www.damned.org/images/ddemo1.gif)
-
What happens is when you got to a web site.. you will query your ISP's DNS first.. if it has the IP to match the name in cache then it will use that to send the packets on the the destination.. If the cache does not have a match then it will start down in this case .com tree to find out who is the athority for (again in this case) hitechcreations.com... The root .com server will the the ISP server... Hey ask so-in-so he should know..... so the request if sent on until it gets to a server which is suppose to know.. Since I control our servers I can flush the cache... but I checked it from 2 different domains.. on in the .edu and on in the .net so they take different routes and both give a SERVERFAIL message.. meaning they tried but the server would not or could not give the info needed...
See-ya
mdbaker
106th Air Group (http://www.106thvag.org)
-
Oh and yes if you use the IP address directly, it will bypass any lookups so you can get there direct.. that is what I did....
See-ya
mdbaker
-
Originally posted by ATC
Houston, we have a problem.
Thanks for posting this in BW, HB.
Yes, many thanks, hblair! Just wish I had read BW earlier - flying time now! :D
-
Well currently I can't even ping the IP from my home machine. There seems to be a severe DNS problem somewhere. It looks like the domain's DNS was transfered, and the old DNS servers are dead, long before the changes have propagated. HTC's new dns servers seem to be up, but the old, now non-existant servers are still being used by the rootserver.
Blah, any word from HTC on what happened? Fire? Sysadmin have an incident with the dns server and a large axe?
Thank god for lynx lol
Oddly enough, It's the people who's ISP's keep the caches forever that are still going now. Normally those caches cause the problems :D
--edit--
Connection issue was my problem, btw.
-
HTC has moved their domain to new dns. When moving a domain to new dns, it's best to leave the old servers hosting the domain until the change propagates to the rest of the net. Apparently the old Applink DNS stopped serving hitechcreations.com sometime yesterday and your local ISPs dns caches expired the zone file. That's why it looked like this site fell off the face of the earth. Everything should be back to normal within 24 hours.
Luckily the game runs off IP addresses and not hostnames. ;)
-
I haven't been able to reach hitechcreations.com since mid Sunday, and still can't tonight (Monday). I finally got here by temporarilly setting dns.hitechcreation.com's IP as my primary DNS. I'll un-set that shortly, but just a heads up, it's still in-accessible from my work systems (at symantec.com) or via my ISP (AT&T Broadband). When I change DNS info for one of my domains, it usually propagates within 6-12 hours, this has been over 24 so far.
-
Why not use http://216.91.192.19/forums/index.php and skip the change to your config?
-
Well gosh, I couldn't resolve the IP of the web server without hooking up to a DNS that knew the new address. I just did a WHOIS, saw the DNS IP, then used it long enough to get the IP.
How'd you know the IP address?
Either way, it's moot now, I've got the new IP cached, so I'm already back to using my old DNS.
-
Originally posted by Chairboy
How'd you know the IP address?
It's the first post in this thread. :)
BTW... I think the DNS is still fouled up. Did a check with WSPING and hitechcreations is not found...
-
See, that's why I didn't just use the IP, unlike some of you, I had to work to get my AH BBS fix! : )
-
Well, I'm not 100% sure, but I think they've got some bugs in their nameserver setup. The nameserver doesn't seem to be giving out the zone file. You can query the nameserver directly and it works, but going through your own ISPs DNS will fail since your ISPs DNS is trying to grab the whole zone file and not just the 'www' address.
-
The problem is that the rootservers are still pointing towards the old DNS server. As soon as they update it'll work.
I'd still like to know why the original DNS was shut down before the new one was operational. SOMETHING must have caught fire.
-
It's coming up on two days now since the DNS change, that seems somewhat excessive. My DNS changes usually propagate in a few hours. I wonder what the hold up is?
-
http://216.91.192.19/forums/index.php works, but it's ugly.
http://www.hitechcreations.com won't give me an IP in germany, had to figure it elsewhere in the web.
-
WOW look at this, everyone got an chance to strutt their technical SkiLZZ :D
It aint working from sweden either... the url http://www.hitechcreation.com works tough, but thats just the intro page....
http://www.hitechcreations.com com is dead.
-
hehehe.. I got skilzzz... Just added the IP address to my /etc/hosts file No prob.. when they get things fixed .. remove it.. No problem... :D
I know *I* would be shot... (and that is the good part) if I did a major change to out DNS and didn't keep backups online until we were sure they worked..
Oh well.. It could be worse.....
See-ya
mdbaker
106th Air Group (Anything - Anywhere - Anytime) (http://www.106thvag.org)
-
Originally posted by Innominate
The problem is that the rootservers are still pointing towards the old DNS server. As soon as they update it'll work.
Yea.. but since the root servers only give back what they are told.. Someone or something has messed up... They are showing that the name servers should be DNS and DNS2 with IP addresses of 216.91.192.1 and 216.91.192.2 which matches the whois entry... So from the dig I did from here it looks like the root servers match the registrars record... If I use the IP addresses of DNS or DNS2 to bounce the DNS request off of.. it works as well. From a basic setup standpoint, they seem to be servering names... Could be as simple as an IP acl... Oh well all speculation from the outside... but that is the fun part.. Anyone want to start a pool on the exact probem??? :cool: :cool:
See-ya
mdbaker
106th Air Group (Anything - Anywhere -Anytime) (http://www.106thvag.org)
-
actually it goes to ARPA off the root of the Internet right after the first query.. then recrusvie until it finally gets an answer..
hey wait.. you said that.
day late, dollar short
and I MISSED THE CON>> damnit
-
I've also added this into the hosts file.
Theres alot of entries...
For some sites I regularly visit and then some addy/track sites redirected to "null" :)
-
my understanding is that the first request is itterative and the following ones (responding to the first local DNS) are recursive.
the root passes on to the next (.com or whatever) and on down the line until the first DNS server gets an answer. Then it responds to the query (you).
-
The "fault" was simple.
The nameservers for the HTC domain were changed in the whois database. The whois databases often take time to sync with the root servers. The root servers were still pointing at the old DNS servers, which knew nothing about the htc domain anymore.
During this time, people who's isps had cached the IP could still connect, untill that ran out. Those whose isps didn't have the IP cached got the DNS errors. And now that the root servers are fixed, the people who's isps had cached the old dns server, which doesn's exist, will continue to receive errors untill the cache expires.
-
'zactly..
now can we move on ?
I wanna' see nominees for Babe of the Week !!!
-
Correct,...propagation delay due to expiration of DNS caches in the local ISP DNS servers cause delays for full propagation by the timestamp in the SOA header of the domain record.
In this case, the expiration is 2 weeks. Although refreshes are set to 24 hours.
Now, why the change?
Well folks, AppLink is about to close shop and I will be in the market for a job. I won't bore you with the details.
The transition of the HTC domain was supposed to go smoother, but some miscommunications occurred and that is what caused the overall problem.
I want to stress, it was not an error on HTC's part that caused the problem.
On a more personal note. Sorry I missed the CON this year, but I had to get my stuff moved out of the office. Going to miss you lugs, as of tomorrow, I will not have an Internet connection and do not know when I will be back.
On the congestion with the CT/TA areanas. During this shutdown of AppLink I had to put everyone through the last remaining Internet backbone connection. This is causing congestion and problems with connections to the CT/TA.
Again, not HTC's fault. Put it on me, not them. They were caught a bit off gaurd by all this and had the CON to deal with as well.
The gang at HTC are some of the best people I have ever had the pleasure of being associated with and the community here is a great one. to all.
Now,..cook my goose.
-
We'll miss ya Skuzzy.
:(
(http://www.boomspeed.com/swoop/logo_small.jpg)
-
Sorry to hear that Skuzzy. Let us know when you land on your feet.
-
Hope all is well skuzzy. Best of luck to you in the future man, and please don't run off! Get an account and join us in the arenas. Don't disappear on us!
-
no doubt!! good luck and hurry back !
-
Best of luck to you Skuzzy!
Sorry I didn't get to meet you at the con.
-
Welcome to umark.com!
-
Skuzzy
-
Sorry to hear that Skuzzy, but my main consern is : will this affect my pingtimes to the MA ?
Without you there , I am afraid, very afraid.....
I am shure you will come down on your feet, I really hope so :)
Lasse