cannot resolve DNS over internet?

[iphonogasm]

Hi, im quite new to DNS and have a new domain www.example.com which require me to specify a DNS server.

 

So im creating a DNS server. ns1.haighaccess.net, and ive done a DNS lookup and it is not taken.

 

I have created the Zone, but cannot ping my hostname ns1.haighaccess.net remotely from outside the network. ie. ns1.haighaccess.net should resolve xxx.xxx.xxx.xxx

 

I can ping the hostname lacally ns1.haighaccess.net resolves 192.168.0.2

 

Any ideas?

 

Thanks!

[Virgule]

Hi,

 

i think your dns server is provide by the registrar of your domain www.example.com. you cannot ping your hostname ns1.haighacces.ns remotely because the server have a non routable adresse "192.168.0.2" and you don't have to create a your own dns server for the public zone !

 

Example : me i'have a domaine xxxxx.yyy which is registred by 1&1 for example. if i have a webserver behind a router-firewall i have to open port 80 (http) or/and 443 (https)for example on my gateway to the webserve. On my registrar i have dns option to record a "A" record with www.xxxxx.yyy which point to the Public IP which is the same external IP of your gateway, it 's the same process if you're web server it host by a different hoster. I 'm not a network expert but i never create a dns server when i by a domain name for client and i 've to redirect their www.xxxxx.yyy on the correct server. you registrar give you all tools to manage correctly you record and dns server.

 

sorry for the English.

 

Bye

[iphonogasm]

Ok so i have the domain www.megahosting.co.nz

 

I contact the company that is hosting my domain, and they said i need to setup these name servers on my side

 

I guess so my name server ns1.haighaccess.net resolves my public ip right?

 

Or would it be ns1.megahosting.co.nz

 

This is for educational purposes to learn more about DNS anyway so id like to do it the hard way :P

 

Thanks for your help

[iphonogasm]

Could someone please provide more help on this issue,

 

I have today launched my site, www.megahosting.co.nz and now need some name servers.

 

I need ns1.megahosting.co.nz to resolve my public IP.. and ns2.megahosting.co.nz to resolve a different IP.

 

how can i setup my name server to resolve my PUBLIC ip?

 

step-by-step guide would be great as im quite new to DNS, but i cannot find this anywhere?

 

is bind required for this?

 

Thanks!

[koga73]

Intodns.com

dnscolos.com

Those two sites will give you insite to your DNS problems.

On your domain registrar I'm guessing you are pointing your domain to your name servers ns1.example.com and ns2.example.com located at your static IP. If you are planning on hosting your web server on the same static IP as your DNS then you will need to setup port forwarding on your router for port 53 (dns) to the internal ip of your domain controller (which will handle the DNS entries for ns1 and ns2). Then setup port forwarding for 80/443 (http/https) to the internal IP of your web server. You really should have multiple static IPs having one for your domain controller handling DNS and a separate IP for your web server. Hope that makes sense good luck!

[iphonogasm]

Yes i have DNS forwarded at the roter. What sort of record do i create for my name server to resolve my public ip?

 

Heres my current setup.

 

[ATTACH=full]194[/ATTACH][ATTACH=full]195[/ATTACH][ATTACH=full]196[/ATTACH][ATTACH=full]197[/ATTACH][ATTACH=full]198[/ATTACH]

 

I then delegated my two name server ns1.megahosting.co.nz and ns2.megahosting.co.nz

 

Thanks

[koga73]

The part your missing is where you are actually setting your DNS entry to point to your web server. Microsoft didn't make this very clear because I struggled with the same issue. You need to create a new A host entry pointing to your web servers public static IP. Leave the first field blank so that your entry has "(same as parent folder)" type "A Host" pointing to "Public Static IP". If your trying to host your web server on the same instance of Windows Server 2008 as your DNS server you may run into problems. I had to use separate virtual machines with one acting as a DC and DNS and a separate to run IIS.