webserer is not up
I just setup my first new Linode here. I follow all the instruction on
Once all that complete.. I still unable to see something here: linarno.matt28hosting.com
According to the support.. It looks like SSH is working properly but your webserver is not. That is what they said.
Any idea?
2 Replies
The host you mentioned has no entry:
$ dig linarno.matt28hosting.com
; <<>> DiG 9.7.3 <<>> linarno.matt28hosting.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 26858
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;linarno.matt28hosting.com. IN A
;; AUTHORITY SECTION:
matt28hosting.com. 10800 IN SOA ns1.matt28hosting.com. staff.matt28hosting.com. 2015071311 86400 7200 3600000 86400
;; Query time: 337 msec
;; SERVER: 216.126.207.9#53(216.126.207.9)
;; WHEN: Wed Jul 15 07:05:25 2015
;; MSG SIZE rcvd: 89
There are no obvious problems with matt28hosting.com itself, but I'll note that none of these IP addresses are Linode's:
dig -t ANY matt28hosting.com
; <<>> DiG 9.7.3 <<>> -t ANY matt28hosting.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 28066
;; flags: qr rd ra; QUERY: 1, ANSWER: 6, AUTHORITY: 2, ADDITIONAL: 2
;; QUESTION SECTION:
;matt28hosting.com. IN ANY
;; ANSWER SECTION:
matt28hosting.com. 14400 IN A 67.222.9.132
matt28hosting.com. 86400 IN SOA ns1.matt28hosting.com. staff.matt28hosting.com. 2015071311 86400 7200 3600000 86400
matt28hosting.com. 14400 IN MX 0 mail.matt28hosting.com.
matt28hosting.com. 14400 IN TXT "v=spf1 ip4:67.222.9.132 +a +mx +ip4:67.222.9.132 ~all"
matt28hosting.com. 86400 IN NS ns1.matt28hosting.com.
matt28hosting.com. 86400 IN NS ns2.matt28hosting.com.
;; AUTHORITY SECTION:
matt28hosting.com. 86400 IN NS ns1.matt28hosting.com.
matt28hosting.com. 86400 IN NS ns2.matt28hosting.com.
;; ADDITIONAL SECTION:
ns1.matt28hosting.com. 172738 IN A 67.222.9.132
ns2.matt28hosting.com. 172738 IN A 67.222.9.20
;; Query time: 526 msec
;; SERVER: 216.126.207.9#53(216.126.207.9)
;; WHEN: Wed Jul 15 07:06:27 2015
;; MSG SIZE rcvd: 276
Also, your MX host points to a CNAME entry, which is a violation of RFC 5321
$ dig mail.matt28hosting.com
; <<>> DiG 9.7.3 <<>> mail.matt28hosting.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 49275
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 2
;; QUESTION SECTION:
;mail.matt28hosting.com. IN A
;; ANSWER SECTION:
mail.matt28hosting.com. 14363 IN CNAME matt28hosting.com.
matt28hosting.com. 14289 IN A 67.222.9.132
;; AUTHORITY SECTION:
matt28hosting.com. 86289 IN NS ns2.matt28hosting.com.
matt28hosting.com. 86289 IN NS ns1.matt28hosting.com.
;; ADDITIONAL SECTION:
ns1.matt28hosting.com. 172627 IN A 67.222.9.132
ns2.matt28hosting.com. 172627 IN A 67.222.9.20
;; Query time: 769 msec
;; SERVER: 216.126.207.9#53(216.126.207.9)
;; WHEN: Wed Jul 15 07:08:18 2015
;; MSG SIZE rcvd: 138
@RFC 5321:
When a domain name associated with an MX RR is looked up and the associated data field obtained, the data field of that response MUST contain a domain name. That domain name, when queried, MUST return at least one address record (e.g., A or AAAA RR) that gives the IP address of the SMTP server to which the message should be directed. Any other response, specifically including a value that will return a CNAME record when queried, lies outside the scope of this Standard. The prohibition on labels in the data that resolve to CNAMEs is discussed in more detail in RFC 2181, Section 10.3 [38].