FYI - technically speaking. DNS errors aren't the host server's fault, but generally the requesting computer's ISP's fault. So the problem isn't with Larue, or his server, or his ISP, but with the individual's who are experiencing the problem.
I don't have Larue's old IP address, but if their address changed, then their DNS server updated the record and noted that the record was changed an propagation needs to occur. This is all Larue's provider can do. The problem is your DNS server has cache, and that means when you try to go to www.larue.com your internet service provider isn't actually looking up what Larue's address is...it is simply saying, "Oh, you've been here before, it's the same address as last time, here's where you need to go". Problem is the server may have moved (as is probably the case here, technically not physically).
You can either clear your DNS cache and force a lookup, or set your DNS server to a server that never ever runs a cache (my suggestion). Use 4.2.2.1 as your DNS server and you'll never see this problem again. It is the DNS root server for AT&T hosted in Alexandria Virginia and has been on-line since 1984. The 2nd longest living DNS server in existence. (4.1.1.1 is the longest living)
(yes, in a prior life I used to work for an ISP and a host OS software developer)