I'm glad to hear I'm not the only one trying this out. If you've read the boards over the last 2 weeks, I've been working on this same problem and I think I'm about to solve the problem. If I do, I'll be sure to post it, but I'm actually typing this to ask that, if you find the solution, to post it as well.
Any time saved solving this would be greatly welcomed.
In this post by Sapient
it sounds like he had the same problem and solved it... but, sadly, that made no sense to me. Maybe if he reads this, he'll have some 'idiot-proof' steps we might take?
As to my attempt at solving this, in some of the posts I've read, some suggestions were made that I want to incorporate which might end up working to my benefit.
In particular, this post:
Which says that on a multi-homed server, browsing to http://ipaddress
, you get a generic 'Sorry, you cannot browse this IP address, please type in the domain name' message (similar to ie. http://www.server274.com/
) This way, browsing to the IP address gives you an error message instead of the first website created.
There may be a different way to do this, but I set up the server before with the mindset that the first domain was the 'admin' domain or root, and I think this creates part of the problem.
I'm thinking that if I set up the server, keeping in mind that 'admin' will be the IP address, not a domain name, then creating a domain name to use to host the Name Server, might work better? I guess the problem is having the domain that's acting as the DNS pointing to itself. If this doesn't work, then I'll probably register another domain name to use strictly for resolving my new ns.domain.com, point it to zoneedit and then point all the other domains to that domain name...
That may have been completely confusing... but, hopefully that will work. If not, I'm back to square one.
By the way, if anyone else has any other ideas or solutions to this problem, please post it for both of us.