{"id":29,"date":"2004-10-29T04:55:17","date_gmt":"2004-10-29T04:55:17","guid":{"rendered":"http:\/\/lachy.id.au\/log\/2004\/10\/dns-issues"},"modified":"2006-04-30T23:52:06","modified_gmt":"2006-04-30T23:52:06","slug":"dns-issues","status":"publish","type":"post","link":"https:\/\/lachy.id.au\/log\/2004\/10\/dns-issues","title":{"rendered":"DNS Issues"},"content":{"rendered":"

Over the past 14 hours, since about 2004-10-29T00:00+10:00, this site was experiencing severe technical difficulties. Some of you may have noticed that the Atom feeds were reported as invalid by your feed reader, or received a 307 Temporary Redirect<\/code> to a page explaining some technical difficulties; or, depending on when you visited, noticed that none of the pages were styled and contained errors about include directives. If any of you that took a look at the source, you would have noticed a disastrous frameset document<\/a> I discussed earlier, that is used forward<\/em><\/q> requests. However, all it does is use a single frame to mask the real URI<\/abbr> from the location bar.<\/p>\r\n\r\n

The problem was in fact that the domain name servers had been reset to those of my previous domain registrar, and hence was reaching the wrong web host A WHOIS<\/a> indicated that the name servers were set to:<\/p>\r\n\r\n

Name Server: ns3.bottledomains.net.au \r\nName Server IP: 209.126.193.12 \r\nName Server: ns4.bottledomains.net.au \r\nName Server IP: 69.10.134.206<\/pre>\r\n\r\n
After I contacted my current host, iiNet<\/a>, this morning, within a few hours they promptly re-delegated the name servers to the correct ones, and restored my site for full working order.  However, it\u2019s an issue that should never have occurred.  I was asked by iiNet to contact Bottle Domains<\/a> to ensure this doesn\u2019t happen again, as they believed it must have been them that reclaimed the servers.  However the response from Bottle Domains indicated that it would not have been them as they do not control the domain.  So, basically, I don\u2019t have a clue what caused it, nor any guarantee that it won\u2019t happen again.  I just hope it doesn\u2019t.<\/p>\r\n","protected":false},"excerpt":{"rendered":"Over the past 14 hours, since about 2004-10-29T00:00+10:00, this site was experiencing severe technical difficulties. Some of you may have noticed that the Atom feeds were reported as invalid by your feed reader, or received a 307 Temporary Redirect to a page explaining some technical difficulties; or, depending on when you visited, noticed that none … Continue reading DNS Issues<\/span> →<\/span><\/a>","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[8],"tags":[],"_links":{"self":[{"href":"https:\/\/lachy.id.au\/log\/wp-json\/wp\/v2\/posts\/29"}],"collection":[{"href":"https:\/\/lachy.id.au\/log\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/lachy.id.au\/log\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/lachy.id.au\/log\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/lachy.id.au\/log\/wp-json\/wp\/v2\/comments?post=29"}],"version-history":[{"count":0,"href":"https:\/\/lachy.id.au\/log\/wp-json\/wp\/v2\/posts\/29\/revisions"}],"wp:attachment":[{"href":"https:\/\/lachy.id.au\/log\/wp-json\/wp\/v2\/media?parent=29"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/lachy.id.au\/log\/wp-json\/wp\/v2\/categories?post=29"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/lachy.id.au\/log\/wp-json\/wp\/v2\/tags?post=29"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}