Hi, I setup pfSense and added all the port forwards from my router, into pfSense, but my website still won't show?
I have tried: Linux > Terminal > $ ping www.domain.com > unknown host www.domain.com. I accessed Proxmox via Mint > Chrome > 192.168.1.160 > Webserver is running. I accessed Webmin VirtualServer via Mint > Chrome > https://192.168.1.163:10000 > Username: root > Password: xxx > Enter > System Information, all services are up. I accessed Webmin via Mint > Terminal >
$ ssh email@example.com. [root@centos ~]# dig www.domain.com ; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.17.rc1.el6_4.6 <<>> www.domain.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 58817 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;www.domain.com. IN A ;; Query time: 3 msec ;; SERVER: 192.168.1.180#53(192.168.1.180) ;; WHEN: Thu Feb 6 16:53:56 2014 ;; MSG SIZE rcvd: 37
Parent Info Domain NS records Nameserver records returned by the parent servers are: ns2.domain.com. ['WANIP'] [TTL=14400] ns1.domain.com. ['WANIP'] [TTL=14400] w.au was kind enough to give us that information. Warn TLD Parent Check WARNING: Looks like the parent servers do not have information for your TLD when asked. This is ok but can be confusing. Pass Your nameservers are listed Good. The parent server w.au has your nameservers listed. This is a must if you want to be found as anyone that does not know your DNS servers will first ask the parent nameservers. Pass DNS Parent sent Glue Good. The parent nameserver sent GLUE, meaning he sent your nameservers as well as the IPs of your nameservers. Glue records are A records that are associated with NS records to provide "bootstrapping" information to the nameserver.(see RFC 1912 section 2.3) Pass Nameservers A records Good. Every nameserver listed has A records. This is a must if you want to be found. NS Info NS records from your nameservers NS records got from your nameservers listed at the parent NS are: Oups! I could not get any nameservers from your nameservers (the ones listed at the parent server). Please verify that they are not lame nameservers and are configured properly. Pass Recursive Queries Good. Your nameservers (the ones reported by the parent server) do not report that they allow recursive queries for anyone. Pass Same Glue Hmm,I do not consider this to be an error yet, since I did not detect any nameservers at your nameservers. Pass Glue for NS records OK. Your nameservers (the ones reported by the parent server) have no ideea who your nameservers are so this will be a pass since you already have a lot of errors! Error Mismatched NS records WARNING: One or more of your nameservers did not return any of your NS records. Error DNS servers responded ERROR: One or more of your nameservers did not respond: The ones that did not respond are: 18.104.22.168 Pass Name of nameservers are valid OK. The nameservers reported by the parent send out nothing as shown above. I can't check nothing so it's a green! Error Multiple Nameservers ERROR: Looks like you have less than 2 nameservers. According to RFC2182 section 5 you must have at least 3 nameservers, and no more than 7. Having 2 nameservers is also ok by me. Pass Nameservers are lame OK. All the nameservers listed at the parent servers answer authoritatively for your domain. Pass Missing nameservers reported by parent OK. All NS records are the same at the parent and at your nameservers. Error Missing nameservers reported by your nameservers You should already know that your NS records at your nameservers are missing, so here it is again: ns2.domain.com. ns1.domain.com. Pass Domain CNAMEs OK. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present. Pass NSs CNAME check OK. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present. Pass Different subnets OK. Looks like you have nameservers on different subnets! Pass IPs of nameservers are public Ok. Looks like the IP addresses of your nameservers are public. This is a good thing because it will prevent DNS delays and other problems like Pass DNS servers allow TCP connection OK. Seems all your DNS servers allow TCP connections. This is a good thing and useful even if UDP connections are used by default. Pass Different autonomous systems OK. It seems you are safe from a single point of failure. You must be careful about this and try to have nameservers on different locations as it can prevent a lot of problems if one nameserver goes down. Pass Stealth NS records sent Ok. No stealth ns records are sent SOA Error SOA record No valid SOA record came back! MX Error MX Records Oh well, I did not detect any MX records so you probably don't have any and if you know you should have then they may be missing at your nameservers! WWW Error WWW A Record ERROR: I could not get any A records for www.domain.com! (I only do a cache request, if you recently added a WWW A record, it might not show up here.)
I went back into Webmin > Servers > BIND DNS Server > Existing DNS Zones > Zone: domain.com > Edit Master Zone > Type: All > Type: NS says domain.com. I think name server should be ns1.domain.com and ns2.domain.com.
I backed up current webmin files in Virtualmin > Backup and Restore > Scheduled Backups > Add a new backup schedule > Virtual servers > Servers to save: All virtual servers > Destination and format > Backup destinations: Local file or directory > Browse... > tmp > Backup (make folder if not there in tmp mkdir backup) > Ok > Create Schedule > Actions: Backup.. > Backup Now.
I tried restore but backups are of whole Virtualmin server from Proxmox. Had to restore whole webserver on Proxmox.
I haven't changed or deleted any nameservers, so I don't know if this is the true error or not, as pfSense install could probably not effect the name servers?