Kinda doubtful (DNS doesn't really do codes). DNS in a fairly dumbed down description points a domain name to an IP address - from the user perspective the only things that will usually cock up with that are someone cocking up the primary DNS (usually fixed quickly as that will break things attached to the domain), or having an upstream DNS server that ignores the refresh and TTL data for a zone resulting in any changes not going through (kinda rare these days, but does happen). DNS gets blamed for a whole lot of things it's innocent of; most people don't understand it, and they blame it because they saw "DNS Servers" listed in their network settings. Back in the late 1990s, DNS was referred to as a "black art".
Routing issues however - far more complex, and unless you really understand how the internet is joined together, it's going to be hard to convey to you exactly how many different places that routing issues can occur. Every major ISP will (should) have various interconnect points to different countries. Data will always try to take the shortest/fastest path to its destination, which it works out based on routing data. Any of that data gets screwed up; something that might happen at a CPE router, ISP router, their upstream provider, their upstream provider, maybe the various levels of upstream providers to the host you're trying to connect to, or something at the host network itself. Data will try to take alternative paths if its usual path has issues. Depending on a myriad of configurations depends entirely how successful it is. Your poor modem router may get caught up in this - it tries to route your connection out to where it thinks you need it to go. If it can't send it that way, some times they'll get confused and nothing works. Consumer grade routers are fairly limited on power so they're prone to taking "shortcuts" to reduce their load. End result, something gets funky somewhere, and shit stops.
If you reboot your modem and it works, the Internet did what it was designed to do. If the reboot doesn't do the trick, someone broke some little part of the internet.
Understanding how all of that gels together kinda makes you bloody impressed that the Internet works at all. It's a lot more complicated than that, but I'm trying to keep this as simple as possible :p
Now specifically for the period that was mentioned - there were known issues on one of the main interconnects to the US about the time that the relevant users (myself included) were having issues. People shouldn't have noticed it, but it's certainly possible. There might be something in that ;)
Good information very informative
DO THIS THE NEXT TIME YOU CANT ACCESS THE SITE
A usefull thing to do to test this would be to go to run,
type in CMD
enter this in the black box
tracert
www.thereefuge.com.au
you will then see the path your going down. post the info here and it will help everyone see what is going on and if it is infact a dns issue or the server is reject your IP
C:\Users\scott.rotton>tracert
www.thereefuge.com.au
Tracing route to thereefuge.com.au [76.10.221.241]
over a maximum of 30 hops:
1 6 ms 4 ms 4 ms 220-244-28-145.static.tpgi.com.au [220.244.28.14
5]
2 5 ms 5 ms 4 ms syd-nxg-men-crt1-ge-5-0-0.tpgi.com.au [202.7.171
.165]
3 159 ms 158 ms 158 ms te8-3.ccr01.sjc05.atlas.cogentco.com [38.122.92.
41]
4 158 ms 159 ms 158 ms te0-3-0-7.ccr21.sjc01.atlas.cogentco.com [154.54
.6.73]
5 162 ms 159 ms 161 ms te0-0-0-4.mpd21.sfo01.atlas.cogentco.com [154.54
.1.25]
6 204 ms 213 ms 203 ms te0-1-0-3.mpd21.mci01.atlas.cogentco.com [154.54
.2.209]
7 208 ms 208 ms 208 ms te0-4-0-3.mpd21.ord01.atlas.cogentco.com [154.54
.30.169]
8 211 ms 211 ms 212 ms te4-1.ccr01.sbn01.atlas.cogentco.com [154.54.27.
62]
9 214 ms 214 ms 214 ms te4-4.ccr01.ind01.atlas.cogentco.com [154.54.27.
81]
10 342 ms 223 ms 222 ms te4-1.ccr01.cvg02.atlas.cogentco.com [154.54.84.
169]
11 319 ms 219 ms 220 ms te4-1.ccr01.cmh02.atlas.cogentco.com [154.54.84.
178]
12 227 ms 222 ms 222 ms 38.104.22.74
13 223 ms 223 ms 222 ms 68.68.24.150.customer.bluemilenetworks.com [68.6
8.24.150]
14 221 ms 224 ms 224 ms 68.68.24.33.customer.bluemilenetworks.com [68.68
.24.33]
15 223 ms 224 ms 223 ms 76.10.221.241.customer.bluemilenetworks.com [76.
10.221.241]
Trace complete.