Not horribly on topic, but perhaps there is a united.com person listening:
www.united.com's NS servers are -
dns01.uls-prod.com.
dns02.uls-prod.com.
DNS01 seems 'fine' (responds atleast)
DNS02 seems to return 'servefail' for everything...
Servefail seems to make cache dns servers not attempt lookups from the
other NS's on record. This seems 'bad', if your dns server is busted could
you just null route it or turn it off?
Actually, now as I test both NS's are toasted 
Hope the record's TTL is
long enough for you.
-Chris
whois and "dig +trace" show that www.united.com's servers are now:
dc1lbs1.uls-prod.com
dc2lbs1.uls-prod.com
maybe the dns changes were recently made and are still "in-flight"... (ducks)
Not horribly on topic, but perhaps there is a united.com person listening:
www.united.com's NS servers are -
dns01.uls-prod.com.
dns02.uls-prod.com.
whois and "dig +trace" show that www.united.com's servers are now:
dc1lbs1.uls-prod.com
dc2lbs1.uls-prod.com
maybe the dns changes were recently made and are still "in-flight"... (ducks)
% host dns01.uls-prod.com
dns01.uls-prod.com has address 209.87.112.200
% host dns02.uls-prod.com
dns02.uls-prod.com has address 209.87.113.200
% host dc1lbs1.uls-prod.com
dc1lbs1.uls-prod.com has address 209.87.112.4
% host dc2lbs1.uls-prod.com
dc2lbs1.uls-prod.com has address 209.87.113.4
love that 2182
i don't think so, the united.com domain was those two earlier today, with
www.united.com NS from dns01/02.uls-prod.com ... though I've seen this
situation change some throughout the day as well with the dcXlbs1 boxes in
the mix as well. Asking direcly from dns01/02 gets you records for SOME
things but not others and servfail 'often' for www.united.com.
Someone else pointed out that this is not a 'new' situation and has been
the case for about 3-4 weeks so far... their POC's on the domains:
united.com
ual.com
uls-prod.com
are all invalid/dead/not-answering... perhaps someone will be watching
nanog, perhaps they will continue to be busted Oh well.
yeah, ok, the situation appears slightly more messed up than originally
surmised.
the dcXlbs1 boxes are the ones pointed to by the root. unfortunately,
they think the dns0X boxes are the nameservers (though that doesn't matter
if you don't ask dcXlbs1 for NS records).
also of note is the SOA serial number is 20050503 (four weeks ago).
also interesting is that the whois/registry for uls-prod.com says
that it's expired.
maybe it was still on-the-fly after all. whois united.com now shows
dcXlbs1 as the name servers, and a flush of the local nameserver here
now has www.united.com resolving properly.
Registrar Name....: REGISTER.COM, INC.
Registrar Whois...: whois.register.com
Registrar Homepage: www.register.com
Domain Name: united.com
Created on..............: Thu, Dec 17, 1998
Expires on..............: Fri, Dec 16, 2011
Record last updated on..: Fri, Nov 12, 2004
So, some sort of register.com snafu?
* Christopher L. Morrow:
i don't think so, the united.com domain was those two earlier today, with
www.united.com NS from dns01/02.uls-prod.com ... though I've seen this
situation change some throughout the day as well with the dcXlbs1 boxes in
the mix as well. Asking direcly from dns01/02 gets you records for SOME
things but not others and servfail 'often' for www.united.com.
The COM zone list the dc?lbs1.uls-prod.com servers as authoritative,
while the UNITED.COM zone contains NS records for dns0?.uls-prod.com.
Maybe this contributes to the confusion.
As far as I can tell, neither the NS records nor the A records have
recently changed.