The problem is that the MIAB box itself cannot resolve its own A section address. My conclusion is that for some reason the DNS that’s running on the localhost has the wrong AUTHORITY SECTION reply. Here’s what I get for my box’ own domain name:
root@mailbox:/etc# dig mailbox.kypelihosting.com
; <<>> DiG 9.9.5-3ubuntu0.9-Ubuntu <<>> mailbox.kypelihosting.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 6803
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;mailbox.kypelihosting.com. IN A
;; AUTHORITY SECTION:
kypelihosting.com. 1179 IN SOA ns1.digitalocean.com. hostmaster.kypelihosting.com. 1435002584 10800 3600 604800 1800
AFAIK this means that the request if forwarded to ns1.digitalocean.com that is not going to handle the request. Thus, when resolving the host, it won’t work:
root@mailbox:/etc# host mailbox.kypelihosting.com
Host mailbox.kypelihosting.com not found: 3(NXDOMAIN)
Here’s the dig output for a domain that is hosted on the MIAB:
root@mailbox:/etc# dig kypeli.com
; <<>> DiG 9.9.5-3ubuntu0.9-Ubuntu <<>> kypeli.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 1518
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;kypeli.com. IN A
I would assume the replies on these both should be the same. But I can’t figure out what’s wrong and where.
From the outside world, everything is working and the A record is resolved just fine => email is working and so on. But I have to renew my SSL certificates and that’s not going to work if the box cannot resolve its own domain name, so I would like to get this fixed.
Any help? Thanks!