Ok so I 4 failover ips and i have my main website on the main ip and a secondary website on a failover ip dns records are working correctly but the secondary website wont load at all i dont know what i have configured wrong please help My ubuntu version is 18.04.2
Fix the punctuation keys on your keyboard first so you can write sentences. Are you sure DNS works correctly? This tutorial shows also how to test DNS is working. https://www.howtoforge.com/tutorial/setting-up-your-own-name-service-with-ispconfig/#nbsptesting If DNS does not work correctly, you can test the website with this method: https://www.faqforge.com/linux/cont...ess-a-namebased-website-without-a-dns-record/ You wrote Can you provide more info? It would be strange if nothing happens. Does it load the other website instead, for example?
So i received this error. when i ran the dig command ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached Also my dns records are all on godaddy and the error i receive when trying to go to website is "the server took too long to respond
There is something wrong with your DNS setup or records. After querying enough times, I sometimes do get an answer: Code: $ dig bruceskc.com ; <<>> DiG 9.10.3-P4-Debian <<>> bruceskc.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4484 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;bruceskc.com. IN A ;; ANSWER SECTION: bruceskc.com. 600 IN A 192.99.174.239 ;; Query time: 89 msec ;; SERVER: 192.168.8.1#53(192.168.8.1) ;; WHEN: Sat Apr 06 12:33:43 EEST 2019 ;; MSG SIZE rcvd: 57 taleman@yosemitesam:~ $ dig bruceskc.com ;; Got bad packet: FORMERR 57 bytes f4 2a 81 20 00 01 00 01 00 00 00 01 08 62 72 75 .*...........bru 63 65 73 6b 63 03 63 6f 6d 00 00 01 00 01 c0 0c ceskc.com....... 00 01 00 01 00 00 02 58 00 04 c0 63 ae ef 00 00 .......X...c.... 00 00 00 00 00 00 00 00 00 ......... taleman@yosemitesam:~ $ Check that both your registered name servers have identical data. Code: $ whois bruceskc.com | grep "Name Server:" Name Server: NS67.DOMAINCONTROL.COM Name Server: NS68.DOMAINCONTROL.COM Name Server: NS67.DOMAINCONTROL.COM Name Server: NS68.DOMAINCONTROL.COM taleman@yosemitesam:~ $ Code: $ dig @NS68.DOMAINCONTROL.COM bruceskc.com ANY ;; Truncated, retrying in TCP mode. ; <<>> DiG 9.10.3-P4-Debian <<>> @NS68.DOMAINCONTROL.COM bruceskc.com ANY ; (2 servers found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 54878 ;; flags: qr aa rd; QUERY: 1, ANSWER: 6, AUTHORITY: 0, ADDITIONAL: 1 ;; WARNING: recursion requested but not available ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;bruceskc.com. IN ANY ;; ANSWER SECTION: bruceskc.com. 600 IN A 192.99.174.239 bruceskc.com. 3600 IN NS ns67.domaincontrol.com. bruceskc.com. 3600 IN NS ns68.domaincontrol.com. bruceskc.com. 600 IN SOA ns67.domaincontrol.com. dns.jomax.net. 2019040302 28800 7200 604800 600 bruceskc.com. 3600 IN TXT "google-site-verification=snlSb3Mhv_Yi_mJMwEt5sRO5OURblrpB-bb7jAnpCtc" bruceskc.com. 3600 IN TXT "v=spf1 mx a ip4:158.69.248.37 ~all" ;; Query time: 51 msec ;; SERVER: 173.201.71.44#53(173.201.71.44) ;; WHEN: Sat Apr 06 12:36:29 EEST 2019 ;; MSG SIZE rcvd: 286 taleman@yosemitesam:~ Things to check: all records are correctly formatted and do not contain any extra whitespace or control characters both your name servers answer the same way to all queries both your name servers actually work all the time. It looks after my testing that they sometimes do not answer. Code: $ dig @NS67.DOMAINCONTROL.COM bruceskc.com ANY dig: couldn't get address for 'NS67.DOMAINCONTROL.COM': failure taleman@yosemitesam:~ the name servers for domain domaincontrol.com actually all work all the time.
If you read the Tutorial https://www.howtoforge.com/tutorial...service-with-ispconfig/#nbspusing-ispconfig-x you learn to end the FQDN names in ISPConfig DNS entries with a dot character ".". Try adding that. I'm not sure what @ means on those fields, I would use the FQDN instead.
