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

Innominate · « **Reply #15 on:** August 06, 2002, 02:33:24 AM »

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.

Chairboy · « **Reply #16 on:** August 06, 2002, 02:38:02 AM »

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?

devious · « **Reply #17 on:** August 06, 2002, 03:02:21 AM »

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.

Maniac · « **Reply #18 on:** August 06, 2002, 04:00:58 AM »

WOW look at this, everyone got an chance to strutt their technical SkiLZZ

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.

GhostRider2110 · « **Reply #19 on:** August 06, 2002, 08:48:32 AM »

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

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)

GhostRider2110 · « **Reply #20 on:** August 06, 2002, 08:59:54 AM »

Quote

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

See-ya
mdbaker
106th Air Group (Anything - Anywhere -Anytime)

Wlfgng · « **Reply #21 on:** August 06, 2002, 11:28:26 AM »

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

Fishu · « **Reply #22 on:** August 06, 2002, 01:41:52 PM »

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"

Wlfgng · « **Reply #23 on:** August 06, 2002, 02:59:00 PM »

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

Innominate · « **Reply #24 on:** August 06, 2002, 03:31:51 PM »

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.

Wlfgng · « **Reply #25 on:** August 06, 2002, 04:17:52 PM »

'zactly..
now can we move on ?

I wanna' see nominees for Babe of the Week !!!

Skuzzy · « **Reply #26 on:** August 06, 2002, 05:39:07 PM »

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.

Swoop · « **Reply #27 on:** August 06, 2002, 05:50:01 PM »

We'll miss ya Skuzzy.

majic · « **Reply #28 on:** August 06, 2002, 06:10:49 PM »

Sorry to hear that Skuzzy. Let us know when you land on your feet.

hblair · « **Reply #29 on:** August 06, 2002, 06:57:07 PM »

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!