I posted this in SM's forum; so I'm just gonna quote it .
We've recently got a server from here, and we're kind have run into a problem with sorting out general NS issues. Its a new company, but I'm not new to the hosting business, where I was at previously used Cpanel/WHM. Basically I've created the NS's at our totalregistrations, and have the main domains using them, Skylis.net, using ns1/ns2.skylis.net. Now, at this present time, ive got the domain resolving to the server, but its giving what I can gather as the default page for a domain pointing at plesk that isnt set up to use the server yet. Except of course, it is, and theres and account for it.. but I'm thinking its to do with the zonefile issues on the server, and since I never dealt with DNS personally in the previous company nor used Plesk, I not sure what I should be putting down for the DNS template to sort this out; if at all this is the problem.
After doing that add the following, or get rid of what is already in there
nameserver xx.xx.xx.xx(use the IP you have for the ns1)
If both nameservers IPs are on the same box, just do that, if they're in different locations, to get the maximum redundancy add another nameserver. Then exit and save.
Then go back into PSA, and goto the Skylis.net domain, and go into it's DNS settings, if you have the NS records setup for them, make sure you have A records for the NS records. So if you have domain.com NS ns1.skylis.net you should have ns1.skylis.net A xx.xx.xx.xx -- See what I mean?
Hope that works, give it a few hours to make sure it fully propogates
Hey. Ive set everything, though you did say leave it to propergate, shouldnt it be working still via links on that box, since it checks the next DNS up, which would have propergated instantly. If so, no change.
Nah, it'll take 24-48 hours for your new NS to register.
What PSA does is, it'll recognize the IP since you put in the resolv.conf, and it'll goto the IP, which gives you that ugly looking PSA default. Give it a day or so, it'll propogate. I've used PSA5-7 and I've always had similar issues with it like this, it'll propogate, just give it some time
Hey, ok, Been looking around fixing other stuff, and something occoured to me.... FTP is working on the domains. this means propagation has been completed, yet i still get the Plesk page error. My inital thoughts are vhost settings in apache now, but i've been thro all the conf files related to them.
There are many things that can cause this error. Most common are DNS conflicts in the zone file or when a domain's IP is changed. There are a few other things too. If you could copy and paste the dns file here, it maybe be possible to discern the problem from that. Failing that, I don't mind taking a look at the server - these things are super easy to fix.
██ Laurence Flynn @ atOmicVPS LTD ██ Linux & Windows Cloud Hosting Solutions Powered by OnApp
██ Fully Managed [Shared] ► [Reseller] ► [Cloud VPS] ► [Dedicated]
██ Featuring the atOmicSTACK™ ● Speed ● Performance ● Reliability