Page 2 - Windows 2003 DNS Issues

Actually registering a name server is a made-up thing. And yes, you must "register" the name server with the registrar you signed up with. All a registrar needs to know is the name server domains and IP's for your hosts. However, they decided to newbify things. Now all you have to do is provide the name server domain and the registrar will look up the IP address for you (to help prevent IP typo errors). However, they'll still provide the means of adding IP's to domains if it is apart of the domain you're registering. This whole "registering nameservers" gig is just an attempt by the registrars to keep the DNS system consistent.

Understand that, but your response sounds more like providing namesersers for a domain rather than registering and managing nameservers themselves.

I've had to change IPs for my "registered" nameservers a time or two and did it through the Dotster interface. I used to do it via NSI, but that is not possible since the registrars have the database control of the domains. It makes things easier for newbies, but a PITA for everyone else. When you needed a handle for nameservers and had to provide the IPs, it was more complicated, but better, IMO.

For newbie registrants, not needing the IPs is actually better. Also, since there is not a separate user/handle/pw for tech contact, the registrant has to make nameserver changes unless he wants to give the pw to the hosting or dns provider. Nowadays, that's not safe. Most registrants have no clue re nameservers other than they have to provide them for their domains. I deal with it daily.

The problems with changing IPs on nameservers comes when you can't access the registrar or their response is quirky. You should be able to go directly to the registry to register and make changes to nameservers using a separate UID/pw, IMO.

oh definately. Anytime anybody "newbifies" things I consider it worse than the alternative. By no means do I support this "registering nameservers" nonsense. I was just showing the value in such a system in DNS consistency. I always try to see the benefit of things I don't like. For example VB vs C programming. VB sucks, but it has a purpose.

First looking at your router IP you gave: 192.168.0.240
I am asuming that this is what your router IP address is internally. However for your name server you need to specify your External router IP so it can it can be found by other servers. This is more easily understood if you understand how DNS resolves:

for instance devshed.com/index.htm is resolved by looking up the nameserver for 'COM', then the COM nameserver tells your browser to look up the nameserver ns1.devshed.com. that server points you to the web server which then displays the index.htm.

-------

Also check to make sure your IPS has registered your network. They usually will, however contact them and tell them you have a name server so your network needs to be registered.

as mentioned by another poster you have to register name servers as well.


I just started with DNS last week, However I hope this helped.

*** Can't find server name for address 192.168.0.1: Non-existent domain
Default Server: UnKnown
Address: 192.168.0.1

> nslookup ns1.militarygunsupply.com
Server: ns1.militarygunsupply.com
Address: 66.139.209.193


The IP 192.168.0.* are IPs generally used for internal networks and not for the outside world!!! You'd best check that as it looks like you are entering the wrong info

*edit
Oops, looks like the guy above already spotted that