Monday, Debtember 03, 2001
DNS and VeriSigh Woes
I found out from Mark that the secondary DNS server has changed IP address and I've neglected to fix the appropriate domain registration records.
Also today I received a letter from VeriSign letting me
know of my new account information. Gone are the days that I'm known as
SC74 in the InterNIC domain database. Sigh.
So I guess that means no more email templates. Double sigh.
So I sign in like the letter says, to update the records for at least my own domain and wouldn't you know it—it doesn't accept IP addresses for DNS servers. And my secondary DNS server has been registered with the InterNIC and it still has the old address.
So I'll have to wait until Kelly makes the appropriate changes.
Finally!
I've been working on this project for a bit over a week, and I finally, finally got it working. For the entire week I was fighting what appeared to be a loosing battle with a Microsoft IIS server when all of a sudden it started working.
I had been working on the project today and appeared to be regressing at an
alarming rate as I was tweaking code that by all rights should work
when I made a final tweak (isolating the code that builds the client
headers for the GET and POST commands into a single common
routine) so that I could be sure of what headers I was sending for which
methods (I need both for this site)) and Lo! It worked!
Looking over the code I see that the only change from the headers I was
sending before have the Cookie: header being sent back as the
second header instead of the third.
This, on top of the other bugs I have to code around. Grrrrrrrrrrr …
