Hello,

I've searched the forum to get an answer on this, but I haven't found anything that helps me.

I got a Windows 2003 standard server with Helm

ns1.mydomain.com works fine, but not n2.mydomain.com.

ns1.mydomain.com has the ip of the server, 192.168.0.1 (that's not the real address). I want ns2.mydomain.com to have 192.168.0.2.

I have added ns2 to my domain name. When I ping ns2 it show me the ip, 192.168.0.2, but it will not respond.

How do I configure NS2 in Windows / Helm? I understand I have to add 192.168.0.2 somewhere to get it respond. I don't have any real secondary DNS so this must be pointed to my primary I guess!

I really hope anybody can help me! I just need ns2 to respond in order to get .se domains to work. They require response from a secondary name server.

Best regards,
Henrik

In Linux this is called "Virtual DNS".

Thank you in advance,

Henrik

I don' think what you looking for is what is so called "Virtual DNS".
Virtual DNS is mainly used to give your resellers their own NS so their customers THINK they are using a real server from their hosting company:)
If you need to know how to setup VDNS in Helm, try Helm Forums in their own web site, I saw many about it when I was looking for.

Hello,

I haven't found how to setup VDNS in Webhostautomation forums.

I don't think it's possible to setup my ns2 if I don't use virtual DNS...

I don't have any real server for my secondary DNS.

First off your IPs you have set are internal IPs you have to have External IPs for this to work. Each NS should have its own IP (external) You cant use a internal domain because users can not access that IP from the web thats only on the server. You can use those IPs to assign to DNS and IIS but for nameserver you need external IPs. You will have to request IPs from your server provider and assign them in DNS. If you need more help just post it I have done alot with NSs and Windows DNS IIS.

- Jon