Only 'externally' registered domains don't reach my VPS-server

[BBM]

Hi,

I would like some pointers on how to properly enter the nameserver-data into DA on my VPS-server.
I have a number of years experience with DA on a sharedhosting-server being a Reseller.

For some 3 months now I'm running a VPS with some 80 domainnames. These 80 domains and VPS are registered through the same company 'TransIP'.
Before this, I moved everything from a SharedHosting server, also running DA. With the user backups I moved and restored everything to my own VPS with DA.
So far everything seems to work fine, eventhough I did enter 'real / existing' nameservers yet into DA. But every domain I register myself automaticly goes online without any issues.

But, I'm having issues with domainnames which are registered by clients themselves through other registrars.
The domains don't resolve to my VPS-server, eventhough they have entered the 'TransIP' domain nameservers.
I *think* the problem lies in the nameservers I've entered in DA.

'TransIP' provides 3 nameservers.
But they also provide 2 DNS resolvers (IP's: 80.69.66.67 and 80.69.67.66) for use with their VPS, although I can't figure out, how, where and IF I have to use these resolvers.

Their nameservers are:
ns0.transip.net
ns1.transip.nl
ns2.transip.eu

I'm currently having 2 websites of clients being offline.
Can someone guide me, where to put what, exactly in DA?
(And, if the initial problem could be caused by this.)

 

[nobaloney]

Did TransIP tell you to give out their nameservers? If so, then they either told you how to register domains into their namesevers, or they've given you a way to get their nameservers to pick up domains registered in your local nameserver (domains should get registered automatically in your local nameserver when your clients set them up in their accounts).

Which did they do?

The only way we can check is if you give us the name and IP# of a domain which works, and do the same for one that doesn't work.

Then we can use standard DNS checking tools to see whee the problem lies.

Jeff

 

[Richard G]

I also use Transip for some years and I've never heard before that you could use their nameservers as your nameservers for external domains not registered by Transip. I could ofcourse be mistaken, but I can't find anything in their help section about it either.

for use with their VPS, although I can't figure out, how, where and IF I have to use these resolvers.

In /etc/resolve.conf you can use them.

But every domain I register myself automaticly goes online without any issues.

They probably all point to ns1.yourdomain.nl and ns2.yourdomain.nl, correct? You probably made some settings that A records or NS records point to your VPS server on registration.

The domains don't resolve to my VPS-server, eventhough they have entered the 'TransIP' domain nameservers.

They should enter the ns1.domain.nl and ns2.domain.nl which you have setup in Directadmin.
If not, then they should have their A records point to the ip address of your VPS.

Did you already wrote a ticket to Transip themselves? They have a great support department.

Edit: I've just seen you put Transip resolver ip's in your reseller section etc. You should not do it that way, because it are not your ip's.
Check this (click) thread, it's in Dutch, maybe you understand better what to do with them.
You can also always ask at webhostingtalk.nl which is a dutch languages forum and Transip employee's visit it too from time to time.

 

[BBM]

Thanks for the answers guys.
I've learned yesterday this is a 'simple' zone-transfer error.

I've edited named.conf and gave a number of TransIP-server permission to do zone-transfers from my VPS.
But reading all the info online, I was under the impression I was supposed to do more to get it to work properly, like changing a serialnumber and matching SOA-values.

While there are some more nameserver-issues with my setup at the moment, somehow the offline website went online today, without me (knowingly) initiating a zone-transfer to TransIP.
Having about 80 domains on the VPS with about 20 important ones, I carefully changed a some nameserver-settings in DA. Not expecting to solve this particulair problem though, but mainly removing some unused nameservers and replacing them with a single TransIP-nameservers for now. This was probably enough to solve this issue enough to get the site online again.
I still need to dive into this further and get everything properly setup and know for certain that zone-transfers are happening as they should.

 

[Richard G]

like changing a serialnumber and matching SOA-values.

That is not needed. Those things are done automatically when you make changes in DNS in DA (or with Transip).

You can find something here about Transip and zone transfers.
Maybe it's a good idea to use your own domain as primary nameserver, and the Transip as secondary nameserver. That is possible and supported by Transip. Because the easyest way to have external registered domain names point to your server or vps, is let the customer use your nameservers.
Indeed that will take some looking in to, but if you have about 80 domains I'm sure you will work it out.

 

[BBM]

Thanks Richard,
I didn't know DA took care of those serialnumber updates.

I've seen that link on TransIP (and a lot others on this subject). Those are the IP's I've given permission to transfer zones on my VPS.
At the moment I'm looking into getting a domainname of mine ready for primary nameserver-use. (Don't want to 'down' a lot of sites because of a silly mistake here).

 

[Richard G]

Oke no problem. I don't know where or how your customers external registered domain names point to you, but if I can be of help, just write me pm or email. You can do that in Dutch then too.