Missing domain mystery...
David M. Lloyd
registered with us. It was working great 2 days ago; then it suddeny
ceased. If you do an nslookup for the domain on any nameserver
anywhere,
it is not found. However, it shows up under our server, and it also
shows up under whois; it appears to still be registered.
My slaves pick it up okay, but I am starting the serial numbers over
just in case...
Am I missing something obvious?
--
===========================================================
David M. Lloyd mailto:da...@inxpress.net
Administrator
Internet Express, Inc.
802 W. Broadway, Suite 0101
Madison, WI. 53713-1866
Voice: (608) 663-5555 http://www.inxpress.net
Fax: (608) 663-5595 mailto:ad...@inxpress.net
Data: (608) 663-5551 mailto:sup...@inxpress.net
===========================================================
Barry Margolin
David M. Lloyd <da...@inxpress.net> wrote:
>This one has me totally stumped... we have a customer who has a domain
>registered with us. It was working great 2 days ago; then it suddeny
>ceased. If you do an nslookup for the domain on any nameserver
>anywhere,
>it is not found. However, it shows up under our server, and it also
>shows up under whois; it appears to still be registered.
>
>My slaves pick it up okay, but I am starting the serial numbers over
>just in case...
It's probably on hold due to non-payment of the NSI bill. Check
<https://payments.networksolutions.com>.
A number of our customers have had their domains go on hold this week. I
think NSI just did a pass through all their overdue accounts and put them
on hold. Either that, or they had a database SNAFU and marked lots of
domains as being overdue when they weren't.
--
Barry Margolin, bar...@bbnplanet.com
GTE Internetworking, Powered by BBN, Burlington, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.
Joseph S D Yao
Check the syslogs for indications that the 'named' found an error and
rejected the domain.
Check whether the immediate parent domains [the root servers?] for some
reason glitched and lost your domain.
--
Joe Yao js...@cospo.osis.gov - Joseph S. D. Yao
COSPO/OSIS Computer Support EMT-B
-----------------------------------------------------------------------
This message is not an official statement of COSPO policies.
David Lloyd
>> Am I missing something obvious?
>
>Check the syslogs for indications that the 'named' found an error and
>rejected the domain.
>
>Check whether the immediate parent domains [the root servers?] for some
>reason glitched and lost your domain.
Okay, looks like it was a simple problem after all... Apparently the
customer didn't pay their InterNIC bill and they put it on hold.. That's
difficult since there is no way (apparently) to *tell* whether a domain is
on hold thru InterNIC.
Michael Faurot
: Okay, looks like it was a simple problem after all... Apparently the
: customer didn't pay their InterNIC bill and they put it on hold.. That's
: difficult since there is no way (apparently) to *tell* whether a domain is
: on hold thru InterNIC.
In the past, I've been able to determine this by simply doing a
"whois" on the domain. If there was a problem, the whois data would
show the domain "on hold" (or something similar).
--
------------------------------------------------------------------------------
Michael | mfaurot | Green light in A.M. for new projects. Red light in
Faurot | atww.org | P.M. for traffic tickets.
Tani Hosokawa
> David Lloyd <da...@inxpress.net> wrote:
> : Okay, looks like it was a simple problem after all... Apparently the
> : customer didn't pay their InterNIC bill and they put it on hold.. That's
> : difficult since there is no way (apparently) to *tell* whether a domain is
> : on hold thru InterNIC.
>
> In the past, I've been able to determine this by simply doing a
> "whois" on the domain. If there was a problem, the whois data would
> show the domain "on hold" (or something similar).
They no longer do that. This is because the InterNIC is completely
useless. Anyone tried registering a domain in the past few months?
---
tani hosokawa
river styx internet
Barry Margolin
>David Lloyd <da...@inxpress.net> wrote:
>: Okay, looks like it was a simple problem after all... Apparently the
>: customer didn't pay their InterNIC bill and they put it on hold.. That's
>: difficult since there is no way (apparently) to *tell* whether a domain is
>: on hold thru InterNIC.
>
>In the past, I've been able to determine this by simply doing a
>"whois" on the domain. If there was a problem, the whois data would
>show the domain "on hold" (or something similar).
They got rid of this in WHOIS, since domain speculators were abusing it.
You can now go to <https://payments.networksolutions.com> and enter the
domain, and you'll see whether its payments are up to date.
Doug
> On Thu, 1 Jul 1999, Joseph S D Yao wrote:
>
> >> Am I missing something obvious?
> >
> >Check the syslogs for indications that the 'named' found an error and
> >rejected the domain.
> >
> >Check whether the immediate parent domains [the root servers?] for some
> >reason glitched and lost your domain.
>
> Okay, looks like it was a simple problem after all... Apparently the
> customer didn't pay their InterNIC bill and they put it on hold.. That's
> difficult since there is no way (apparently) to *tell* whether a domain is
> on hold thru InterNIC.
Checking the roots for delegation is usually a good hint. whois
records + no root delegation usually == overdue bill. This is useful for
the many times that netsol's accounting page isn't working. :)
Good luck,
Doug
--
On account of being a democracy and run by the people, we are the only
nation in the world that has to keep a government four years, no matter
what it does.
-- Will Rogers
Jay Koski
On Fri, 2 Jul 1999, Barry Margolin wrote:
> In article <7lj17q$ugk$1...@phzzzt.atww.org>, Michael Faurot <lo...@my.sig> wrote:
> >David Lloyd <da...@inxpress.net> wrote:
> >: Okay, looks like it was a simple problem after all... Apparently the
> >: customer didn't pay their InterNIC bill and they put it on hold.. That's
> >: difficult since there is no way (apparently) to *tell* whether a domain is
> >: on hold thru InterNIC.
> >
> >In the past, I've been able to determine this by simply doing a
> >"whois" on the domain. If there was a problem, the whois data would
> >show the domain "on hold" (or something similar).
>
> They got rid of this in WHOIS, since domain speculators were abusing it.
>
> You can now go to <https://payments.networksolutions.com> and enter the
> domain, and you'll see whether its payments are up to date.
>
> --
> Barry Margolin, bar...@bbnplanet.com
> GTE Internetworking, Powered by BBN, Burlington, MA
> *** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
> Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.
>
>
You can also do this:
dig <domainname>
Check for:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6
When a domain has been placed on hold, status seems to change to
NXDOMAIN. This is how I check for domains that have been frozen. I don't
know how accurate this is, but afaik, it works.
Doug
> On Thu, 1 Jul 1999, Joseph S D Yao wrote:
>
> >> Am I missing something obvious?
> >
> >Check the syslogs for indications that the 'named' found an error and
> >rejected the domain.
> >
> >Check whether the immediate parent domains [the root servers?] for some
> >reason glitched and lost your domain.
>
> Okay, looks like it was a simple problem after all... Apparently the
> customer didn't pay their InterNIC bill and they put it on hold.. That's
> difficult since there is no way (apparently) to *tell* whether a domain is
> on hold thru InterNIC.
Checking the roots for delegation is usually a good hint. whois
Cricket Liu
news:<Pine.BSF.4.10.990702...@quiveringmeatwheel.desolation
row.com>...
> You can also do this:
>
> dig <domainname>
>
> Check for:
>
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6
>
> When a domain has been placed on hold, status seems to change to
> NXDOMAIN. This is how I check for domains that have been frozen. I don't
> know how accurate this is, but afaik, it works.
NXDOMAIN just means "no such domain name," so you'd also get that error if
the domain name had never existed.
cricket
Acme Byte & Wire
cri...@acmebw.com
www.acmebw.com
Attend our next DNS and BIND class! See
www.acmebw.com/training.htm for the
schedule and to register for upcoming
classes.
Lawrence Chan
Tani Hosokawa wrote:
> On 2 Jul 1999, Michael Faurot wrote:
>
> > David Lloyd <da...@inxpress.net> wrote:
> > : Okay, looks like it was a simple problem after all... Apparently the
> > : customer didn't pay their InterNIC bill and they put it on hold.. That's
> > : difficult since there is no way (apparently) to *tell* whether a domain is
> > : on hold thru InterNIC.
> >
> > In the past, I've been able to determine this by simply doing a
> > "whois" on the domain. If there was a problem, the whois data would
> > show the domain "on hold" (or something similar).
>
> They no longer do that. This is because the InterNIC is completely
> useless. Anyone tried registering a domain in the past few months?
>
> ---
> tani hosokawa
> river styx internet
If you think trying to register a new domain is hard, try something else that
requires services but do not involve any payment from you, like telling them that
certain domains no longer exist or deleting contacts.
Why is the single most important nexus of the whole naming system in the Net could
have so much servicing problems? And you have to pay for all your "troubles"!
Lawrence Chan
lc...@montevino.com
R David Decker
news:<Pine.BSF.4.10.990702...@quiveringmeatwheel.desolation
row.com>...
> You can also do this:
>
> dig <domainname>
>
> Check for:
>
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6
>
> When a domain has been placed on hold, status seems to change to
> NXDOMAIN. This is how I check for domains that have been frozen. I don't
> know how accurate this is, but afaik, it works.
thanks for the tip...
If whois <domainname> shows the domain exists then do
dig @a.root-servers.net <domainname>
If status: NXDOMAIN then the domainname is on hold.. i.e. they need to
pay the registration fee..
If status: NOERROR then the domainname is ok