It looks like this site is using a forwarded IP address, rather than a legitimate DNS entry for your domain... look at the results of a tracert to www.ulukatu.com...

Tracing route to premium6.geo.yahoo.akadns.net [68.142.234.50]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1 
  2    28 ms    25 ms    22 ms  172.31.255.251 
  3    21 ms    22 ms    22 ms  192.168.23.57 
  4    24 ms    22 ms    22 ms  ge-5-0-102.hsa2.Seattle1.Level3.net [209.247.88.57] 
  5    24 ms    22 ms    22 ms  ae-1-51.mp1.Seattle1.Level3.net [4.68.105.1] 
  6   119 ms   119 ms   117 ms  as-3-0.bbr1.Washington1.Level3.net [64.159.3.254] 
  7   118 ms   119 ms   119 ms  ge-3-0-0-53.gar1.washington1.level3.net [4.68.121.66] 
  8   105 ms   107 ms   107 ms  63.210.29.230 
  9   106 ms   104 ms   107 ms  unknown-206-190-41-69.yahoo.com [206.190.41.69] 
 10   106 ms   107 ms   107 ms  p6w1.geo.re2.yahoo.com [68.142.234.50]

DotNetNuke is not picking up on anything meaningful in the PortalAlias table and so can't make a match.  What you're seeing is simply DNN displaying the default site because it doesn't know what else to do.

I have never set up a site with forwarding... I think you might be OK with simply putting the IP address into the portalalias table as well.  Someone else may wish to comment.

---

Scott Willhite, Co-Founder DNN

The best choice is simply to use a true DNS A record to point to the IP address... rather than a forward.  Honestly, I'm a little fuzzy on using virtual directories, I always use new websites.  I presume from the entry you've specified that DNN is running in a virutal directory called "dotnetnuke"?  You can at least remove the last part...

---

Scott Willhite, Co-Founder DNN