Author Topic: What's up with the DNS stuff? (Read 528 times)

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=

GhostRider2110 · « **Reply #1 on:** August 05, 2002, 01:40:18 PM »

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

AKDejaVu · « **Reply #2 on:** August 05, 2002, 02:06:49 PM »

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

ATC · « **Reply #3 on:** August 05, 2002, 02:21:35 PM »

Houston, we have a problem.

Thanks for posting this in BW, HB.

ATC

GhostRider2110 · « **Reply #4 on:** August 05, 2002, 02:33:53 PM »

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

GhostRider2110 · « **Reply #5 on:** August 05, 2002, 02:35:26 PM »

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

Flossy · « **Reply #6 on:** August 05, 2002, 04:41:22 PM »

Quote

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!

Innominate · « **Reply #7 on:** August 05, 2002, 05:20:40 PM »

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

--edit--
Connection issue was my problem, btw.

Sancho · « **Reply #8 on:** August 05, 2002, 06:12:35 PM »

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.

Chairboy · « **Reply #9 on:** August 05, 2002, 10:49:16 PM »

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.

Sandman · « **Reply #10 on:** August 05, 2002, 10:57:53 PM »

Why not use http://216.91.192.19/forums/index.php and skip the change to your config?

Chairboy · « **Reply #11 on:** August 05, 2002, 11:16:07 PM »

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.

Sandman · « **Reply #12 on:** August 05, 2002, 11:22:26 PM »

Quote

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...

Chairboy · « **Reply #13 on:** August 05, 2002, 11:35:50 PM »

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! : )

Sancho · « **Reply #14 on:** August 06, 2002, 12:10:41 AM »

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.