Problem Accessing My Domain

ok, thank you all for all the previous help on this board... it got me through to this point without asking questions, but now i cannot find anything that has to do with my problem and i have no idea what i am doing wrong....

I am using bind 9.2.3 and have set up 1 zone in my name.conf file. (i am on win XP, if it makes a differance). i bought a domain from **** and regestered my DNS servers with them as ns1.***.com & ns2.***.com.... i had no problem using the same IP for both(unless it is a transparent problem i am unaware of)... i can ping both ns1.***.com and ns2.***.com.... but when i try to ping my domain ***.com it does not work...
ok heres my named.conf file (kinda looks like that of SilentRage)

options {
# Set the working directory from which all relative paths are based
#
directory "/windows/system32/DNS/etc";

# this server performs as a caching server. Allow recursion
#
recursion yes;

# For requests we aren't authoritative for, forward the request to
# the forwarder servers first, then try resolving it ourself
#
#forward first;

# use these servers as forwarders when resolving requests
# You may want to change the below IP's to your ISP caching servers
#
#forwarders {};

# Do not notify slave servers of zone changes
#
notify no;
};

# I'm a log fan
logging {
channel query_logging {
file "/windows/system32/DNS/log/dns.log"
versions 3 size 100M;
print-time yes; // timestamp log entries
};
category queries {
query_logging;
};
category lame-servers { null; };
};

# Specify the root name servers
zone "." IN {
type hint;
file "root.hint";
};

# My domain's zone
zone "***.com" IN {
type master;
file "***.com.zone";
};

now heres ***.com.zone

$ORIGIN ***.com.

@ SOA ns1 ( ***.com
admin
1
21600
1800
604800
900 )

NS ns1
NS ns2
A 68.39.255.81

ns1 A 68.39.255.81
ns2 A 68.39.255.81

www A 68.39.255.81

ok now if i run named -g this is what i get

C:\WINDOWS\system32\dns\bin>named -g
Feb 2 04:08:41.879 starting BIND 9.2.3 -g
Feb 2 04:08:41.879 using 1 CPU
Feb 2 04:08:41.889 loading configuration from 'C:\WINDOWS\System32\dns\etc\name
d.conf'
Feb 2 04:08:41.889 set maximum stack size to 0: not implemented
Feb 2 04:08:41.889 set maximum data size to 0: not implemented
Feb 2 04:08:41.889 set maximum core size to 0: not implemented
Feb 2 04:08:41.889 set maximum open files to 0: not implemented
Feb 2 04:08:41.899 listening on IPv4 interface Loopback Interface 1, 127.0.0.1#
53
Feb 2 04:08:41.899 listening on IPv4 interface TCP/IP Interface 2, 192.168.0.1#
53
Feb 2 04:08:41.899 listening on IPv4 interface TCP/IP Interface 3, ***
#53
Feb 2 04:08:41.909 command channel listening on 127.0.0.1#953
Feb 2 04:08:41.939 ignoring config file logging statement due to -g option
Feb 2 04:08:41.949 lilec.com.zone:3: no TTL specified; using SOA MINTTL instead

Feb 2 04:08:41.949 zone lilec.com/IN: loaded serial 1
Feb 2 04:08:41.949 running
(and it doesnt return to the command prompt i have to press ctrl+C... dont know if i am sopposed to or if i messed some configuration up)

now if i run dig on ***.com this is what i get

C:\WINDOWS\system32\dns\bin>dig ***.com

; <<>> DiG 9.2.3 <<>> ***.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2

;; QUESTION SECTION:
;***.com. IN A

;; ANSWER SECTION:
***.com. 900 IN A ***

;; AUTHORITY SECTION:
***.com. 900 IN NS ns2.***.com.
***.com. 900 IN NS ns1.***.com.

;; ADDITIONAL SECTION:
ns1.***.com. 900 IN A ***
ns2.***.com. 900 IN A ***
;; Query time: 20 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Mon Feb 02 04:10:28 2004
;; MSG SIZE rcvd: 111


ok i am doing all this from the computer with bind installed on it.... ok some more background info i am running apache web server and i have set up virtual hosts.... now before i acctually bought a domain and i was just testing it locally it worked(if i pointed my computer to use itself as the name server instead of the ones i get from my isp)... i'm not sure what is wrong it looks good to me from everything i saw on the board.... please if someone could help me out much thanks..... i tried to give as much info as possibly, cause i noticed that you all dont like when people are vague... Thank you....

"i had no problem using the same IP for both"

