DNS and internal IP address's

I host a Web Server on my computer. My computer is my Domain Controller, Web Server and DNS Server. I have been trying to figure this problem out for a LONG time and cannot seem to get it right and was HOPING that someone here might be able to help.

My DNS is setup as follows:

(same as parent folder) SOA [251], main.twistedpaircomputing.com., admin.twisted-pair.cjb.net.
(same as parent folder) NS ns2.twistedpaircomputing.com.
(same as parent folder) NS main.twistedpaircomputing.com.
(same as parent folder) NS ns1.twistedpaircomputing.com.
(same as parent folder) A 192.168.1.100
(same as parent folder) A 131.191.12.230
adam CNAME twistedpaircomputing.com.
dauntless CNAME twistedpaircomputing.com.
ns1 A 131.191.12.230
ns2 A 131.191.12.230
the-joys CNAME twistedpaircomputing.com.
tim CNAME twistedpaircomputing.com.
www CNAME twistedpaircomputing.com.

Everything appears to be OK except when people try and go to my website (Twisted Pair Computing) the DNS sometimes resolves the 192.168.1.100 first and it takes a while to load. I was told to delete the "(same as parent folder) A 192.168.1.100" line but when I do Windows DNS puts it back in. I cannot figure this out I am going nutz here.

Anyone got any suggestions?????

Please HELP!!!!!!!!!!!!!!!!!!!!!!!

See http://homepages.tesco.net/~J.deBoy...omain-name.html for more information on this.

...and I do not think it applies to me. I am not trying to run an internal and external DNS. I am not providing DNS for the internal computers. I am merely running DNS to provide records for my domains. BTW my router provides DHCP.

Maybe you could either explain how that document (above) applies OR help me with my "possibly different" issue.

Any thoughts anyone???

I just read that if I set up internal IP only and then set up forwarders to my ISPs DNS that this should work. Any thoughts?

(same as parent folder) SOA [251], main.twistedpaircomputing.com., admin.twisted-pair.cjb.net.
(same as parent folder) NS ns2.twistedpaircomputing.com.
(same as parent folder) NS main.twistedpaircomputing.com.
(same as parent folder) NS ns1.twistedpaircomputing.com.
(same as parent folder) A 192.168.1.100
adam CNAME twistedpaircomputing.com.
dauntless CNAME twistedpaircomputing.com.
ns1 A 192.168.1.100
ns2 A 192.168.1.100
the-joys CNAME twistedpaircomputing.com.
tim CNAME twistedpaircomputing.com.
www CNAME twistedpaircomputing.com.

(with forwarders setup)

If you changed that cname for WWW to an a record to the correct IP...that should go a long way.

I presume you named your windows domain twistedpaircomputing.com and this is why this automatically propogates. Not much you can do about it. Also as far it taking a long time...ONLY in your internal network would anyone be able to browse the 192.168 IP. No one from the public internet would be able to.