Two weeks and counting

[cmdr_zoom]

That's two weeks now that my reverse DNS has been broken, courtesy of qwest; two weeks without the ability to send email or update my homepage, except by complicated workarounds.

For such a small and stupid error, that might be affecting up to 255 customers, they sure are taking their sweet time about fixing it.

In the words of Lily Tomlin:
"We don't care; we don't have to. We're the Phone Company."

Comments

[z-gryphon.livejournal.com]

I realize that this is a question so stupid as to border on the outright idiotic, but... they are aware of this problem, right?

[ardaniel]

Kel's emailed and attempted to call their DSL support line, *I've* emailed requesting that the issue be referred to the DNS team, etc.

Nothin'.

Cmdr_zoom and ardaniel:

[biomekanic.livejournal.com]

I need a few things from you:
-your phone numbers
-who you've talked to
-your ISP
-what exactly is the issue, and please keep the Geekese to a minimum, my fragile little mind can't handle much of that today.
Leave me a message at home, Kelly has my number.
The problem may not be us, but might be the ISP (I've run into situations before were we can't get access to the facilities to make repairs), I'll let you know I find out ASAP.

Re: Cmdr_zoom and ardaniel:

[cmdr-zoom.livejournal.com]

You've got mine.
I called qwest DSL service.
My building is wired by qwest, but I use EFN for my email still.
My IP is currently resolving as 67.42.57.134.57.42.67.in-addr.arpa (67.42.57.134) ... which at the start was amusing in its sheer brokenness, but has become less so in the two weeks following.
I am told by Ard that the problem (1) affects the entire block at the end (.57.1-255); (2) that the blocks to either side are legitimate uswest (or was it qwest?) customer IPs; and (3) that it is almost certainly due to someone at qwest leaving out a . at the end of an entry.

Ard, would you care to correct or elaborate?

[abiku.livejournal.com]

dubhain contacted me and asked me to look into this problem for you. (The support request didn't make it to my particular group--and it probably never will--but I built the nameservers and have full access to them, so I can fix the problem.)

The original cause of the problem was a bug in one of our internal web tools--used by the majority of our support groups--which dropped the trailing "." after part of the $GENERATE statement. This, of course, is a Very Bad Thing. I've notified our lead developer of the bug and, with any luck, he'll fix it ASAP so this doesn't happen again in the future.

The problem with the 57.42.67.in-addr.arpa zone will be fixed by tomorrow morning at the latest. (My login on the master nameserver expired, since I rarely have to use it anymore, and I'm waiting for the admins of that particular machine to reset it for me so I can bypass the "user-friendly" web interface and just edit the zone file manually.)

I'm sorry for the huge headaches this must be causing you. I know I, as a customer, would be furious. As an employee who fought for over a year against the change to this particular DNS management setup, it pisses me off, too. ::sigh::

If you're still seeing the problem by tomorrow evening, please feel free to contact me directly at postmaster@qwest.net and I will look into it further.

[cmdr-zoom.livejournal.com]

Thank you!

[abiku.livejournal.com]

Well, it looks like our authoritative nameservers know about the change, which means it'll probably start propagating as soon as the cached zones expire on the resolvers around the net.

nexus[1] date
Tue Aug 26 13:37:40 CDT 2003
nexus[2] nslookup 67.42.57.134 authns1.mpls.qwest.net
Server: authns1.mpls.qwest.net
Address: 63.231.205.1

Name: 67-42-57-134.eugn.qwest.net
Address: 67.42.57.134

With any luck, you should be good by later this evening.