Pages

Monday, April 1, 2013

Error github: github.com [0: 207.97.227.239]: errno = Connection timed out fatal: unable to connect a socket (Connection timed out)

Error github: github.com [0: 207.97.227.239]: errno = Connection timed out fatal: unable to connect a socket (Connection timed out)

 

git clone -b 6.1.1 git://github.com/wgm/cerb6.git
And got this result:
Cloning into 'cerb6'...
fatal: unable to connect to github.com:
github.com[0: 207.97.227.239]: errno=Connection timed out

 

This error just happens because you have blocked port 9418 on the proxy just enable it and runs smoothly gitbub

 

installing git for single user

cd ~
wget http://git-core.googlecode.com/files/git-1.7.10.1.tar.gz
tar zxvf git-1.7.10.1.tar.gz
cd git-1.7.10.1
./configure --prefix=/home/$USER
make
make install
echo 'PATH=$PATH:$HOME/bin' >> $HOME/.bashrc
source $HOME/.bashrc

named-checkzone and named-checkconf command syntax

named-checkzone {zonename} {filename}
Where,

  • zonename : The domain name of the zone being checked.

  • filename : The name of the zone file.


How do I check my zone file configuration for errors?


Use named-checkzone to check the zone files as follows:
named-checkzone nixcraft.com /var/named/zone.nixcraft.com
Output:
OK

If you see "OK" as result, the zone file is properly configured and you can restart bind name server.

 

How do I check my bind configuration for errors?


Simply run command as follows:
# named-checkconf /etc/named.conf
You may want to chroot to directory so that include directives in the configuration file are processed as if run by a similarly chrooted named:
# named-checkconf -t /var/named/chroot /etc/named.conf
If there is no output, the configuration is considered correct and you can safely restart or reload bind configuration file. If there is an error it will be displayed on screen:
# named-checkconf /etc/named.conf