we'll know for sure if the name servers update. If it turns out that godaddy DOES allow identical IP's now (I think they've changed their interface sometime recently), I'll edit my previous post about registering name servers. However, they don't even appear to be registered yet. Since you downloaded my whois client, I'll show you the commands to check. First extract whois.zip to your "C:\WINDOWS\SYSTEM32\" directory or any directory included in your path environment variable. Then enter the following commands:

Failed responses (the .COM and .NET server uses "nameserver")

C:\>whois nameserver ns1.lilac.com | more
C:\>whois nameserver ns2.lilac.com | more

Successful responses (the .ORG server uses "host")

C:\>whois host ns1.dollardns.org | more
C:\>whois host ns2.dollardns.org | more

And finally to check on your domain host nameservers

C:\>whois lilac.com | more

It says:
NS48.PAIR.COM
NS0000.NS0.COM

The DNS agrees:
DNS Crawler

Course by the time you read this post, the whois and maybe the DNS has updated with your new servers. You see, that's why it doesn't work from the outside cause your name servers haven't updated. If it doesn't work from the inside it's cause you haven't changed your operating system's resolving servers as shown here under "DNS Servers":

C:\>ipconfig /all

one of those 2 IP's should be your LAN IP (or loopback IP if you do a registry hack like I had to. stupid MS wouldn't let me use 127.0.0.1 on windows 2000 via the GUI)

#forward first;
#forwarders {68.39.224.6; 68.39.224.7};

You need to remove the comment symbols (#) if you intend to use your ISP as your server's preferred resolver.

"(and it doesnt return to the command prompt i have to press ctrl+C... dont know if i am sopposed to or if i messed some configuration up)"

This is normal. -g is basically test mode and causes the server to start in the foreground.

"i tried to give as much info as possibly, cause i noticed that you all dont like when people are vague"

oh no, you gave me all I needed to know. Every bit of information you showed me helped with my diagnostic.

ok thanks for the speedy reply.... but i ran your client this was the results it found everthing.... i updated everything for over a week now... at first my name servers didnt show up but then after 2-3 days everything was official...

here are the results of your PROG....

C:\Documents and Settings\Bowser\Desktop\whois>whois "nameserver ns1.***.com"

Whois Server Version 1.3

Domain names in the .com and .net domains can now be registered
with many different competing registrars. Go to http://www.internic.net
for detailed information.

Server Name: NS1.***.COM
IP Address: ***
Registrar: ***
Whois Server: ***
Referral URL: ***


>>> Last update of whois database: Sun, 1 Feb 2004 18:41:03 EST <<<

C:\Documents and Settings\Bowser\Desktop\whois>whois "domain ***.com"

Whois Server Version 1.3

Domain names in the .com and .net domains can now be registered
with many different competing registrars. Go to http://www.internic.net
for detailed information.

Domain Name: ***
Registrar: ***
Whois Server: ***
Referral URL: ***
Name Server: NS1.***.COM
Name Server: NS2.***.COM
Status: ACTIVE
Updated Date: 29-jan-2004
Creation Date: 28-jan-2004
Expiration Date: 28-jan-2009


>>> Last update of whois database: Sun, 1 Feb 2004 18:41:03 EST <<<

ok it was my mistake for the two lines that were # (commented out) cause when i was testing locally i didnt know if i forwarded it ment forward my zones or forward the requests( but i figure now it means forward request)... i forgot to clear those two comments... and the ip, i dont have it set anymore to look locally cause like you said if i did it wouldnt look to the net first... if i try to ping ***.com it says "Ping request could not find host ***.com. Please check the name and try again." ... i am unsure why if i can ping the name serververs..... everything looked peaches right?? Thanks again.....

ok i did the thing to add 127.0.0.1 to my DNS server list....... it comes up locally now, but i new that would work to get it to come up locally, as i said i was testing it before.... but do i have to keep it in my DNS list to make it work for other people to see it as well?? can you see it?? www.***.com ...... it will be just an apache webpage telling you like if you see this something wrong... but for me it would be perfect.....

ok moving on. It appears everything has updated. Godaddy does indeed support identical IPs. I guess I can't rag on them anymore.

dig @a.gtld-servers.net lilec.com

however, the request times out when it goes to your server. This means you either have a router that isn't forwarding port 53 for UDP or TCP, or you have a firewall blocking those ports.

HAHAHAHA..... man i swear.... HAHAHAHA i bet that its this stupid XP Firewall that i have enabled..... I forgot to let port 53 open.... WOW......... man it had to be some small little thing like that... But honestly SilentRage you shouldnt answer anyones questions on setting up bind to work cause i just read all these post and got it running... Your the Best... (haha i feel like i'm doing a commercial)... ohh yeah I know its udp port 53, its also tcp port 53?? and now i have to work on that reverse lookup.... is it nessacary??

a reverse mapping is only useful if your ISP delegates your IP resolution to your name server. It's not required.

TCP port 53 is most typically used for zone transfers. If you don't need slaves to download zone transfers from your server, consider TCP port 53 optional.

(P.S. your domain works now)

ok cool... Thanks....