vBulletin 4, the most powerful community software + vBSEO 3.5, the ultimate SEO solution = Your ultimate platform for 2010 and beyond. Click below to learn more.
This is a discussion on vBSEO Web Hosting Survey - Demand Blazing Speed! within the vBSEO Announcements forums, part of the Announcements & Pre-Sales category; Originally Posted by pspmodandcfw I log into vbseo every day and it always works. Your location says your in Ireland, ...
I'm on here, well, constantly,and haven't had any issues either.
next time you see it happen, run a tracert to vbseo.com and see what happens.
or, you can add an entry to your host file for
vbseo.com 75.126.140.207
www.vbseo.com 75.126.140.207
which will bypass dns altogether.
I've already run diagnostics on it.
The problem lies with the dns:
dig +trace vbseo.com
; <<>> DiG 9.5.0-P2 <<>> +trace vbseo.com
;; global options: printcmd
. 90707 IN NS E.ROOT-SERVERS.NET.
. 90707 IN NS F.ROOT-SERVERS.NET.
. 90707 IN NS G.ROOT-SERVERS.NET.
. 90707 IN NS H.ROOT-SERVERS.NET.
. 90707 IN NS I.ROOT-SERVERS.NET.
. 90707 IN NS J.ROOT-SERVERS.NET.
. 90707 IN NS K.ROOT-SERVERS.NET.
. 90707 IN NS L.ROOT-SERVERS.NET.
. 90707 IN NS M.ROOT-SERVERS.NET.
. 90707 IN NS A.ROOT-SERVERS.NET.
. 90707 IN NS B.ROOT-SERVERS.NET.
. 90707 IN NS C.ROOT-SERVERS.NET.
. 90707 IN NS D.ROOT-SERVERS.NET.
;; Received 500 bytes from 192.168.1.1#53(192.168.1.1) in 53 ms
com. 172800 IN NS a.gtld-servers.net.
com. 172800 IN NS b.gtld-servers.net.
com. 172800 IN NS c.gtld-servers.net.
com. 172800 IN NS d.gtld-servers.net.
com. 172800 IN NS e.gtld-servers.net.
com. 172800 IN NS f.gtld-servers.net.
com. 172800 IN NS g.gtld-servers.net.
com. 172800 IN NS h.gtld-servers.net.
com. 172800 IN NS i.gtld-servers.net.
com. 172800 IN NS j.gtld-servers.net.
com. 172800 IN NS k.gtld-servers.net.
com. 172800 IN NS l.gtld-servers.net.
com. 172800 IN NS m.gtld-servers.net.
;; Received 487 bytes from 128.63.2.53#53(H.ROOT-SERVERS.NET) in 150 ms
vbseo.com. 172800 IN NS ns1.crawlability.com.
vbseo.com. 172800 IN NS ns2.crawlability.com.
;; Received 108 bytes from 192.5.6.30#53(a.gtld-servers.net) in 170 ms
dig: couldn't get address for 'ns1.crawlability.com': not found
That very last line is NOT normal.
So I ran it through a few more tools like this one:
DNSCheck which threw similar errors
And this test also throws loads of errors
Those are odd results, and it could be something on the DNS side entries where you reside, as out of where I am, the NE USA, the resolve works correctly:
ping ns1.crawlability.com
Pinging ns1.crawlability.com [75.126.140.204] with 32 bytes of data:
Reply from 75.126.140.204: bytes=32 time=54ms TTL=51
Reply from 75.126.140.204: bytes=32 time=54ms TTL=51
Reply from 75.126.140.204: bytes=32 time=52ms TTL=51
Reply from 75.126.140.204: bytes=32 time=53ms TTL=51
Ping statistics for 75.126.140.204:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 52ms, Maximum = 54ms, Average = 53ms
ping ns2.crawlability.com
Pinging ns2.crawlability.com [75.126.140.205] with 32 bytes of data:
Reply from 75.126.140.205: bytes=32 time=54ms TTL=51
Reply from 75.126.140.205: bytes=32 time=53ms TTL=51
Reply from 75.126.140.205: bytes=32 time=55ms TTL=51
Reply from 75.126.140.205: bytes=32 time=53ms TTL=51
Ping statistics for 75.126.140.205:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 53ms, Maximum = 55ms, Average = 53ms
ping vbseo.com
Pinging vbseo.com [75.126.140.207] with 32 bytes of data:
Reply from 75.126.140.207: bytes=32 time=52ms TTL=51
Reply from 75.126.140.207: bytes=32 time=54ms TTL=51
Reply from 75.126.140.207: bytes=32 time=53ms TTL=51
Reply from 75.126.140.207: bytes=32 time=61ms TTL=51
Ping statistics for 75.126.140.207:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 52ms, Maximum = 61ms, Average = 55ms
ns1.crawlability.com is DNS mapped to 75.126.140.204, based on the results I get.
The DNS check tools are not checking against our local (USA) DNS servers, obviously, as they are sourced to Sweden and France, respectively.
When the same checks are run from a US based DNS tool, all results come back as intact and correct.
DNS Quick Check - DNS Report Tool, Test your DNS delegation, DNS Servers, Mail and Web Servers, Network Admins, Webmasters, Hosting
It would appear to be some form of foreign addressing issue, as the entries exist.Code:Got DNS list for 'vbseo.com' from A.GTLD-SERVERS.NET
- Found NS record: ns1.crawlability.com[75.126.140.204], was resolved to IP address by A.GTLD-SERVERS.NET
- Found NS record: ns2.crawlability.com[75.126.140.205], was resolved to IP address by A.GTLD-SERVERS.NET
- Domain has 2 DNS server(s)
- CheckDNS.NET is verifying if NS are alive
- DNS server ns1.crawlability.com[75.126.140.204] is alive and authoritative for domain vbseo.com
- DNS server ns2.crawlability.com[75.126.140.205] is alive and authoritative for domain vbseo.com
- 2 server(s) are alive