My IP is blocked but I can access it via ftp or ssh

erisone

Verified User
Joined
Mar 10, 2010
Messages
8
Hello,

I have some issues with my dedicated server and DA.
My website works fine for everybody except me (from my PC).
I can access it via http://IP but not via www.domain.com
I can log into ssh via domain name and password, I can
log into ftp via domain and password but via http://domain.com
it gives me the error Server not found.
I can access it via internet proxy server.
I checked the /usr/local/directadmin/data/admin/ip_blacklist
and it's empty.
Any ideas?

Thank You!
 
It worked perfectly for years untill a few days ago. Should I re-check the DA settings, maybe update them? Or the problem it may be with my ISP?

Thank You!
 
@floyd - other websites work perfectly, only the websites hosted on my dedicated server are not working...
 
But everybody else can get to your site so that means the problem is with you.

Have you tried using a different computer, different isp with the same computer?
 
There is no problem with other computers accessing my website, only mine.
Other ISP are working. I install now ubuntu to see what happens...
 
well you should tell us the domain so we should check dns settings aswell but probably it depend from your own computer or your dns settings OR windows hosts file (maybe a spyware or a wrong setting)
 
The nameservers are with Godaddy, this is what they told me:

It appears that your domains are being routed correctly to your name servers you have set up in the Domain Manager, however, once it's reaching your name servers, they are not returning any DNS information. Please contact your hosting provider to determine why the zone files on the name servers are not resolving correctly.

Please let us know if we can assist you in any other way.

Sincerely,...​
Seems that the problem is with DA, not my PC or something else.
Any solutions?

Thank You!
 
Domain name: myposton.com
Nameservers: neo1.subtire.net, neo2.subtire.net

/etc/bind/named.conf

// This is the primary configuration file for the BIND DNS server named.
//
// Please read /usr/share/doc/bind9/README.Debian.gz for information on the
// structure of BIND configuration files in Debian, *BEFORE* you customize
// this configuration file.
//
// If you are just adding zones, please do that in /etc/bind/named.conf.local

include "/etc/bind/named.conf.options";

// prime the server with knowledge of the root servers
zone "." {
type hint;
file "/etc/bind/db.root";
};

// be authoritative for the localhost forward and reverse zones, and for
// broadcast zones as per RFC 1912

zone "localhost" {
type master;
file "/etc/bind/db.local";
};

zone "127.in-addr.arpa" {
type master;
file "/etc/bind/db.127";
};

zone "0.in-addr.arpa" {
type master;
file "/etc/bind/db.0";
};

zone "255.in-addr.arpa" {
type master;
file "/etc/bind/db.255";
};

// zone "com" { type delegation-only; };
// zone "net" { type delegation-only; };

// zone "com" { type delegation-only; };
// zone "net" { type delegation-only; };

// From the release notes:
// Because many of our users are uncomfortable receiving undelegated answers
// from root or top level domains, other than a few for whom that behaviour
// has been trusted and expected for quite some length of time, we have now
// introduced the "root-delegations-only" feature which applies delegation-only
// logic to all top level domains, and to the root domain. An exception list
// should be specified, including "MUSEUM" and "DE", and any other top level
// domains from whom undelegated responses are expected and trusted.
// root-delegation-only exclude { "DE"; "MUSEUM"; };

include "/etc/bind/named.conf.local";
zone "USR001.local" { type master; file "/etc/bind/USR001.local.db"; };
zone "kestia.com" { type master; file "/etc/bind/kestia.com.db"; };
zone "subtire.net" { type master; file "/etc/bind/subtire.net.db"; };
zone "ampuso.com" { type master; file "/etc/bind/ampuso.com.db"; };
zone "subtire.com" { type master; file "/etc/bind/subtire.com.db"; };
zone "cazaneledunarii.com" { type master; file "/etc/bind/cazaneledunarii.com.db"; };
zone "subtire.me" { type master; file "/etc/bind/subtire.me.db"; };
zone "e43.me" { type master; file "/etc/bind/e43.me.db"; };
zone "telmob.me" { type master; file "/etc/bind/telmob.me.db"; };
zone "myposton.com" { type master; file "/etc/bind/myposton.com.db"; };

Is this enough?
 
cat /etc/bind/subtire.net.db

seems that neo1 and neo2 A record are not created on the domain subtire.net

reported by your nameservers You should already know that your NS records at your nameservers are missing, so here it is again:

neo1.subtire.net.
neo2.subtire.net.


Create an A record for each neo

neo1 A IP
neo2 A IP

Should solve your problem
 
/etc/bind/myposton.com.db

$TTL 14400
@ IN SOA neo1.subtire.net. hostmaster.myposton.com. (
2009121900
14400
3600
1209600
86400 )

myposton.com. 14400 IN NS neo1.subtire.net.
myposton.com. 14400 IN NS neo2.subtire.net.

ftp 14400 IN A 94.75.205.153
localhost 14400 IN A 127.0.0.1
mail 14400 IN A 94.75.205.153
myposton.com. 14400 IN A 94.75.205.153
pop 14400 IN A 94.75.205.153
smtp 14400 IN A 94.75.205.153
www 14400 IN A 94.75.205.153

myposton.com. 14400 IN MX 10 mail



myposton.com. 14400 IN TXT "v=spf1 a mx ip4:94.75.205.153 ~all"
 
Adding a neo1 A IP
neo2 A IP worked, now they are working all but there is another problem.
Seems that all my domains point now to a blank page.
http://myposton.com like apache structure.
I think that that is my root server.
I think that the problem may be that I changed some Reverse ip


This was - > http://i.imgur.com/YaXIg.png
I changed them to neo1.subtire.net and neo2.subtire.net
And I think that that may be the problem, should I wait a
while to see if that's the problem or should I try something else?
Maybe my virtual hosts are messed up now?

Thank You!
 
I could use the nameservers listed below to performe recursive queries. It may be that I am wrong but the chances of that are low. You should not have nameservers that allow recursive queries as this will allow almost anyone to use your nameservers and can cause problems. Problem record(s) are:
94.75.205.153
94.75.205.172

seems that in your domain registration you have set 2 different ip for neo1 and neo2 and in your dns settings of domain subtire.net you had set same ip for both records neo1 and neo2 resolve 94.75.205.153

You should check that first, by the way, if you have no wrong setup in your server for virtual host you should see website soon when dns are propagated, i just suggest you to solve neo2 IP to poin to 94.75.205.172 so everything gonna be perfect
 
Back
Top