website on other server then mail

S

schoonmoeder

Verified User
Joined
Oct 14, 2007
Messages
34
Location
netherlands
hello,

my problem is that i have an server where only the mail is handled. but on another server (not da) there is the website. now i changed the dns records to the other server.

ftp
www
and domein.com
are pointing to the other server but it isn't routed there.

what do i need to change that it wil point to the other server
 
but it isn't routed there.
Click to expand...

Did you wait the required time after making a dns change before checking it?

Please also read this.
 
Last edited:
it's sended to my own DA server. if i place a site redirect it is done in 1 minut (site redirect to another domain)

but if i change my dns record on my ns then it's not changed. it's still pointing to my webserver but this part i want to send to another server
 
Please answer the question and read the link posted above. Otherwise we cannot help you unless domein.com really is your domain. Is it?

What was the TTL on the dns record before you changed it?
 
Last edited:
If it is the problem then DNS isn't set up properly, it uses the same IP# for domein.com and for all thre mx records. www.domein.com does use a different IP#.

However it probably isn't, becaue domein.com isn't hosted on a DirectAdmin server.

Jeff
 
it was for the domain simpelsales.nl
i now sended the domain provider to setup de mx record to my server and the reset to an other server (website provider).

i did had the following configurations.
mail mx 10
mail A my IP
smtp A my IP
pop A my IP
simpelsales.nl. txt My IP (with the normal DA stuff infront and behind it)
simpelsales.nl. NS ns1.newdream.nl.
simpelsales.nl. NS ns2.newdream.nl.

the follow A record where sended to there IP
www
www.simpelsales.nl.
ftp
simpelsales.nl.

maybe you can say what was wrong here so i can provide the right service the next time.

thanx in advanced
 
Deleted the stuff that was incorrect.

This is your current setup. Notice the www is pointing to a different ip and the nameservers are different than what you have listed. Do you see now why it is important to give us your real domain?

Code: 
simpelsales.nl.		275	IN	MX	21 mail.simpelsales.nl.
www.simpelsales.nl.	196	IN	A	85.158.250.80
simpelsales.nl.		177	IN	A	195.8.208.34
mail.simpelsales.nl.	182	IN	A	195.8.208.34
smtp.simpelsales.nl.	182	IN	A	195.8.208.34
pop.simpelsales.nl.	182	IN	A	195.8.208.34
simpelsales.nl.		6860	IN	NS	ns10.sohosted.com.
simpelsales.nl.		6860	IN	NS	ns11.sohosted.com.
 
Last edited:
Unfortunately, Floyd, you've misread his post. schoonmoeder was showing you the settings as shown in DirectAdmin, not as shown in the DNS zone file.

schoonmoeder, Floyd's information about the MX record is incorrect. The rest of his post may be relied upon.

Especially the part about not hiding your domain name from the very beginning :).

Jeff
 
Neither of the ip's or the nameservers appear to be on DA servers so I am not sure why the question was posted here. A DA server is not handling DNS so what DA says is not relevant anyway. Maybe he has DA configured on a different port or port 2222 blocked for the outside world.
 
i was hosting it on my DA server. and i was handling the DNS on my server. but as part of providing good service i can't keep a domain offline for some hours so i mailed the domain seller to take over the DNS.

well we now found out the where sending us wrong information about how they where forwarding the domain to us. they where runnen there own dns server and had fault configurations.

the main question is. if i give a A record for the www and for the simpelsales.nl. it should follow the IP i give there and not stay on my own server (other IP then the IP a wanted those parts to go to)
 
Again I am not sure what you are asking but this I can tell you, DNS changes are not immediate. You have to wait past the TTL that is in the zone file which can be a few minutes, several hours or even a whole day. So if you make a change and do not see an immediate effect do not think something is wrong at that point. Whoever is handling DNS for the domain right now should change the TTL to a few minutes so that you can see the effect quicker. But also remember the TTL change which take as long as the previous TTL before you see the change in TTL.

Hope that make sense. Bottom line is you have to wait for DNS changes. They are not immediate.
 
when i say to my domain provider just forward all from simpelsales.nl traffic to my DA server.

then i handle the dns stuff on my DA server isn't that then handled on the fly? because when i make a subdomain normally it is done on the fly.

i just want to thank you all for making everything clear
 
The DNS changes should be made instantly on your server.

However you wrote:
simpelsales.nl. NS ns1.newdream.nl.
simpelsales.nl. NS ns2.newdream.nl.
Click to expand...

and the authoritative nameservers on the internet report your namesevers are:

ns11.sohosted.com
ns10.sohosted.com

Unless these are the same, then DNS isn't going to work until you change your nameservers at your registrar.

My testing shows they are not the same:
Code: 
$ dig ns10.sohosted.com +short
195.8.208.34
$ dig ns11.sohosted.com +short
195.8.208.35
$ dig ns1.newdream.nl +short
85.17.169.138
$ dig ns2.newdream.nl +short
80.127.146.11
$

So you need to fix the nameservers for your domain at the registrar where you registered your domain.

Jeff



Jeff
 
The DNS changes should be made instantly on your server.
Click to expand...

That is true. However likely he is not using his server for his general web surfing. He is likely using his isp's nameservers for general web surf and so his isp is going to cache the DNS information so therefore his isp is not going to reflect his DNS changes immediately.

I was just trying to help to see that he himself may not see the effect immediately.
 
You must log in or register to reply here.
Back
Top