-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
- --On Thursday, November 16, 2006 12:26:04 +0100 Magnus Hagander
<mha@sollentuna.net> wrote:
>
>> I just restarted the name server(s), and same result ... I've
>> even disabled the change I made the other day to 'disable
>> recursive', restarted, same result ...
>> so it isn't related to any change I've made recently :(
>>
>> Anyone out there with more knowledge of DNS then I have any ideas?
>
> whois says the domain expired very recently, and was updated Nov 17th.
> My guess would be something expired before it was renewed and was
> dropped from the zones for a while. Now you're probably just waiting for
> the cache to clear...
Where did you find that out? According to whois here:
Domain Name: VARLENA.COM
Created on: 14-Nov-2002
Expires on: 12-Nov-2014
Last Updated on: 17-Nov-2005
It was last updated Nov 17th *2005* ... a year ago ... neat thing is, shouldn't
I be able to resolve from her name servers:
postgresql# nslookup varlena.com JASMINE.NORCOV.COM
;; connection timed out; no servers could be reached
postgresql# nslookup varlena.com KOLIBRI.NORCOV.COM
;; connection timed out; no servers could be reached
postgresql# nslookup varlena.com ns.uunet.ca
Server: ns.uunet.ca
Address: 142.77.1.1#53
Non-authoritative answer:
Name: varlena.com
Address: 64.81.253.188
- ----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email . scrappy@hub.org MSN . scrappy@hub.org
Yahoo . yscrappy Skype: hub.org ICQ . 7615664
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (FreeBSD)
iD8DBQFFXE0U4QvfyHIvDvMRAkrIAKDtSZ3vEF+tme1b5IP+oqCcqEvjTQCgonlq
Bh/bUrw7kMJ4sbpBmE7iWR8=
=aY1M
-----END PGP SIGNATURE-----