| 1:15 am on Jan 17, 2002 (gmt 0)|
I generally use a third party DNS service. I don't know if url's are acceptable in this case, but www.mydomain.com (yes that is the actual domain) offers free DNS and the whole thing is set up with little web forms...it shouldn't be too tough.
| 2:17 am on Jan 17, 2002 (gmt 0)|
Actually this helps a little. But What I want is to set up my own name server so I can have control. How is this done with win2k, or could I use some other DNS server (linux?), if so which one where do I get the software, how is it configured etc...As well www.mydomain.com is free at the basic level, but I will install Exchange 2000 and I need the MX in the DNS. Again if there is another free resource like mydomain.com that does it all then I would appreciate all responses.
| 2:45 am on Jan 17, 2002 (gmt 0)|
I'm pretty sure mydomain.com lets you change MX settings.
| 3:46 am on Jan 17, 2002 (gmt 0)|
Whoever registered your domain should also provide a free DNS server.
There is a program similar to BIND (a UNIX DNS server) for W2K, but I haven't installed it. I can't recall the name off hand, but if you do a search for "BIND Windows 2000" you'll find it.
The DNS entries are very important - as they contain your MX and A records, so I'd rather let Verio keep those for me.
I can edit them at any time, but I didn't want the added responsibility of my own DNS server.
| 4:00 am on Jan 17, 2002 (gmt 0)|
I tried to register with mydomain.com, their site is flaky (connect to page then no connection). What other DNS hosters are you using.
| 4:02 am on Jan 17, 2002 (gmt 0)|
registered FQDN with internic.ca. They have 2 DNS servers listed as ns1, ns2, but how does this connect to my IP and website.
| 5:36 am on Jan 17, 2002 (gmt 0)|
This is a guess since I haven't used internic.ca, the entries you made at Internic.ca are just to delegate the domain, but no DNS function is performed, essentially it is parked.
If you had your own DNS set up, or signed up for hosting with an ISP, you would then enter the IP addresses of the primary and secondary dns (either your own and/or the ISP's) as the entries for the primary and secondary DNS.
FWIW, I don't know how much you know about DNS, but if you are not familiar with it I would suggest some reading on Bind (for Unix/Linux) there is also a port of Bind for NT, if you go with Bind, stay away from versions lower than 8. You can also use the DNS server that comes with Win/2000 server (not included with the desktop version I believe).
Some DNS/Bind info that may be of interest can be found HERE [dns.net].
Once you get familiar with Bind I'd be happy to answer some questions to get you going, there is just too much involved to answer it as an open ended question.
Or you can go to [dyndns.org...] and donate $30. and use their DNS for your registered domain (while you work on setting up your own if that is what you ultimately would like to do).
.... and welcome to WebmasterWorld, hope you enjoy the forums.
| 10:59 am on Jan 17, 2002 (gmt 0)|
"Bind for Windows 2000" called Microsoft DNS Service :)
I think a good idea is to buy a book and RTFM
Setting up DNS is a complex process too large to describe in few paragraphs.
| 8:49 am on Jan 19, 2002 (gmt 0)|
w2kASiis5, what exactly are you having trouble with?
This is the basic process that you'll need to complete:
Register your Name Servers with your Domain Name Registrar.
Install the W2k DNS service.
Create your Zones.
Populate the Zones with your resource records.
| 1:25 am on Jan 20, 2002 (gmt 0)|
I think the initial problem is the setting up of the Name Server(s), so that I can point from the Registrar. This is where I need help.
I try to point the Registrar's to my name server ns1.atmydomain.ca and I get
"The following problems were found with your DNS servers... Please verify your data and try again An error was found with ns1.atmydomain.ca"
And when I get more info I get
"Error: Nameserver # is the same as Nameserver #. [95%]
A nameserver in your list was specified twice.Each domain must have at least two distinct,...
Error: The nameserver does not exist [95%]
One of the nameservers you specified has not been registered.Please contact your hoster to verify...
How do I register a new nameserver? [80%]
Only the owner of a domain can perform the initial registration of a nameserver under... "
W2K DNS is installed, I believe that the zones I created are correct.
Now do I have to get the provider of my broadband highspeed cable to enter entries into their DNS?
| 3:13 pm on Jan 20, 2002 (gmt 0)|
You need at least 2 distinct DNS servers to set up a domain. One is primary and one is secondary (which gets data from primary). You can ask your provider to setup secondary DNS for you. Than allow your DNS to transfer data to secondary and put both servers in registrar's DNS servers fields.
| 4:31 pm on Jan 20, 2002 (gmt 0)|
Try granitecanyon.com That's what I use and it's free and works great.
| 3:11 am on Feb 1, 2002 (gmt 0)|
I think I have corrected my DNS problems can anyone check my website to see if it resolves correctly. Its www.compu-trade.ca
| 4:06 am on Feb 1, 2002 (gmt 0)|
>check my website to see if it resolves correctly
does not resolve.
| 4:58 pm on Feb 1, 2002 (gmt 0)|
FWIW, from here (Arizona), a DNS lookup produced an IP (184.108.40.206) but I can't connect to the web server using either the DNS or the IP. Pinging the IP gives good response time.
| 10:50 pm on Feb 1, 2002 (gmt 0)|
Now I need some help. My cable sevice provider is mountaincable.net, Anyone on mountaincable.net can connect to the websitew using the URL. I did some testing usimg multiple dial up accesses (Interlynx.net connected to the website, inforamp.net no connection, golden.net no connection). A friend which live out in the country uses lintap.com and he can connect.)
I also did some testing using external NSLOOKUP utilities that are offered on the net, some come up with non-authoratative error. Does this info explain why?
| 11:46 pm on Feb 1, 2002 (gmt 0)|
Neither [220.127.116.11...] nor [18.104.22.168...] bring up a web page for me. Netscape gives a "There was no response" error. If this was my problem, I'd make sure the world could access my IP and web server before worrying about assigning a name to it.
Assuming this is the correct IP and YOU can access a web server on it, find out who else can and go from there. AFTER all of that is working correctly is the time to add DNS addressing. Remember, DNS names are simply "alaises" for IPs. If the underlying IP setup isn't correct...