DNS is (VERY short form) a vast database that passes addresses around from one DNS server to another. Each server may retain entries for only so long, then dumps the entry. I suspect, cbenoi1, that your DNS servers (probably set by your ISP) are timing out entries, and then not immediately refreshing when you try to browse to AW.
I think, in this case, it isn't ipconfig that you want. It's nslookup.
Next time is happens, bring up a command prompt (terminal in KUbuntu). Type this (in caps for emphasis, not necessary):
NSLOOKUP
WWW.ABSOLUTEWRITE.COM
If you get the error of not found, try this:
NSLOOKUP
WWW.ABSOLUTEWRITE.COM 8.8.8.8
Using a made-up domain for error illustration:
C:\Windows\system32>NSLOOKUP
WWW.ABSOLITEWRITE.COM
Server: <redacted>
Address: 172.16.7.10
*** <DNS Server redacted> can't find
WWW.ABSOLITEWRITE.COM: Non-existent domain
It used my default DNS server and couldn't find it. I don't know if you'd get the "Non-existent domain" message. But it will likely fail similar.
The latter forces NSLOOKUP to use Google's open DNS servers. I think the syntax is the same in Linux (my Linux-fu is way out of practice). For me, I got this:
C:\Windows\system32>NSLOOKUP
WWW.ABSOLUTEWRITE.COM 8.8.8.8
Server: google-public-dns-a.google.com
Address: 8.8.8.8
Non-authoritative answer:
Name:
WWW.ABSOLUTEWRITE.COM
Address: 184.168.82.237
If the first one errors, but the second one works, it's your ISP's DNS servers (most likely, IMO). Or, whatever DNS servers you see when you type ipconfig /all (ifconfig in Linux).