216.127.66.122 - RIP
Feb. 13th, 2006 03:18 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
robinbobinСтарый сервер все.
кто не перепрятался я не виноват.
есть бекап на сегодняшнее утро.
телефон я забыл дома.
шлите письма на robinbobin @ inbox.ru
кто не перепрятался я не виноват.
есть бекап на сегодняшнее утро.
телефон я забыл дома.
шлите письма на robinbobin @ inbox.ru
![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png){kind=small}
no subject
Date: 2006-02-13 04:52 pm (UTC)no subject
Date: 2006-02-13 06:07 pm (UTC)no subject
Date: 2006-02-14 02:46 am (UTC)no subject
Date: 2006-02-14 06:30 am (UTC)no subject
Date: 2006-02-14 07:58 am (UTC)no subject
Date: 2006-02-14 09:13 am (UTC)no subject
Date: 2006-02-14 09:13 am (UTC)no subject
Date: 2006-02-14 09:32 am (UTC)rock-club.org resolves to 216.127.66.122
IP Address 216.127.66.122 is located in
Domain Whois Results:
no subject
Date: 2006-02-14 10:06 am (UTC)no subject
Date: 2006-02-14 10:07 am (UTC)no subject
Date: 2006-02-14 10:36 am (UTC)no subject
Date: 2006-02-14 10:33 am (UTC)rock-club.org
This domain does not have the proper name servers to participate in free hosting services.
ns1.7pik.info
ns2.7pik.info
In order to take advantage of directNIC's free hosting services, your domain must be associated with directNIC.com's name servers. To enable these name servers click on the "Modify Name Servers" link below and select use directNIC defaults.
---------------
ERROR: You have one or more lame nameservers. These are nameservers that do NOT answer authoritatively for your domain. This is bad; for example, these nameservers may never get updated. The following nameservers are lame:
193.218.105.149
199.203.56.42
------------------
ERROR: One or more of the nameservers listed at the parent servers are not listed as NS records at your nameservers. The problem NS records are:
ns2.7pik.info.
ns1.7pik.info.
-------------------
WARNING: At least one of your nameservers did not return your NS records (it reported 0 answers). This could be because of a referral, if you have a lame nameserver (which would need to be fixed).
193.218.105.149 returns 0 answers (may be a referral)
199.203.56.42 returns 0 answers (may be a referral)
------------------------
Your DNS servers leak stealth information in non-NS requests:
Stealth nameservers are leaked [tld3.ultradns.org.]!
Stealth nameservers are leaked [tld4.ultradns.org.]!
Stealth nameservers are leaked [tld5.ultradns.info.]!
Stealth nameservers are leaked [tld6.ultradns.co.uk.]!
Stealth nameservers are leaked [tld1.ultradns.net.]!
Stealth nameservers are leaked [tld2.ultradns.net.]!
This can cause some serious problems (especially if there is a TTL discrepancy). If you must have stealth NS records (NS records listed at the authoritative DNS servers, but not the parent DNS servers), you should make sure that your DNS server does not leak the stealth NS records in response to other queries.
---------------------------
no subject
Date: 2006-02-14 10:37 am (UTC)199.203.56.42
Этот по-моему вообще не пашет
no subject
Date: 2006-02-14 10:38 am (UTC)no subject
Date: 2006-02-14 11:21 am (UTC)193.218.105.149
Одним ламерским сервером стало меньше:) Прогресс;)
no subject
Date: 2006-02-14 12:42 pm (UTC)shas bazu budu kidat