deprecated constructor

[snakes1100]

As the error page clearly states: ERR_NAME_NOT_RESOLVED

According to an ns dig, pakistanipoint.com doesnt have any ns servers assigned to the domains dns record.

As you can see below, there is no ANSWER SECTION

[root@forums rep-user]# dig pakistanipoint.com ns

; <<>> DiG 9.9.4-RedHat-9.9.4-51.el7_4.2 <<>> pakistanipoint.com ns
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 984
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;pakistanipoint.com.            IN      NS

;; AUTHORITY SECTION:
com.                    427     IN      SOA     a.gtld-servers.net. nstld.verisign-grs.com. 1525602285 1800 900 604800 86400

;; Query time: 0 msec
;; SERVER: 77.235.33.38#53(77.235.33.38)
;; WHEN: Sun May 06 12:32:59 CEST 2018
;; MSG SIZE  rcvd: 120

Nothing on your server would cause the site to not be reachable, unless you was running your own dns records & you somehow nuked the dns records on accident.

--------------- Added [DATE]1525603575[/DATE] at [TIME]1525603575[/TIME] ---------------

Looking into your domain a bit more, its appears you are using your own dns servers

ns1.pakistanipoint.com
ns2.pakistanipoint.com

Possible causes:
Missing DNS records on the NS severs
Incorrect IP's assigned to the NS servers @ the registrar
Borked named server

Its not suggestible to run your own dns from your server anyways, especially 2 of them on the same server, that totally defeats the purpose of ns2, as its hte backup incase ns1 goes down.